citypay_api_client 1.1.1 → 1.1.3

data/lib/citypay_api_client/version.rb

@@ -1,14 +1,14 @@
 =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 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. 
+# Welcome to the CityPay API, a robust HTTP API payment solution designed for seamless server-to-server  transactional processing. Our API facilitates a wide array of payment operations, catering to diverse business needs.  Whether you're integrating Internet payments, handling Mail Order/Telephone Order (MOTO) transactions, managing  Subscriptions with Recurring and Continuous Authority payments, or navigating the complexities of 3-D Secure  authentication, our API is equipped to support your requirements. Additionally, we offer functionalities for  Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids, and Completion processing, alongside the capability  for tokenised payments.  ## Compliance and Security Overview <aside class=\"notice\">   Ensuring the security of payment transactions and compliance with industry standards is paramount. Our API is    designed with stringent security measures and compliance protocols to safeguard sensitive information and meet    the rigorous requirements of Visa, MasterCard, and the PCI Security Standards Council. </aside>  ### Key Compliance and Security Measures  * **TLS Encryption**: All data transmissions must utilise TLS version 1.2 or higher, employing [strong cryptography](#enabled-tls-ciphers). Our infrastructure strictly enforces this requirement to maintain the integrity and confidentiality of data in transit. We conduct regular scans and assessments of our TLS endpoints to identify and mitigate vulnerabilities. * **Data Storage Prohibitions**: Storing sensitive cardholder data (CHD), such as the card security code (CSC) or primary account number (PAN), is strictly prohibited. Our API is designed to minimize your exposure to sensitive data, thereby reducing your compliance burden. * **Data Masking**: For consumer protection and compliance, full card numbers must not be displayed on receipts or any customer-facing materials. Our API automatically masks PANs, displaying only the last four digits to facilitate safe receipt generation. * **Network Scans**: If your application is web-based, regular scans of your hosting environment are mandatory to identify and rectify potential vulnerabilities. This proactive measure is crucial for maintaining a secure and compliant online presence. * **PCI Compliance**: Adherence to PCI DSS standards is not optional; it's a requirement for operating securely and legally in the payments ecosystem. For detailed information on compliance requirements and resources, please visit the PCI Security Standards Council website [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/). * **Request Validation**: Our API includes mechanisms to verify the legitimacy of each request, ensuring it pertains to a valid account and originates from a trusted source. We leverage remote IP address verification alongside sophisticated application firewall technologies to thwart a wide array of common security threats.  ## Getting Started Before integrating with the CityPay API, ensure your application and development practices align with the outlined compliance and security measures. This preparatory step is crucial for a smooth integration process and the long-term success of your payment processing operations.  For further details on API endpoints, request/response formats, and code examples, proceed to the subsequent sections of our documentation. Our aim is to provide you with all the necessary tools and information to integrate our payment processing capabilities seamlessly into your application.  Thank you for choosing CityPay API. We look forward to supporting your payment processing needs with our secure, compliant, and versatile API solution. 
 
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.2.1
+OpenAPI Generator version: 7.2.0
 
 =end
 
 module CityPayApiClient
-  VERSION = '1.1.1'
+  VERSION = '1.1.3'
 end

