citypay_api_client 1.0.0

data/spec/models/request_challenged_spec.rb

@@ -0,0 +1,65 @@
+=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. 
+
+The version of the OpenAPI document: 6.0.0
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.0.0-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for CityPayApiClient::RequestChallenged
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'RequestChallenged' do
+  before do
+    # run before each test
+    @instance = CityPayApiClient::RequestChallenged.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of RequestChallenged' do
+    it 'should create an instance of RequestChallenged' do
+      expect(@instance).to be_instance_of(CityPayApiClient::RequestChallenged)
+    end
+  end
+  describe 'test attribute "acs_url"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "creq"' 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 "three_d_server_trans_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 "transno"' 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/retrieve_request_spec.rb

@@ -0,0 +1,53 @@
+=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. 
+
+The version of the OpenAPI document: 6.0.0
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.0.0-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for CityPayApiClient::RetrieveRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'RetrieveRequest' do
+  before do
+    # run before each test
+    @instance = CityPayApiClient::RetrieveRequest.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of RetrieveRequest' do
+    it 'should create an instance of RetrieveRequest' do
+      expect(@instance).to be_instance_of(CityPayApiClient::RetrieveRequest)
+    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
+
+  describe 'test attribute "transno"' 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/three_d_secure_spec.rb

@@ -0,0 +1,65 @@
+=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. 
+
+The version of the OpenAPI document: 6.0.0
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.0.0-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for CityPayApiClient::ThreeDSecure
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'ThreeDSecure' do
+  before do
+    # run before each test
+    @instance = CityPayApiClient::ThreeDSecure.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of ThreeDSecure' do
+    it 'should create an instance of ThreeDSecure' do
+      expect(@instance).to be_instance_of(CityPayApiClient::ThreeDSecure)
+    end
+  end
+  describe 'test attribute "accept_headers"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "downgrade1"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "merchant_termurl"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "tds_policy"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "user_agent"' 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/void_request_spec.rb

@@ -0,0 +1,59 @@
+=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. 
+
+The version of the OpenAPI document: 6.0.0
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.0.0-SNAPSHOT
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for CityPayApiClient::VoidRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'VoidRequest' do
+  before do
+    # run before each test
+    @instance = CityPayApiClient::VoidRequest.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of VoidRequest' do
+    it 'should create an instance of VoidRequest' do
+      expect(@instance).to be_instance_of(CityPayApiClient::VoidRequest)
+    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
+
+  describe 'test attribute "sdk"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "transno"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/spec_helper.rb

@@ -0,0 +1,111 @@
+=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. 
+
+The version of the OpenAPI document: 6.0.0
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.0.0-SNAPSHOT
+
+=end
+
+# load the gem
+require 'citypay_api_client'
+
+# The following  was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# The `.rspec` file also contains a few flags that are not defaults but that
+# users commonly want.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # These two settings work together to allow you to limit a spec run
+  # to individual examples or groups you care about by tagging them with
+  # `:focus` metadata. When nothing is tagged with `:focus`, all examples
+  # get run.
+  config.filter_run :focus
+  config.run_all_when_everything_filtered = true
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  config.example_status_persistence_file_path = "spec/examples.txt"
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
+  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
+  config.disable_monkey_patching!
+
+  # This setting enables warnings. It's recommended, but in some cases may
+  # be too noisy due to issues in dependencies.
+  config.warnings = true
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = 'doc'
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+=end
+end

metadata

