citypay_api_client 1.0.1 → 1.0.2

data/spec/models/authen_required_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT

data/spec/models/c_res_auth_request_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT

data/spec/models/capture_request_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT

data/spec/models/card_holder_account_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT
@@ -21,12 +20,59 @@ describe 'CardHolderAccount' do
   before do
     # run before each test
     @instance = CityPayApiClient::CardHolderAccount.new
+    json = '{"CardHolderAccount": {
+        "account_id": "abc123",
+        "cards": [{
+                      "bin_commercial": false,
+                      "bin_corporate": false,
+                      "bin_country_issued": "GBR",
+                      "bin_currency": "GBP",
+                      "bin_description": "Visa Classic",
+                      "bin_eu": false,
+                      "card_id": "2U1XV3PJSeUXFNzXidACn2TyCzAK",
+                      "card_status": "ACTIVE",
+                      "default": true,
+                      "expmonth": 7,
+                      "expyear": 2022,
+                      "label": "TestVisa/0002",
+                      "label2": "TestVisa/0002,Exp:7/2022",
+                      "scheme": "TestVisa",
+                      "token": "ctPCzxq4WxEwWbkG7whRPLRCG27vYFNzsEDNihYmDwqsBc5QEXnFRvq2j5oRyb56ErRVEQaBN7PFMEDtjQQXDQpfxKkp3AxbyeGo61RhKBjFTFegaP4LBZUxFZimsXW8Deae9VyhWSgS2o8AXzTJU9UP3bo8kRcpataxuH3fJj3JHDnyeZt"
+                  }],
+        "contact": {
+            "address1": "7 Esplanade",
+            "address2": "",
+            "address3": "",
+            "area": "St Helier",
+            "company": "CityPay Ltd",
+            "country": "JE",
+            "email": "support@citypay.com",
+            "firstname": "Joe",
+            "lastname": "Wicks",
+            "mobile_no": "077112123456",
+            "postcode": "JE2 3QA",
+            "telephone_no": "+4415341234567",
+            "title": "Mr"},
+        "date_created": "2020-08-01T09:15:24Z",
+        "default_card_id": "2U1XV3PJSeUXFNzXidACn2TyCzAK",
+        "default_card_index": 0,
+        "status": "ACTIVE",
+        "unique_id": "Ew3BKeWNdL3qKQU7XK7Sbt2eAL5WFW4AfoASDSA"
+    }}'
+    data = JSON.parse(json, :symbolize_names => true)
+    @account = CityPayApiClient::ApiClient.new.convert_to_type(data, "CardHolderAccount")
   end
 
   after do
     # run after each test
   end
 
+  describe 'JSON parser' do
+    it 'should parse an account' do
+      expect(@account).to be_instance_of(CityPayApiClient::CardHolderAccount)
+    end
+  end
+
   describe 'test an instance of CardHolderAccount' do
     it 'should create an instance of CardHolderAccount' do
       expect(@instance).to be_instance_of(CityPayApiClient::CardHolderAccount)
@@ -34,49 +80,78 @@ describe 'CardHolderAccount' do
   end
   describe 'test attribute "account_id"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      expect(@account.account_id).to eq("abc123")
     end
   end
 
   describe 'test attribute "cards"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      expect(@account.cards.length).to eq(1)
+      @c = @account.cards[0]
+      expect(@c.bin_commercial).to eq(false)
+      expect(@c.bin_corporate).to eq(false)
+      expect(@c.bin_country_issued).to eq("GBR")
+      expect(@c.bin_currency).to eq("GBP")
+      expect(@c.bin_description).to eq("Visa Classic")
+      expect(@c.bin_eu).to eq(false)
+      expect(@c.card_id).to eq("2U1XV3PJSeUXFNzXidACn2TyCzAK")
+      expect(@c.card_status).to eq("ACTIVE")
+      expect(@c.default).to eq(true)
+      expect(@c.expmonth).to eq(7)
+      expect(@c.expyear).to eq(2022)
+      expect(@c.label).to eq("TestVisa/0002")
+      expect(@c.label2).to eq("TestVisa/0002,Exp:7/2022")
+      expect(@c.scheme).to eq("TestVisa")
+      expect(@c.token).to eq("ctPCzxq4WxEwWbkG7whRPLRCG27vYFNzsEDNihYmDwqsBc5QEXnFRvq2j5oRyb56ErRVEQaBN7PFMEDtjQQXDQpfxKkp3AxbyeGo61RhKBjFTFegaP4LBZUxFZimsXW8Deae9VyhWSgS2o8AXzTJU9UP3bo8kRcpataxuH3fJj3JHDnyeZt")
     end
   end
 
   describe 'test attribute "contact"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      @c = @account.contact