data/lib/citypay_api_client.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 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. 
+# Welcome to the CityPay API, a robust HTTP API payment solution designed for seamless server-to-server  transactional processing. Our API facilitates a wide array of payment operations, catering to diverse business needs.  Whether you're integrating Internet payments, handling Mail Order/Telephone Order (MOTO) transactions, managing  Subscriptions with Recurring and Continuous Authority payments, or navigating the complexities of 3-D Secure  authentication, our API is equipped to support your requirements. Additionally, we offer functionalities for  Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids, and Completion processing, alongside the capability  for tokenised payments.  ## Compliance and Security Overview <aside class=\"notice\">   Ensuring the security of payment transactions and compliance with industry standards is paramount. Our API is    designed with stringent security measures and compliance protocols to safeguard sensitive information and meet    the rigorous requirements of Visa, MasterCard, and the PCI Security Standards Council. </aside>  ### Key Compliance and Security Measures  * **TLS Encryption**: All data transmissions must utilise TLS version 1.2 or higher, employing [strong cryptography](#enabled-tls-ciphers). Our infrastructure strictly enforces this requirement to maintain the integrity and confidentiality of data in transit. We conduct regular scans and assessments of our TLS endpoints to identify and mitigate vulnerabilities. * **Data Storage Prohibitions**: Storing sensitive cardholder data (CHD), such as the card security code (CSC) or primary account number (PAN), is strictly prohibited. Our API is designed to minimize your exposure to sensitive data, thereby reducing your compliance burden. * **Data Masking**: For consumer protection and compliance, full card numbers must not be displayed on receipts or any customer-facing materials. Our API automatically masks PANs, displaying only the last four digits to facilitate safe receipt generation. * **Network Scans**: If your application is web-based, regular scans of your hosting environment are mandatory to identify and rectify potential vulnerabilities. This proactive measure is crucial for maintaining a secure and compliant online presence. * **PCI Compliance**: Adherence to PCI DSS standards is not optional; it's a requirement for operating securely and legally in the payments ecosystem. For detailed information on compliance requirements and resources, please visit the PCI Security Standards Council website [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/). * **Request Validation**: Our API includes mechanisms to verify the legitimacy of each request, ensuring it pertains to a valid account and originates from a trusted source. We leverage remote IP address verification alongside sophisticated application firewall technologies to thwart a wide array of common security threats.  ## Getting Started Before integrating with the CityPay API, ensure your application and development practices align with the outlined compliance and security measures. This preparatory step is crucial for a smooth integration process and the long-term success of your payment processing operations.  For further details on API endpoints, request/response formats, and code examples, proceed to the subsequent sections of our documentation. Our aim is to provide you with all the necessary tools and information to integrate our payment processing capabilities seamlessly into your application.  Thank you for choosing CityPay API. We look forward to supporting your payment processing needs with our secure, compliant, and versatile API solution. 
 
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.2.1
+OpenAPI Generator version: 7.2.0
 
 =end
 
@@ -28,11 +28,12 @@ require 'citypay_api_client/models/auth_reference'
 require 'citypay_api_client/models/auth_references'
 require 'citypay_api_client/models/auth_request'
 require 'citypay_api_client/models/auth_response'
-require 'citypay_api_client/models/authen_required'
 require 'citypay_api_client/models/batch'
 require 'citypay_api_client/models/batch_report_request'
 require 'citypay_api_client/models/batch_report_response_model'
 require 'citypay_api_client/models/batch_transaction'
+require 'citypay_api_client/models/batch_transaction_report_request'
+require 'citypay_api_client/models/batch_transaction_report_response'
 require 'citypay_api_client/models/batch_transaction_result_model'
 require 'citypay_api_client/models/bin'
 require 'citypay_api_client/models/bin_lookup'
@@ -58,6 +59,10 @@ require 'citypay_api_client/models/external_mpi'
 require 'citypay_api_client/models/list_merchants_response'
 require 'citypay_api_client/models/mcc6012'
 require 'citypay_api_client/models/merchant'
+require 'citypay_api_client/models/merchant_batch_report_request'
+require 'citypay_api_client/models/merchant_batch_report_response'
+require 'citypay_api_client/models/merchant_batch_response'
+require 'citypay_api_client/models/net_summary_response'
 require 'citypay_api_client/models/pa_res_auth_request'
 require 'citypay_api_client/models/paylink_address'
 require 'citypay_api_client/models/paylink_adjustment_request'
@@ -73,6 +78,7 @@ require 'citypay_api_client/models/paylink_email_notification_path'
 require 'citypay_api_client/models/paylink_error_code'
 require 'citypay_api_client/models/paylink_field_guard_model'
 require 'citypay_api_client/models/paylink_part_payments'
+require 'citypay_api_client/models/paylink_resend_notification_request'
 require 'citypay_api_client/models/paylink_sms_notification_path'
 require 'citypay_api_client/models/paylink_state_event'
 require 'citypay_api_client/models/paylink_token_created'
@@ -81,11 +87,17 @@ require 'citypay_api_client/models/paylink_token_status'
 require 'citypay_api_client/models/paylink_token_status_change_request'
 require 'citypay_api_client/models/paylink_token_status_change_response'
 require 'citypay_api_client/models/paylink_ui'