@@ -0,0 +1,252 @@
+--- !ruby/object:Gem::Specification
+name: citypay_api_client
+version: !ruby/object:Gem::Version
+  version: 1.0.0
+platform: ruby
+authors:
+- citypay
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2020-08-03 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: typhoeus
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.0.1
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.0.1
+- !ruby/object:Gem::Dependency
+  name: json
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.1.0
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.1'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.1.0
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.1'
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 3.6.0
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.6'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 3.6.0
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.6'
+description: CityPay API Client for Ruby
+email:
+- support@citypay.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- Gemfile
+- README.md
+- Rakefile
+- citypay_api_client.gemspec
+- docs/AccountCreate.md
+- docs/AccountStatus.md
+- docs/Acknowledgement.md
+- docs/AirlineAdvice.md
+- docs/AirlineSegment.md
+- docs/AuthReference.md
+- docs/AuthReferences.md
+- docs/AuthRequest.md
+- docs/AuthResponse.md
+- docs/AuthenRequired.md
+- docs/CResAuthRequest.md
+- docs/CaptureRequest.md
+- docs/Card.md
+- docs/CardHolderAccount.md
+- docs/CardHolderAccountApi.md
+- docs/CardStatus.md
+- docs/ChargeRequest.md
+- docs/ContactDetails.md
+- docs/Decision.md
+- docs/Error.md
+- docs/ExternalMPI.md
+- docs/ListMerchantsResponse.md
+- docs/MCC6012.md
+- docs/Merchant.md
+- docs/OperationalApi.md
+- docs/PaResAuthRequest.md
+- docs/PaymentProcessingApi.md
+- docs/Ping.md
+- docs/RegisterCard.md
+- docs/RequestChallenged.md
+- docs/RetrieveRequest.md
+- docs/ThreeDSecure.md
+- docs/VoidRequest.md
+- git_push.sh
+- lib/citypay_api_client.rb
+- lib/citypay_api_client/api/card_holder_account_api.rb
+- lib/citypay_api_client/api/operational_api.rb
+- lib/citypay_api_client/api/payment_processing_api.rb
+- lib/citypay_api_client/api_client.rb
+- lib/citypay_api_client/api_error.rb
+- lib/citypay_api_client/configuration.rb
+- lib/citypay_api_client/models/account_create.rb
+- lib/citypay_api_client/models/account_status.rb
+- lib/citypay_api_client/models/acknowledgement.rb
+- lib/citypay_api_client/models/airline_advice.rb
+- lib/citypay_api_client/models/airline_segment.rb
+- lib/citypay_api_client/models/api_key.rb
+- lib/citypay_api_client/models/auth_reference.rb
+- lib/citypay_api_client/models/auth_references.rb
+- lib/citypay_api_client/models/auth_request.rb
+- lib/citypay_api_client/models/auth_response.rb
+- lib/citypay_api_client/models/authen_required.rb
+- lib/citypay_api_client/models/c_res_auth_request.rb
+- lib/citypay_api_client/models/capture_request.rb
+- lib/citypay_api_client/models/card.rb
+- lib/citypay_api_client/models/card_holder_account.rb
+- lib/citypay_api_client/models/card_status.rb
+- lib/citypay_api_client/models/charge_request.rb
+- lib/citypay_api_client/models/contact_details.rb
+- lib/citypay_api_client/models/decision.rb
+- lib/citypay_api_client/models/error.rb
+- lib/citypay_api_client/models/external_mpi.rb
+- lib/citypay_api_client/models/list_merchants_response.rb
+- lib/citypay_api_client/models/mcc6012.rb
+- lib/citypay_api_client/models/merchant.rb
+- lib/citypay_api_client/models/pa_res_auth_request.rb
+- lib/citypay_api_client/models/ping.rb
+- lib/citypay_api_client/models/register_card.rb
+- lib/citypay_api_client/models/request_challenged.rb
+- lib/citypay_api_client/models/retrieve_request.rb
+- lib/citypay_api_client/models/three_d_secure.rb
+- lib/citypay_api_client/models/void_request.rb
+- lib/citypay_api_client/version.rb
+- spec/api/card_holder_account_api_spec.rb
+- spec/api/operational_api_spec.rb
+- spec/api/payment_processing_api_spec.rb
+- spec/api_client_spec.rb
+- spec/configuration_spec.rb
+- spec/models/account_create_spec.rb
+- spec/models/account_status_spec.rb
+- spec/models/acknowledgement_spec.rb
+- spec/models/airline_advice_spec.rb
+- spec/models/airline_segment_spec.rb
+- spec/models/auth_reference_spec.rb
+- spec/models/auth_references_spec.rb
+- spec/models/auth_request_spec.rb
+- spec/models/auth_response_spec.rb
+- spec/models/authen_required_spec.rb
+- spec/models/c_res_auth_request_spec.rb
+- spec/models/capture_request_spec.rb
+- spec/models/card_holder_account_spec.rb
+- spec/models/card_spec.rb
+- spec/models/card_status_spec.rb
+- spec/models/charge_request_spec.rb
+- spec/models/contact_details_spec.rb
+- spec/models/decision_spec.rb
+- spec/models/error_spec.rb
+- spec/models/external_mpi_spec.rb
+- spec/models/list_merchants_response_spec.rb
+- spec/models/mcc6012_spec.rb
+- spec/models/merchant_spec.rb
+- spec/models/pa_res_auth_request_spec.rb
+- spec/models/ping_spec.rb
+- spec/models/register_card_spec.rb
+- spec/models/request_challenged_spec.rb
+- spec/models/retrieve_request_spec.rb
+- spec/models/three_d_secure_spec.rb
+- spec/models/void_request_spec.rb
+- spec/spec_helper.rb
+homepage: https://github.com/citypay/citypay-api-client-ruby
+licenses:
+- Unlicense
+metadata: {}
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '1.9'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.0.3
+signing_key: 
+specification_version: 4
+summary: A ruby wrapper for the CityPay API
+test_files:
+- spec/api/payment_processing_api_spec.rb
+- spec/api/operational_api_spec.rb
+- spec/api/card_holder_account_api_spec.rb
+- spec/api_client_spec.rb
+- spec/configuration_spec.rb
+- spec/models/error_spec.rb
+- spec/models/capture_request_spec.rb
+- spec/models/acknowledgement_spec.rb
+- spec/models/external_mpi_spec.rb
+- spec/models/decision_spec.rb
+- spec/models/airline_advice_spec.rb
+- spec/models/retrieve_request_spec.rb
+- spec/models/ping_spec.rb
+- spec/models/card_holder_account_spec.rb
+- spec/models/c_res_auth_request_spec.rb
+- spec/models/airline_segment_spec.rb
+- spec/models/card_spec.rb
+- spec/models/auth_references_spec.rb
+- spec/models/list_merchants_response_spec.rb
+- spec/models/void_request_spec.rb
+- spec/models/auth_request_spec.rb
+- spec/models/register_card_spec.rb
+- spec/models/account_status_spec.rb
+- spec/models/auth_response_spec.rb
+- spec/models/request_challenged_spec.rb
+- spec/models/account_create_spec.rb
+- spec/models/merchant_spec.rb
+- spec/models/contact_details_spec.rb
+- spec/models/charge_request_spec.rb
+- spec/models/mcc6012_spec.rb
+- spec/models/card_status_spec.rb
+- spec/models/pa_res_auth_request_spec.rb
+- spec/models/authen_required_spec.rb
+- spec/models/three_d_secure_spec.rb
+- spec/models/auth_reference_spec.rb
+- spec/spec_helper.rb