citypay_api_client 1.0.2 → 1.1.1

data/spec/api_client_spec.rb

@@ -1,11 +1,11 @@
 =begin
 #CityPay Payment API
 
-# 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. 
+# 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 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. These include  * 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. 
 
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.0.0-SNAPSHOT
+OpenAPI Generator version: 6.2.1
 
 =end
 
@@ -196,8 +196,8 @@ describe CityPayApiClient::ApiClient do
     let(:api_client) { CityPayApiClient::ApiClient.new }
 
     it 'works' do
-      expect(api_client.select_header_content_type(nil)).to eq('application/json')
-      expect(api_client.select_header_content_type([])).to eq('application/json')
+      expect(api_client.select_header_content_type(nil)).to be_nil
+      expect(api_client.select_header_content_type([])).to be_nil
 
       expect(api_client.select_header_content_type(['application/json'])).to eq('application/json')
       expect(api_client.select_header_content_type(['application/xml', 'application/json; charset=UTF8'])).to eq('application/json; charset=UTF8')

data/spec/configuration_spec.rb

@@ -1,11 +1,11 @@
 =begin
 #CityPay Payment API
 
-# 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. 
+# 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 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. These include  * 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. 
 
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.0.0-SNAPSHOT
+OpenAPI Generator version: 6.2.1
 
 =end
 
@@ -17,7 +17,7 @@ describe CityPayApiClient::Configuration do
   before(:each) do
     # uncomment below to setup host and base_path
     # require 'URI'
-    # uri = URI.parse("https://api.citypay.com/v6")
+    # uri = URI.parse("https://api.citypay.com")
     # CityPayApiClient.configure do |c|
     #   c.host = uri.host
     #   c.base_path = uri.path
@@ -27,14 +27,14 @@ describe CityPayApiClient::Configuration do
   describe '#base_url' do
     it 'should have the default value' do
       # uncomment below to test default value of the base path
-      # expect(config.base_url).to eq("https://api.citypay.com/v6")
+      # expect(config.base_url).to eq("https://api.citypay.com")
     end
 
     it 'should remove trailing slashes' do
       [nil, '', '/', '//'].each do |base_path|
         config.base_path = base_path
         # uncomment below to test trailing slashes
-        # expect(config.base_url).to eq("https://api.citypay.com/v6")
+        # expect(config.base_url).to eq("https://api.citypay.com")
       end
     end
   end

data/spec/it_api_sandbox_spec.rb