+require 'citypay_api_client/models/payment_intent'
+require 'citypay_api_client/models/payment_intent_reference'
 require 'citypay_api_client/models/ping'
 require 'citypay_api_client/models/process_batch_request'
 require 'citypay_api_client/models/process_batch_response'
 require 'citypay_api_client/models/refund_request'
 require 'citypay_api_client/models/register_card'
+require 'citypay_api_client/models/remittance_data'
+require 'citypay_api_client/models/remittance_report_request'
+require 'citypay_api_client/models/remittance_report_response'
+require 'citypay_api_client/models/remitted_client_data'
 require 'citypay_api_client/models/request_challenged'
 require 'citypay_api_client/models/retrieve_request'
 require 'citypay_api_client/models/three_d_secure'
@@ -99,6 +111,7 @@ require 'citypay_api_client/api/card_holder_account_api__'
 require 'citypay_api_client/api/direct_post_api__'
 require 'citypay_api_client/api/operational_functions_api__'
 require 'citypay_api_client/api/paylink_api__'
+require 'citypay_api_client/api/reporting_api__'
 
 module CityPayApiClient
   class << self

data/spec/api/reporting_api___spec.rb

@@ -0,0 +1,99 @@
+=begin
+#CityPay Payment API
+
+# Welcome to the CityPay API, a robust HTTP API payment solution designed for seamless server-to-server  transactional processing. Our API facilitates a wide array of payment operations, catering to diverse business needs.  Whether you're integrating Internet payments, handling Mail Order/Telephone Order (MOTO) transactions, managing  Subscriptions with Recurring and Continuous Authority payments, or navigating the complexities of 3-D Secure  authentication, our API is equipped to support your requirements. Additionally, we offer functionalities for  Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids, and Completion processing, alongside the capability  for tokenised payments.  ## Compliance and Security Overview <aside class=\"notice\">   Ensuring the security of payment transactions and compliance with industry standards is paramount. Our API is    designed with stringent security measures and compliance protocols to safeguard sensitive information and meet    the rigorous requirements of Visa, MasterCard, and the PCI Security Standards Council. </aside>  ### Key Compliance and Security Measures  * **TLS Encryption**: All data transmissions must utilise TLS version 1.2 or higher, employing [strong cryptography](#enabled-tls-ciphers). Our infrastructure strictly enforces this requirement to maintain the integrity and confidentiality of data in transit. We conduct regular scans and assessments of our TLS endpoints to identify and mitigate vulnerabilities. * **Data Storage Prohibitions**: Storing sensitive cardholder data (CHD), such as the card security code (CSC) or primary account number (PAN), is strictly prohibited. Our API is designed to minimize your exposure to sensitive data, thereby reducing your compliance burden. * **Data Masking**: For consumer protection and compliance, full card numbers must not be displayed on receipts or any customer-facing materials. Our API automatically masks PANs, displaying only the last four digits to facilitate safe receipt generation. * **Network Scans**: If your application is web-based, regular scans of your hosting environment are mandatory to identify and rectify potential vulnerabilities. This proactive measure is crucial for maintaining a secure and compliant online presence. * **PCI Compliance**: Adherence to PCI DSS standards is not optional; it's a requirement for operating securely and legally in the payments ecosystem. For detailed information on compliance requirements and resources, please visit the PCI Security Standards Council website [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/). * **Request Validation**: Our API includes mechanisms to verify the legitimacy of each request, ensuring it pertains to a valid account and originates from a trusted source. We leverage remote IP address verification alongside sophisticated application firewall technologies to thwart a wide array of common security threats.  ## Getting Started Before integrating with the CityPay API, ensure your application and development practices align with the outlined compliance and security measures. This preparatory step is crucial for a smooth integration process and the long-term success of your payment processing operations.  For further details on API endpoints, request/response formats, and code examples, proceed to the subsequent sections of our documentation. Our aim is to provide you with all the necessary tools and information to integrate our payment processing capabilities seamlessly into your application.  Thank you for choosing CityPay API. We look forward to supporting your payment processing needs with our secure, compliant, and versatile API solution. 
+
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 7.2.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for CityPayApiClient::ReportingApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'ReportingApi' do
+  before do
+    # run before each test
+    @api_instance = CityPayApiClient::ReportingApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of ReportingApi' do
+    it 'should create an instance of ReportingApi' do
+      expect(@api_instance).to be_instance_of(CityPayApiClient::ReportingApi)
+    end
+  end
+
+  # unit tests for batched_transaction_report_request
+  # Batch Transaction Report Request
+  # Retrieves transactions available on a given batch.
+  # @param merchantid A merchant ID (MID) for which data is requested. This field allows for filtering of the request by a specific merchant account.
+  # @param batch_no The batch number that is being requested.
+  # @param batch_transaction_report_request 
+  # @param [Hash] opts the optional parameters
+  # @return [BatchTransactionReportResponse]
+  describe 'batched_transaction_report_request test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for merchant_batch_report_request
+  # Merchant Batch Report Request
+  # Retrieves a report of merchant batches within a specified date range.  Batches, which aggregate daily processing activities, are typically generated at &#x60;00:00&#x60; each day.  These batches play a crucial role in the settlement of funds by summarising daily transactions. 
+  # @param merchant_batch_report_request 
+  # @param [Hash] opts the optional parameters
+  # @return [MerchantBatchReportResponse]
+  describe 'merchant_batch_report_request test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for merchant_batch_request
+  # Merchant Batch Request
+  # Retrieves a report of merchant a merchant batch for a specified batch number.
+  # @param merchantid A merchant ID (MID) for which data is requested. This field allows for filtering of the request by a specific merchant account.
+  # @param batch_no The batch number that is being requested.
+  # @param [Hash] opts the optional parameters
+  # @return [MerchantBatchResponse]
+  describe 'merchant_batch_request test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for remittance_range_report
+  # Remittance Report Request
+  # Fetches remittance reports for financial transactions within a specified date range, covering all client-related activities. This report consolidates all batches disbursed to a client, with each remittance summarising the aggregation of batches leading up to settlement. Additionally, the net remittance amount presented in the final settlement will reflect any deductions made by the acquirer. 
+  # @param clientid A client Id for which data is requested.
+  # @param remittance_report_request 
+  # @param [Hash] opts the optional parameters
+  # @return [RemittanceReportResponse]
+  describe 'remittance_range_report test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for remittance_report_request
+  # Remittance Date Report Request
+  # Fetches remittance reports for financial transactions for a given date,  covering all client-related activities. This report consolidates all batches disbursed to a  client, with each remittance summarising the aggregation of batches leading up to settlement.  Additionally, the net remittance amount presented in the final settlement will reflect any  deductions made by the acquirer.  The process also supports the notion of *today* deferring the date to today&#39;s date or *latest* reflecting the latest remittance date available. 
+  # @param clientid A client Id for which data is requested.
+  # @param date Date (YYYY-MM-DD) to filter the request for.
+  # @param [Hash] opts the optional parameters
+  # @return [RemittedClientData]
+  describe 'remittance_report_request test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/it_api_sandbox_spec.rb

