citypay_api_client 1.0.3 → 1.1.2

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/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_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_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

@@ -19,41 +19,73 @@ 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
+        }'
+
+    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
@@ -151,7 +183,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
 
@@ -227,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

@@ -0,0 +1,37 @@
+=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
+
+  describe 'test an instance of BatchReportRequest' do
+    it 'should create an instance of BatchReportRequest' do
+    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,61 @@
+=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
+
+  describe 'test an instance of BatchReportResponseModel' do
+    it 'should create an instance of BatchReportResponseModel' do
+    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

data/spec/models/batch_spec.rb

@@ -0,0 +1,43 @@
+=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::Batch
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe CityPayApiClient::Batch do
+
+  describe 'test an instance of Batch' do
+    it 'should create an instance of Batch' do
+    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
+
+end

data/spec/models/batch_transaction_result_model_spec.rb

@@ -0,0 +1,85 @@
+=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::BatchTransactionResultModel
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe CityPayApiClient::BatchTransactionResultModel do
+
+  describe 'test an instance of BatchTransactionResultModel' do
+    it 'should create an instance of BatchTransactionResultModel' do
+    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 "authcode"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "authorised"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "identifier"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "maskedpan"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "merchantid"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "message"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "result"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "scheme"' 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_transaction_spec.rb

@@ -0,0 +1,49 @@
+=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::BatchTransaction
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe CityPayApiClient::BatchTransaction do
+
+  describe 'test an instance of BatchTransaction' do
+    it 'should create an instance of BatchTransaction' do
+    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 "identifier"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "merchantid"' 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/bin_lookup_spec.rb

@@ -0,0 +1,31 @@
+=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::BinLookup
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe CityPayApiClient::BinLookup do
+
+  describe 'test an instance of BinLookup' do
+    it 'should create an instance of BinLookup' do
+    end
+  end
+  describe 'test attribute "bin"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end