+      expect(@c.address1).to eq("7 Esplanade")
+      expect(@c.address2).to eq("")
+      expect(@c.address3).to eq("")
+      expect(@c.area).to eq("St Helier")
+      expect(@c.company).to eq("CityPay Ltd")
+      expect(@c.country).to eq("JE")
+      expect(@c.email).to eq("support@citypay.com")
+      expect(@c.firstname).to eq("Joe")
+      expect(@c.lastname).to eq("Wicks")
+      expect(@c.mobile_no).to eq("077112123456")
+      expect(@c.postcode).to eq("JE2 3QA")
+      expect(@c.telephone_no).to eq("+4415341234567")
+      expect(@c.title).to eq("Mr")
     end
   end
 
   describe 'test attribute "date_created"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      expect(@account.date_created).to eq(DateTime.parse("2020-08-01T09:15:24Z"))
     end
   end
 
   describe 'test attribute "default_card_id"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      expect(@account.default_card_id).to eq("2U1XV3PJSeUXFNzXidACn2TyCzAK")
     end
   end
 
   describe 'test attribute "default_card_index"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      expect(@account.default_card_index).to eq("0")
     end
   end
 
   describe 'test attribute "status"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      expect(@account.status).to eq("ACTIVE")
     end
   end
 
   describe 'test attribute "unique_id"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      expect(@account.unique_id).to eq("Ew3BKeWNdL3qKQU7XK7Sbt2eAL5WFW4AfoASDSA")
     end
   end
 

data/spec/models/card_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT

data/spec/models/card_status_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT

data/spec/models/charge_request_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT

data/spec/models/contact_details_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT

data/spec/models/decision_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT
@@ -27,13 +26,39 @@ describe 'Decision' do
     # run after each test
   end
 
+  def convert_decision(json)
+    data = JSON.parse(json, :symbolize_names => true)
+    CityPayApiClient::ApiClient.new.convert_to_type(data, "Decision")
+
+  end
+
   describe 'test an instance of Decision' do
     it 'should create an instance of Decision' do
       expect(@instance).to be_instance_of(CityPayApiClient::Decision)
     end
   end
-  describe 'test attribute "authentication"' do
+
+
+  describe 'test attribute "authen_required"' do
     it 'should work' do
+
+      decision = convert_decision '{
+    "AuthenRequired": {
+        "acs_url": "https://www.acs.com/tdsecure/opt_in_dispatcher.jsp?partner=debit&VAA=B",
+        "md": "0000000000000000000022",
+        "pareq": "eJxVUm1v2yAQ/itWv8dg/B5dmJyfw=="
+    }
+}'
+
+      expect(decision.auth_response).to be_nil
+      expect(decision.request_challenged).to be_nil
+      expect(decision.authen_required).to be_truthy
+
+      expect(decision.authen_required.acs_url).to eq("https://www.acs.com/tdsecure/opt_in_dispatcher.jsp?partner=debit&VAA=B")
+      expect(decision.authen_required.md).to eq("0000000000000000000022")
+      expect(decision.authen_required.pareq).to eq("eJxVUm1v2yAQ/itWv8dg/B5dmJyfw==")
+
+
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
   end
@@ -46,7 +71,73 @@ describe 'Decision' do
 
   describe 'test attribute "result"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      decision = convert_decision '