@@ -8,9 +8,9 @@ require_relative '../lib/citypay_api_client/utils/digest_utils'
 
 describe 'IntegrationTests' do
 
-  client_id = "PC222210"
-  licence_key = "SK5K1GQLI7USNET1"
-  merchant_id = "62421955"
+  client_id = ENV['CP_CLIENT_ID']
+  licence_key = ENV['CP_LICENCE_KEY']
+  merchant_id = ENV['CP_MERCHANT_ID']
 
   before do
 
@@ -62,7 +62,6 @@ describe 'IntegrationTests' do
       ))
 
       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
@@ -98,7 +97,6 @@ describe 'IntegrationTests' do
       ))
 
       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
@@ -120,14 +118,8 @@ describe 'IntegrationTests' do
                                        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)})
+      object = JSON.parse(c_res)
+      c_res_auth_request = CityPayApiClient::CResAuthRequest.new({:cres => object['cres']})
 
       c_res_request_response =  api_instance.c_res_request(c_res_auth_request)
 
@@ -198,7 +190,6 @@ describe 'IntegrationTests' do
 
       # 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

data/spec/models/account_create_spec.rb

@@ -19,7 +19,6 @@ require 'date'
 describe 'AccountCreate' do
   before do
     # run before each test
-    @instance = CityPayApiClient::AccountCreate.new
   end
 
   after do