@@ -0,0 +1,222 @@
+require 'spec_helper'
+require 'json'
+require 'date'
+require 'securerandom'
+require 'typhoeus'
+require 'base64'
+require_relative '../lib/citypay_api_client/utils/digest_utils'
+
+describe 'IntegrationTests' do
+
+  client_id = "PC222210"
+  licence_key = "SK5K1GQLI7USNET1"
+  merchant_id = "62421955"
+
+  before do
+
+    # for each test
+    CityPayApiClient.configure do |config|
+      config.api_key['cp-api-key'] = CityPayApiClient::ApiKey.new(client_id: client_id, licence_key: licence_key).generate
+      config.debugging = true
+      config.host = "sandbox.citypay.com"
+      config.server_index = 1
+    end
+    cha_api = CityPayApiClient::CardHolderAccountApi.new
+  end
+
+  after do
+    # eun after each test
+  end
+
+  describe 'Can run operational tests' do
+    api_instance = CityPayApiClient::OperationalFunctionsApi.new
+
+    it 'should ping and ack' do
+      uuid = SecureRandom.uuid
+      result = api_instance.ping_request(CityPayApiClient::Ping.new(identifier:  uuid))
+      expect(result.code).to eq("044")
+      expect(result.identifier).to eq(uuid)
+    end
+
+    it 'should list merchants' do
+      result = api_instance.list_merchants_request("default")
+      expect(result.clientid ).to eq(client_id)
+    end
+
+  end
+
+  describe 'Run payment processing tests' do
+    api_instance = CityPayApiClient::AuthorisationAndPaymentApi.new
+
+    it 'should authorise' do
+      uuid = SecureRandom.uuid
+      result = api_instance.authorisation_request(CityPayApiClient::AuthRequest.new(
+        merchantid: merchant_id,
+        cardnumber: "4000000000000002",
+        csc: "012",
+        expmonth: 12,
+        expyear: 2030,
+        amount: 1395,
+        identifier: uuid,
+        threedsecure: CityPayApiClient::ThreeDSecure.new(tds_policy: "2")
+      ))
+
+      expect(result.auth_response).to_not be_nil
+      expect(result.authen_required).to be_nil
+      expect(result.request_challenged).to be_nil
+
+      response = result.auth_response
+
+      expect(response.identifier).to eq(uuid.to_str)
+      expect(response.authcode).to eq("A12345")
+      expect(response.amount).to eq(1395)
+      expect(response.result_code).to eq("001")
+
+      expect(DigestUtils.validate_digest(response, licence_key)).to eq(true)
+    end
+
+  end
+
+  describe 'Run payment processing tests 3DSv2' do
+    api_instance = CityPayApiClient::AuthorisationAndPaymentApi.new
+
+    it 'should authorise 3DSv2' do
+      uuid = SecureRandom.uuid
+      result = api_instance.authorisation_request(CityPayApiClient::AuthRequest.new(
+        merchantid: merchant_id,
+        cardnumber: "4000000000000002",
+        csc: "123",
+        expmonth: 12,
+        expyear: 2030,
+        amount: 1396,
+        identifier: uuid,
+        trans_type: "A",
+        threedsecure: CityPayApiClient::ThreeDSecure.new(
+          cp_bx: "eyJhIjoiRkFwSCIsImMiOjI0LCJpIjoid3dIOTExTlBKSkdBRVhVZCIsImoiOmZhbHNlLCJsIjoiZW4tVVMiLCJoIjoxNDQwLCJ3IjoyNTYwLCJ0IjowLCJ1IjoiTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTFfMl8zKSBBcHBsZVdlYktpdC81MzcuMzYgKEtIVE1MLCBsaWtlIEdlY2tvKSBDaHJvbWUvODkuMC40Mzg5LjgyIFNhZmFyaS81MzcuMzYiLCJ2IjoiMS4wLjAifQ",
+          merchant_termurl: "https://citypay.com/acs/return"
+        )
+      ))
+
+      expect(result.auth_response).to be_nil
+      expect(result.authen_required).to be_nil
+      expect(result.request_challenged).to_not be_nil
+
+      response = result.request_challenged
+
+      expect(response.acs_url).to_not be_nil
+      expect(response.creq).to_not be_nil
+      expect(response.threedserver_trans_id).to_not be_nil
+
+      content = {
+        :threeDSSessionData => response.threedserver_trans_id,
+        :creq => response.creq
+      }
+
+      request = Typhoeus::Request.new("https://sandbox.citypay.com/3dsv2/acs",
+                                       method: :post,
+                                       headers: {
+                                         "Content-Type" => "application/json"
+                                       },
+                                       body: content.to_json)
+      res = request.run
+      c_res = res.response_body
+
+      expect(c_res['acsTransID']).to_not be_nil
+      expect(c_res['messageType']).to_not be_nil
+      expect(c_res['messageVersion']).to_not be_nil
+      expect(c_res['threeDSServerTransID']).to_not be_nil
+      expect(c_res['transStatus']).to_not be_nil
+
+      c_res_auth_request = CityPayApiClient::CResAuthRequest.new({:cres => Base64.encode64(c_res)})
+
+      c_res_request_response =  api_instance.c_res_request(c_res_auth_request)
+
+      expect(c_res_request_response.amount).to eq(1396)
+      expect(c_res_request_response.authcode).to eq("A12345")
+      expect(c_res_request_response.authen_result).to eq("Y")
+      expect(c_res_request_response.authorised).to eq(true)
+    end
+
+  end
+
+  describe 'Run card holder account actions' do
+
+    api_instance = CityPayApiClient::CardHolderAccountApi.new
+    cha_id = SecureRandom.hex(12)
+
+    it 'should create a new cha' do
+
+      result = api_instance.account_create(CityPayApiClient::AccountCreate.new(
+        account_id: cha_id,
+        contact: CityPayApiClient::ContactDetails.new(
+          address1: "7 Esplanade",
+          area: "St Helier",
+          company: "CityPay Limited",
+          country: "JE",
+          email: "dev@citypay.com",
+          firstname: "Integration",
+          lastname: "Test",
+          postcode: "JE2 3QA"
+        )
+      ))
+
+      expect(result.account_id).to eq(cha_id)
+      expect(result.contact.address1).to eq("7 Esplanade")
+
+    end
+
+    it 'should add a card to the account' do
+      result = api_instance.account_card_register_request(cha_id, CityPayApiClient::RegisterCard.new(
+        cardnumber: "4000000000000002",
+        expmonth: 12,
+        expyear: 2030,
+        ))
+      expect(result.account_id).to eq(cha_id)
+      expect(result.cards.length).to eq(1)
+      expect(result.cards[0].expmonth).to eq(12)
+      expect(result.cards[0].expyear).to eq(2030)
+
+    end
+
+    it 'should retrieve the account and charge against it' do
+      result = api_instance.account_retrieve_request(cha_id)
+      expect(result.account_id).to eq(cha_id)
+      expect(result.contact.address1).to eq("7 Esplanade")
+      expect(result.cards.length).to eq(1)
+      expect(result.cards[0].expmonth).to eq(12)
+      expect(result.cards[0].expyear).to eq(2030)
+
+      uuid = SecureRandom.uuid
+      result2 = api_instance.charge_request(CityPayApiClient::ChargeRequest.new(
+        amount: 7801,
+        csc: "012",
+        merchantid: merchant_id,
+        identifier: uuid,
+        threedsecure: CityPayApiClient::ThreeDSecure.new(tds_policy: "2"),
+        token: result.cards[0].token
+      ))
+
+      # decision object returned
+      expect(result2.auth_response).to_not be_nil
+      expect(result2.authen_required).to be_nil
+      expect(result2.request_challenged).to be_nil
+
+      response = result2.auth_response
+
+      expect(response.identifier).to eq(uuid.to_str)
+      expect(response.authcode).to eq("A12345")
+      expect(response.amount).to eq(7801)
+      expect(response.result_code).to eq("001")
+
+    end
+
+
+    it 'should delete the cha' do
+
+      result = api_instance.account_delete_request(cha_id)
+      expect(result.code).to eq("001")
+    end
+
+  end
+
+end