+{
+    "AuthResponse": {
+        "amount": 5500,
+        "atrn": "atrn1",
+        "atsd": "a",
+        "authcode": "12345",
+        "authen_result": "R",
+        "authorised": true,
+        "avs_result": "G",
+        "bin_commercial": false,
+        "bin_debit": false,
+        "bin_description": "bin_desc",
+        "cavv": "cavvvvvvvvvvvvv",
+        "context": "20200812075906AAAGV4",
+        "csc_result": "C",
+        "currency": "GBP",
+        "datetime": "2020-08-12T07:59:11Z",
+        "eci": "0",
+        "identifier": "ident1",
+        "live": true,
+        "maskedpan": "400000******0002",
+        "merchantid": 12345,
+        "result": 1,
+        "result_code": "000",
+        "result_message": "System: Accepted Transaction",
+        "scheme": "VISA_BUSINESS",
+        "sha256": "abcdefg",
+        "trans_status": "P",
+        "transno": 74875
+    }
+}
+'
+      expect(decision.auth_response).to be_truthy
+      expect(decision.request_challenged).to be_nil
+      expect(decision.authen_required).to be_nil
+
+      response = decision.auth_response
+
+      expect(response).to be_instance_of(CityPayApiClient::AuthResponse)
+      expect(response.amount).to eq(5500)
+      expect(response.atrn).to eq("atrn1")
+      expect(response.atsd).to eq("a")
+      expect(response.authcode).to eq("12345")
+      expect(response.authen_result).to eq("R")
+      expect(response.authorised).to eq(true)
+      expect(response.avs_result).to eq("G")
+      expect(response.bin_commercial).to eq(false)
+      expect(response.bin_debit).to eq(false)
+      expect(response.bin_description).to eq("bin_desc")
+      expect(response.cavv).to eq("cavvvvvvvvvvvvv")
+      expect(response.context).to eq("20200812075906AAAGV4")
+      expect(response.csc_result).to eq("C")
+      expect(response.currency).to eq("GBP")
+      expect(response.datetime).to eq(DateTime.parse("2020-08-12T07:59:11Z"))
+      expect(response.eci).to eq("0")
+      expect(response.identifier).to eq("ident1")
+      expect(response.live).to eq(true)
+      expect(response.maskedpan).to eq("400000******0002")
+      expect(response.merchantid).to eq(12345)
+      expect(response.result).to eq(1)
+      expect(response.result_code).to eq("000")
+      expect(response.result_message).to eq("System: Accepted Transaction")
+      expect(response.scheme).to eq("VISA_BUSINESS")
+      expect(response.sha256).to eq("abcdefg")
+      expect(response.trans_status).to eq("P")
+      expect(response.transno).to eq(74875)
     end
   end
 

data/spec/models/error_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT

data/spec/models/external_mpi_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT

data/spec/models/list_merchants_response_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT
@@ -20,7 +19,31 @@ require 'date'
 describe 'ListMerchantsResponse' do
   before do
     # run before each test
-    @instance = CityPayApiClient::ListMerchantsResponse.new
+    json = '
+{
+    "ListMerchantsResponse": {
+        "client_name": "CityPay Demo",
+        "clientid": "PC123456",
+        "merchants": [
+            {
+                "currency": "GBP",
+                "merchantid": 12345678,
+                "name": "CityPay One",
+                "status": "T",
+                "status_label": "Test"
+            },
+            {
+                "currency": "GBP",
+                "merchantid": 87654321,
+                "name": "CityPay Two",
+                "status": "T",
+                "status_label": "Test"
+            }
+        ]
+    }
+}'
+    data = JSON.parse(json, :symbolize_names => true)
+    @instance = CityPayApiClient::ApiClient.new.convert_to_type(data, "ListMerchantsResponse")
   end
 
   after do
@@ -34,19 +57,31 @@ describe 'ListMerchantsResponse' do
   end
   describe 'test attribute "client_name"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      expect(@instance.client_name).to eq("CityPay Demo")
     end
   end
 
   describe 'test attribute "clientid"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      expect(@instance.clientid).to eq("PC123456")
     end
   end
 
   describe 'test attribute "merchants"' do
     it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+      expect(@instance.merchants.length).to eq(2)
+      i = @instance.merchants[0]
+      expect(i.currency).to eq('GBP')
+      expect(i.merchantid).to eq(12345678)
+      expect(i.name).to eq("CityPay One")
+      expect(i.status).to eq("T")
+      expect(i.status_label).to eq("Test")
+      ii = @instance.merchants[1]
+      expect(ii.currency).to eq('GBP')
+      expect(ii.merchantid).to eq(87654321)
+      expect(ii.name).to eq("CityPay Two")
+      expect(ii.status).to eq("T")
+      expect(ii.status_label).to eq("Test")
     end
   end
 

data/spec/models/mcc6012_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT

data/spec/models/merchant_spec.rb

@@ -3,7 +3,6 @@
 
 # This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
-The version of the OpenAPI document: 6.0.0
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0-SNAPSHOT