@@ -28,7 +27,7 @@ describe 'AccountCreate' do
 
   describe 'test an instance of AccountCreate' do
     it 'should create an instance of AccountCreate' do
-      expect(@instance).to be_instance_of(CityPayApiClient::AccountCreate)
+
     end
   end
   describe 'test attribute "account_id"' do

data/spec/models/account_status_spec.rb

@@ -19,7 +19,7 @@ require 'date'
 describe 'AccountStatus' do
   before do
     # run before each test
-    @instance = CityPayApiClient::AccountStatus.new
+
   end
 
   after do
@@ -28,7 +28,7 @@ describe 'AccountStatus' do
 
   describe 'test an instance of AccountStatus' do
     it 'should create an instance of AccountStatus' do
-      expect(@instance).to be_instance_of(CityPayApiClient::AccountStatus)
+
     end
   end
   describe 'test attribute "status"' do

data/spec/models/airline_advice_spec.rb

@@ -19,7 +19,6 @@ require 'date'
 describe 'AirlineAdvice' do
   before do
     # run before each test
-    @instance = CityPayApiClient::AirlineAdvice.new
   end
 
   after do
@@ -28,7 +27,6 @@ describe 'AirlineAdvice' do
 
   describe 'test an instance of AirlineAdvice' do
     it 'should create an instance of AirlineAdvice' do
-      expect(@instance).to be_instance_of(CityPayApiClient::AirlineAdvice)
     end
   end
   describe 'test attribute "carrier_name"' do

data/spec/models/airline_segment_spec.rb

@@ -19,7 +19,6 @@ require 'date'
 describe 'AirlineSegment' do
   before do
     # run before each test
-    @instance = CityPayApiClient::AirlineSegment.new
   end
 
   after do
@@ -28,7 +27,6 @@ describe 'AirlineSegment' do
 
   describe 'test an instance of AirlineSegment' do
     it 'should create an instance of AirlineSegment' do
-      expect(@instance).to be_instance_of(CityPayApiClient::AirlineSegment)
     end
   end
   describe 'test attribute "arrival_location_code"' do

data/spec/models/auth_request_spec.rb

@@ -19,7 +19,6 @@ require 'date'
 describe 'AuthRequest' do
   before do
     # run before each test
-    @instance = CityPayApiClient::AuthRequest.new
   end
 
   after do
@@ -28,7 +27,6 @@ describe 'AuthRequest' do
 
   describe 'test an instance of AuthRequest' do
     it 'should create an instance of AuthRequest' do
-      expect(@instance).to be_instance_of(CityPayApiClient::AuthRequest)
     end
   end
   describe 'test attribute "airline_data"' do

data/spec/models/auth_response_spec.rb

@@ -21,38 +21,71 @@ describe 'AuthResponse' do
     # run before each test
 
     json = '
-{
-      "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
+        }'
+
+    json_no_ident = '
+        {
+          "amount": 0,
+          "atrn": "",
+          "atsd": "",
+          "authcode": "",
+          "authen_result": "",
+          "authorised": false,
+          "avs_result": " ",
+          "bin_commercial": false,
+          "bin_debit": false,
+          "bin_description": "",
+          "cavv": "",
+          "context": "PC.0.A5298ef695b",
+          "csc_result": " ",
+          "currency": "---",
+          "datetime": "1969-12-31T23:59:59Z",
+          "eci": "0",
+          "identifier": "",
+          "live": true,
+          "maskedpan": "N/A",
+          "merchantid": 0,
+          "result": 3,
+          "result_code": "P030",
+          "result_message": "Request Error: Authorisation invalid (203: Data element not in the required format or value is invalid as defined in Table A.1. threeDSSessionData)",
+          "scheme": "",
+          "sha256": "",
+          "trans_status": "_",
+          "transno": -1
+        }'
+
     data = JSON.parse(json, :symbolize_names => true)