data/spec/models/acknowledgement_spec.rb

@@ -21,16 +21,14 @@ describe 'Acknowledgement' do
     # run before each test
     json = '
     {
-    "Acknowledgement": {
-        "code": "000",
-        "context": "1B12WmDZB3EYSbb",
-        "identifier": "testIdentifier",
-        "message": "System: Accepted Transaction"
+      "code": "000",
+      "context": "1B12WmDZB3EYSbb",
+      "identifier": "testIdentifier",
+      "message": "System: Accepted Transaction"
     }
-}
 '
-    data = JSON.parse(json, :symbolize_names => true)
-    @instance = CityPayApiClient::ApiClient.new.convert_to_type(data, "Acknowledgement")
+
+    @instance = CityPayApiClient::ApiClient.new.convert_to_type(JSON.parse(json, :symbolize_names => true), "Acknowledgement")
   end
 
   after do

data/spec/models/acl_check_request_spec.rb

@@ -0,0 +1,33 @@
+=begin
+#CityPay Payment API
+
+# 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. 
+
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.3.0-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for CityPayApiClient::AclCheckRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe CityPayApiClient::AclCheckRequest do
+  let(:instance) { CityPayApiClient::AclCheckRequest.new }
+
+  describe 'test an instance of AclCheckRequest' do
+    it 'should create an instance of AclCheckRequest' do
+      expect(instance).to be_instance_of(CityPayApiClient::AclCheckRequest)
+    end
+  end
+  describe 'test attribute "ip"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/acl_check_response_model_spec.rb