+    data_not_ident = JSON.parse(json_no_ident, :symbolize_names => true)
     @instance = CityPayApiClient::ApiClient.new.convert_to_type(data, "AuthResponse")
+    @instance_not_ident = CityPayApiClient::ApiClient.new.convert_to_type(data_not_ident, "AuthResponse")
   end
 
   after do
@@ -226,4 +259,16 @@ describe 'AuthResponse' do
     end
   end
 
+  describe 'test attribute "result_code"' do
+    it 'should work' do
+      expect(@instance_not_ident.result_code).to eq("P030")
+    end
+  end
+
+  describe 'test attribute "result"' do
+    it 'should work' do
+      expect(@instance_not_ident.result).to eq(3)
+    end
+  end
+
 end

data/spec/models/batch_report_request_spec.rb

@@ -17,11 +17,9 @@ require 'date'
 # 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

data/spec/models/batch_report_response_model_spec.rb

@@ -17,11 +17,9 @@ require 'date'
 # 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

data/spec/models/batch_spec.rb

@@ -17,11 +17,9 @@ require 'date'
 # Automatically generated by openapi-generator (https://openapi-generator.tech)
 # Please update as you see appropriate
 describe CityPayApiClient::Batch do
-  let(:instance) { CityPayApiClient::Batch.new }
 
   describe 'test an instance of Batch' do
     it 'should create an instance of Batch' do
-      expect(instance).to be_instance_of(CityPayApiClient::Batch)
     end
   end
   describe 'test attribute "batch_date"' do

data/spec/models/batch_transaction_report_request_spec.rb

@@ -0,0 +1,47 @@
+=begin
+#CityPay Payment API
+
+# Welcome to the CityPay API, a robust HTTP API payment solution designed for seamless server-to-server  transactional processing. Our API facilitates a wide array of payment operations, catering to diverse business needs.  Whether you're integrating Internet payments, handling Mail Order/Telephone Order (MOTO) transactions, managing  Subscriptions with Recurring and Continuous Authority payments, or navigating the complexities of 3-D Secure  authentication, our API is equipped to support your requirements. Additionally, we offer functionalities for  Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids, and Completion processing, alongside the capability  for tokenised payments.  ## Compliance and Security Overview <aside class=\"notice\">   Ensuring the security of payment transactions and compliance with industry standards is paramount. Our API is    designed with stringent security measures and compliance protocols to safeguard sensitive information and meet    the rigorous requirements of Visa, MasterCard, and the PCI Security Standards Council. </aside>  ### Key Compliance and Security Measures  * **TLS Encryption**: All data transmissions must utilise TLS version 1.2 or higher, employing [strong cryptography](#enabled-tls-ciphers). Our infrastructure strictly enforces this requirement to maintain the integrity and confidentiality of data in transit. We conduct regular scans and assessments of our TLS endpoints to identify and mitigate vulnerabilities. * **Data Storage Prohibitions**: Storing sensitive cardholder data (CHD), such as the card security code (CSC) or primary account number (PAN), is strictly prohibited. Our API is designed to minimize your exposure to sensitive data, thereby reducing your compliance burden. * **Data Masking**: For consumer protection and compliance, full card numbers must not be displayed on receipts or any customer-facing materials. Our API automatically masks PANs, displaying only the last four digits to facilitate safe receipt generation. * **Network Scans**: If your application is web-based, regular scans of your hosting environment are mandatory to identify and rectify potential vulnerabilities. This proactive measure is crucial for maintaining a secure and compliant online presence. * **PCI Compliance**: Adherence to PCI DSS standards is not optional; it's a requirement for operating securely and legally in the payments ecosystem. For detailed information on compliance requirements and resources, please visit the PCI Security Standards Council website [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/). * **Request Validation**: Our API includes mechanisms to verify the legitimacy of each request, ensuring it pertains to a valid account and originates from a trusted source. We leverage remote IP address verification alongside sophisticated application firewall technologies to thwart a wide array of common security threats.  ## Getting Started Before integrating with the CityPay API, ensure your application and development practices align with the outlined compliance and security measures. This preparatory step is crucial for a smooth integration process and the long-term success of your payment processing operations.  For further details on API endpoints, request/response formats, and code examples, proceed to the subsequent sections of our documentation. Our aim is to provide you with all the necessary tools and information to integrate our payment processing capabilities seamlessly into your application.  Thank you for choosing CityPay API. We look forward to supporting your payment processing needs with our secure, compliant, and versatile API solution. 
+
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 7.2.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for CityPayApiClient::BatchTransactionReportRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe CityPayApiClient::BatchTransactionReportRequest do
+  let(:instance) { CityPayApiClient::BatchTransactionReportRequest.new }
+
+  describe 'test an instance of BatchTransactionReportRequest' do
+    it 'should create an instance of BatchTransactionReportRequest' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(CityPayApiClient::BatchTransactionReportRequest)
+    end
+  end
+
+  describe 'test attribute "max_results"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "next_token"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "order_by"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/batch_transaction_report_response_spec.rb