@@ -0,0 +1,51 @@
+=begin
+#CityPay Payment API
+
+# 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. 
+
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.3.0-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for CityPayApiClient::AclCheckResponseModel
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe CityPayApiClient::AclCheckResponseModel do
+  let(:instance) { CityPayApiClient::AclCheckResponseModel.new }
+
+  describe 'test an instance of AclCheckResponseModel' do
+    it 'should create an instance of AclCheckResponseModel' do
+      expect(instance).to be_instance_of(CityPayApiClient::AclCheckResponseModel)
+    end
+  end
+  describe 'test attribute "acl"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "cache"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "ip"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "provider"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/auth_references_spec.rb

@@ -20,13 +20,12 @@ describe 'AuthReferences' do
   before do
     # run before each test
 
-    json ='
+    json = '
     {
-    "AuthReferences": {
         "auths": [
             {
-                "amount": 12,
-                "amount_value": "0.12",
+                "amount": "0.12",
+                "amount_value": 12,
                 "atrn": null,
                 "authcode": "A12345",
                 "batchno": null,
@@ -41,8 +40,8 @@ describe 'AuthReferences' do
                 "transno": 88
             }
         ]
-    }
 }'
+
     data = JSON.parse(json, :symbolize_names => true)
     @instance = CityPayApiClient::ApiClient.new.convert_to_type(data, "AuthReferences")
   end
@@ -60,13 +59,13 @@ describe 'AuthReferences' do
     it 'should work' do
       expect(@instance.auths.length).to eq(1)
       i = @instance.auths[0]
-      expect(i.amount).to eq(12)
-      expect(i.amount_value).to eq("0.12")
+      expect(i.amount).to eq("0.12")
+      expect(i.amount_value).to eq(12)
       expect(i.atrn).to eq(nil)
       expect(i.authcode).to eq("A12345")
       expect(i.batchno).to eq(nil)
       expect(i.currency).to eq("GBP")
-      expect(i.datetime).to eq(DateTime.parse("2020-07-21T15:55:04Z"))
+      expect(i.datetime).to eq(Time.parse("2020-07-21T15:55:04Z"))
       expect(i.identifier).to eq("TestingAPI")
       expect(i.maskedpan).to eq("400000******0000")
       expect(i.merchantid).to eq(12345678)

data/spec/models/auth_response_spec.rb

@@ -19,37 +19,36 @@ require 'date'
 describe 'AuthResponse' do
   before do
     # run before each test
+
     json = '
 {
-    "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
-    }
+      "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
 }
 '
     data = JSON.parse(json, :symbolize_names => true)
@@ -151,7 +150,7 @@ describe 'AuthResponse' do
 
   describe 'test attribute "datetime"' do
     it 'should work' do
-      expect(@instance.datetime).to eq(DateTime.parse("2020-08-12T07:59:11Z"))
+      expect(@instance.datetime).to eq(Time.parse("2020-08-12T07:59:11Z"))
     end
   end
 

data/spec/models/batch_report_request_spec.rb

@@ -0,0 +1,39 @@
+=begin
+#CityPay Payment API
+
+# 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. 
+
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.3.0-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for CityPayApiClient::BatchReportRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe CityPayApiClient::BatchReportRequest do
+  let(:instance) { CityPayApiClient::BatchReportRequest.new }
+
+  describe 'test an instance of BatchReportRequest' do
+    it 'should create an instance of BatchReportRequest' do
+      expect(instance).to be_instance_of(CityPayApiClient::BatchReportRequest)
+    end
+  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
+    end
+  end
+
+  describe 'test attribute "batch_id"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/batch_report_response_model_spec.rb

@@ -0,0 +1,63 @@
+=begin
+#CityPay Payment API
+
+# 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. 
+
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.3.0-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for CityPayApiClient::BatchReportResponseModel
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe CityPayApiClient::BatchReportResponseModel do
+  let(:instance) { CityPayApiClient::BatchReportResponseModel.new }
+
+  describe 'test an instance of BatchReportResponseModel' do
+    it 'should create an instance of BatchReportResponseModel' do
+      expect(instance).to be_instance_of(CityPayApiClient::BatchReportResponseModel)
+    end
+  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
+    end
+  end
+
+  describe 'test attribute "amount"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "batch_date"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "batch_id"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "batch_status"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "transactions"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end