@@ -0,0 +1,53 @@
+=begin
+#CityPay Payment API
+
+# Welcome to the CityPay API, a robust HTTP API payment solution designed for seamless server-to-server  transactional processing. Our API facilitates a wide array of payment operations, catering to diverse business needs.  Whether you're integrating Internet payments, handling Mail Order/Telephone Order (MOTO) transactions, managing  Subscriptions with Recurring and Continuous Authority payments, or navigating the complexities of 3-D Secure  authentication, our API is equipped to support your requirements. Additionally, we offer functionalities for  Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids, and Completion processing, alongside the capability  for tokenised payments.  ## Compliance and Security Overview <aside class=\"notice\">   Ensuring the security of payment transactions and compliance with industry standards is paramount. Our API is    designed with stringent security measures and compliance protocols to safeguard sensitive information and meet    the rigorous requirements of Visa, MasterCard, and the PCI Security Standards Council. </aside>  ### Key Compliance and Security Measures  * **TLS Encryption**: All data transmissions must utilise TLS version 1.2 or higher, employing [strong cryptography](#enabled-tls-ciphers). Our infrastructure strictly enforces this requirement to maintain the integrity and confidentiality of data in transit. We conduct regular scans and assessments of our TLS endpoints to identify and mitigate vulnerabilities. * **Data Storage Prohibitions**: Storing sensitive cardholder data (CHD), such as the card security code (CSC) or primary account number (PAN), is strictly prohibited. Our API is designed to minimize your exposure to sensitive data, thereby reducing your compliance burden. * **Data Masking**: For consumer protection and compliance, full card numbers must not be displayed on receipts or any customer-facing materials. Our API automatically masks PANs, displaying only the last four digits to facilitate safe receipt generation. * **Network Scans**: If your application is web-based, regular scans of your hosting environment are mandatory to identify and rectify potential vulnerabilities. This proactive measure is crucial for maintaining a secure and compliant online presence. * **PCI Compliance**: Adherence to PCI DSS standards is not optional; it's a requirement for operating securely and legally in the payments ecosystem. For detailed information on compliance requirements and resources, please visit the PCI Security Standards Council website [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/). * **Request Validation**: Our API includes mechanisms to verify the legitimacy of each request, ensuring it pertains to a valid account and originates from a trusted source. We leverage remote IP address verification alongside sophisticated application firewall technologies to thwart a wide array of common security threats.  ## Getting Started Before integrating with the CityPay API, ensure your application and development practices align with the outlined compliance and security measures. This preparatory step is crucial for a smooth integration process and the long-term success of your payment processing operations.  For further details on API endpoints, request/response formats, and code examples, proceed to the subsequent sections of our documentation. Our aim is to provide you with all the necessary tools and information to integrate our payment processing capabilities seamlessly into your application.  Thank you for choosing CityPay API. We look forward to supporting your payment processing needs with our secure, compliant, and versatile API solution. 
+
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 7.2.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for CityPayApiClient::BatchTransactionReportResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe CityPayApiClient::BatchTransactionReportResponse do
+  let(:instance) { CityPayApiClient::BatchTransactionReportResponse.new }
+
+  describe 'test an instance of BatchTransactionReportResponse' do
+    it 'should create an instance of BatchTransactionReportResponse' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(CityPayApiClient::BatchTransactionReportResponse)
+    end
+  end
+
+  describe 'test attribute "count"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "max_results"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "next_token"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end