citypay_api_client 1.0.2 → 1.1.1

data/lib/citypay_api_client/models/tokenisation_response_model.rb

@@ -0,0 +1,333 @@
+=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. 
+
+Contact: support@citypay.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 6.2.1
+
+=end
+
+require 'date'
+require 'time'
+
+module CityPayApiClient
+  class TokenisationResponseModel
+    # The result of any authentication using 3d_secure authorisation against ecommerce transactions. Values are:  <table> <tr> <th>Value</th> <th>Description</th> </tr> <tr> <td>Y</td> <td>Authentication Successful. The Cardholder's password was successfully validated.</td> </tr> <tr> <td>N</td> <td>Authentication Failed. Customer failed or cancelled authentication, transaction denied.</td> </tr> <tr> <td>A</td> <td>Attempts Processing Performed Authentication could not be completed but a proof of authentication attempt (CAVV) was generated.</td> </tr> <tr> <td>U</td> <td>Authentication Could Not Be Performed Authentication could not be completed, due to technical or other problem.</td> </tr> </table> 
+    attr_accessor :authen_result
+
+    # Determines whether the bin range was found to be a commercial or business card.
+    attr_accessor :bin_commercial
+
+    # Determines whether the bin range was found to be a debit card. If false the card was considered as a credit card.
+    attr_accessor :bin_debit
+
+    # A description of the bin range found for the card.
+    attr_accessor :bin_description
+
+    # An Electronic Commerce Indicator (ECI) used to identify the result of authentication using 3DSecure. 
+    attr_accessor :eci
+
+    # The identifier provided within the request.
+    attr_accessor :identifier
+
+    # A masked value of the card number used for processing displaying limited values that can be used on a receipt. 
+    attr_accessor :maskedpan
+
+    # A name of the card scheme of the transaction that processed the transaction such as Visa or MasterCard. 
+    attr_accessor :scheme
+
+    # A Base58 encoded SHA-256 digest generated from the token value Base58 decoded and appended with the nonce value UTF-8 decoded.
+    attr_accessor :sig_id
+
+    # The token used for presentment to authorisation later in the procsesing flow.
+    attr_accessor :token
+
+    # Attribute mapping from ruby-style variable name to JSON key.
+    def self.attribute_map
+      {
+        :'authen_result' => :'authen_result',
+        :'bin_commercial' => :'bin_commercial',
+        :'bin_debit' => :'bin_debit',
+        :'bin_description' => :'bin_description',
+        :'eci' => :'eci',
+        :'identifier' => :'identifier',
+        :'maskedpan' => :'maskedpan',
+        :'scheme' => :'scheme',
+        :'sig_id' => :'sig_id',
+        :'token' => :'token'
+      }
+    end
+
+    # Returns all the JSON keys this model knows about
+    def self.acceptable_attributes
+      attribute_map.values
+    end
+
+    # Attribute type mapping.
+    def self.openapi_types
+      {
+        :'authen_result' => :'String',
+        :'bin_commercial' => :'Boolean',
+        :'bin_debit' => :'Boolean',
+        :'bin_description' => :'String',
+        :'eci' => :'String',
+        :'identifier' => :'String',
+        :'maskedpan' => :'String',
+        :'scheme' => :'String',
+        :'sig_id' => :'String',
+        :'token' => :'String'
+      }
+    end
+
+    # List of attributes with nullable: true
+    def self.openapi_nullable
+      Set.new([
+      ])
+    end
+
+    # Initializes the object
+    # @param [Hash] attributes Model attributes in the form of hash
+    def initialize(attributes = {})
+      if (!attributes.is_a?(Hash))
+        fail ArgumentError, "The input argument (attributes) must be a hash in `CityPayApiClient::TokenisationResponseModel` initialize method"
+      end
+
+      # check to see if the attribute exists and convert string to symbol for hash key
+      attributes = attributes.each_with_object({}) { |(k, v), h|
+        if (!self.class.attribute_map.key?(k.to_sym))
+          fail ArgumentError, "`#{k}` is not a valid attribute in `CityPayApiClient::TokenisationResponseModel`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
+        end
+        h[k.to_sym] = v
+      }
+
+      if attributes.key?(:'authen_result')
+        self.authen_result = attributes[:'authen_result']
+      end
+
+      if attributes.key?(:'bin_commercial')
+        self.bin_commercial = attributes[:'bin_commercial']
+      end
+
+      if attributes.key?(:'bin_debit')
+        self.bin_debit = attributes[:'bin_debit']
+      end
+
+      if attributes.key?(:'bin_description')
+        self.bin_description = attributes[:'bin_description']
+      end
+
+      if attributes.key?(:'eci')
+        self.eci = attributes[:'eci']
+      end
+
+      if attributes.key?(:'identifier')
+        self.identifier = attributes[:'identifier']
+      end
+
+      if attributes.key?(:'maskedpan')
+        self.maskedpan = attributes[:'maskedpan']
+      end
+
+      if attributes.key?(:'scheme')
+        self.scheme = attributes[:'scheme']
+      end
+
+      if attributes.key?(:'sig_id')
+        self.sig_id = attributes[:'sig_id']
+      end
+
+      if attributes.key?(:'token')
+        self.token = attributes[:'token']
+      end
+    end
+
+    # Show invalid properties with the reasons. Usually used together with valid?
+    # @return Array for valid properties with the reasons
+    def list_invalid_properties
+      invalid_properties = Array.new
+      if !@identifier.nil? && @identifier.to_s.length > 50
+        invalid_properties.push('invalid value for "identifier", the character length must be smaller than or equal to 50.')
+      end
+
+      if !@identifier.nil? && @identifier.to_s.length < 4
+        invalid_properties.push('invalid value for "identifier", the character length must be great than or equal to 4.')
+      end
+
+      invalid_properties
+    end
+
+    # Check to see if the all the properties in the model are valid
+    # @return true if the model is valid
+    def valid?
+      return false if !@identifier.nil? && @identifier.to_s.length > 50
+      return false if !@identifier.nil? && @identifier.to_s.length < 4
+      true
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] identifier Value to be assigned
+    def identifier=(identifier)
+      if !identifier.nil? && identifier.to_s.length > 50
+        fail ArgumentError, 'invalid value for "identifier", the character length must be smaller than or equal to 50.'
+      end
+
+      if !identifier.nil? && identifier.to_s.length < 4
+        fail ArgumentError, 'invalid value for "identifier", the character length must be great than or equal to 4.'
+      end
+
+      @identifier = identifier
+    end
+
+    # Checks equality by comparing each attribute.
+    # @param [Object] Object to be compared
+    def ==(o)
+      return true if self.equal?(o)
+      self.class == o.class &&
+          authen_result == o.authen_result &&
+          bin_commercial == o.bin_commercial &&
+          bin_debit == o.bin_debit &&
+          bin_description == o.bin_description &&
+          eci == o.eci &&
+          identifier == o.identifier &&
+          maskedpan == o.maskedpan &&
+          scheme == o.scheme &&
+          sig_id == o.sig_id &&
+          token == o.token
+    end
+
+    # @see the `==` method
+    # @param [Object] Object to be compared
+    def eql?(o)
+      self == o
+    end
+
+    # Calculates hash code according to all attributes.
+    # @return [Integer] Hash code
+    def hash
+      [authen_result, bin_commercial, bin_debit, bin_description, eci, identifier, maskedpan, scheme, sig_id, token].hash
+    end
+
+    # Builds the object from hash
+    # @param [Hash] attributes Model attributes in the form of hash
+    # @return [Object] Returns the model itself
+    def self.build_from_hash(attributes)
+      new.build_from_hash(attributes)
+    end
+
+    # Builds the object from hash
+    # @param [Hash] attributes Model attributes in the form of hash
+    # @return [Object] Returns the model itself
+    def build_from_hash(attributes)
+      return nil unless attributes.is_a?(Hash)
+      attributes = attributes.transform_keys(&:to_sym)
+      self.class.openapi_types.each_pair do |key, type|
+        if attributes[self.class.attribute_map[key]].nil? && self.class.openapi_nullable.include?(key)
+          self.send("#{key}=", nil)
+        elsif type =~ /\AArray<(.*)>/i
+          # check to ensure the input is an array given that the attribute
+          # is documented as an array but the input is not
+          if attributes[self.class.attribute_map[key]].is_a?(Array)
+            self.send("#{key}=", attributes[self.class.attribute_map[key]].map { |v| _deserialize($1, v) })
+          end
+        elsif !attributes[self.class.attribute_map[key]].nil?
+          self.send("#{key}=", _deserialize(type, attributes[self.class.attribute_map[key]]))
+        end
+      end
+
+      self
+    end
+
+    # Deserializes the data based on type
+    # @param string type Data type
+    # @param string value Value to be deserialized
+    # @return [Object] Deserialized data
+    def _deserialize(type, value)
+      case type.to_sym
+      when :Time
+        Time.parse(value)
+      when :Date
+        Date.parse(value)
+      when :String
+        value.to_s
+      when :Integer
+        value.to_i
+      when :Float
+        value.to_f
+      when :Boolean
+        if value.to_s =~ /\A(true|t|yes|y|1)\z/i
+          true
+        else
+          false
+        end
+      when :Object
+        # generic object (usually a Hash), return directly
+        value
+      when /\AArray<(?<inner_type>.+)>\z/
+        inner_type = Regexp.last_match[:inner_type]
+        value.map { |v| _deserialize(inner_type, v) }
+      when /\AHash<(?<k_type>.+?), (?<v_type>.+)>\z/
+        k_type = Regexp.last_match[:k_type]
+        v_type = Regexp.last_match[:v_type]
+        {}.tap do |hash|
+          value.each do |k, v|
+            hash[_deserialize(k_type, k)] = _deserialize(v_type, v)
+          end
+        end
+      else # model
+        # models (e.g. Pet) or oneOf
+        klass = CityPayApiClient.const_get(type)
+        klass.respond_to?(:openapi_one_of) ? klass.build(value) : klass.build_from_hash(value)
+      end
+    end
+
+    # Returns the string representation of the object
+    # @return [String] String presentation of the object
+    def to_s
+      to_hash.to_s
+    end
+
+    # to_body is an alias to to_hash (backward compatibility)
+    # @return [Hash] Returns the object in the form of hash
+    def to_body
+      to_hash
+    end
+
+    # Returns the object in the form of hash
+    # @return [Hash] Returns the object in the form of hash
+    def to_hash
+      hash = {}
+      self.class.attribute_map.each_pair do |attr, param|
+        value = self.send(attr)
+        if value.nil?
+          is_nullable = self.class.openapi_nullable.include?(attr)
+          next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}"))
+        end
+
+        hash[param] = _to_hash(value)
+      end
+      hash
+    end
+
+    # Outputs non-array value in the form of hash
+    # For object, use to_hash. Otherwise, just return the value
+    # @param [Object] value Any valid value
+    # @return [Hash] Returns the value in the form of hash
+    def _to_hash(value)
+      if value.is_a?(Array)
+        value.compact.map { |v| _to_hash(v) }
+      elsif value.is_a?(Hash)
+        {}.tap do |hash|
+          value.each { |k, v| hash[k] = _to_hash(v) }
+        end
+      elsif value.respond_to? :to_hash
+        value.to_hash
+      else
+        value
+      end
+    end
+
+  end
+
+end

data/lib/citypay_api_client/models/void_request.rb

@@ -1,15 +1,16 @@
 =begin
 #CityPay Payment API
 
-# This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
+# This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security Your application will need to adhere to PCI-DSS standards to operate safely and to meet requirements set out by  Visa and MasterCard and the PCI Security Standards Council. These include  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.0.0-SNAPSHOT
+OpenAPI Generator version: 6.2.1
 
 =end
 
 require 'date'
+require 'time'
 
 module CityPayApiClient
   class VoidRequest
@@ -19,9 +20,6 @@ module CityPayApiClient
     # Identifies the merchant account to perform the void for.
     attr_accessor :merchantid
 
-    # An optional reference value for the calling client such as a version number i.e.
-    attr_accessor :sdk
-
     # The transaction number of the transaction to look up and void. If an empty value is supplied then an identifier value must be supplied.
     attr_accessor :transno
 
@@ -30,17 +28,20 @@ module CityPayApiClient
       {
         :'identifier' => :'identifier',
         :'merchantid' => :'merchantid',
-        :'sdk' => :'sdk',
         :'transno' => :'transno'
       }
     end
 
+    # Returns all the JSON keys this model knows about
+    def self.acceptable_attributes
+      attribute_map.values
+    end
+
     # Attribute type mapping.
     def self.openapi_types
       {
         :'identifier' => :'String',
         :'merchantid' => :'Integer',
-        :'sdk' => :'String',
         :'transno' => :'Integer'
       }
     end
@@ -74,10 +75,6 @@ module CityPayApiClient
         self.merchantid = attributes[:'merchantid']
       end
 
-      if attributes.key?(:'sdk')
-        self.sdk = attributes[:'sdk']
-      end
-
       if attributes.key?(:'transno')
         self.transno = attributes[:'transno']
       end
@@ -132,7 +129,6 @@ module CityPayApiClient
       self.class == o.class &&
           identifier == o.identifier &&
           merchantid == o.merchantid &&
-          sdk == o.sdk &&
           transno == o.transno
     end
 
@@ -145,7 +141,7 @@ module CityPayApiClient
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [identifier, merchantid, sdk, transno].hash
+      [identifier, merchantid, transno].hash
     end
 
     # Builds the object from hash
@@ -160,8 +156,11 @@ module CityPayApiClient
     # @return [Object] Returns the model itself
     def build_from_hash(attributes)
       return nil unless attributes.is_a?(Hash)
+      attributes = attributes.transform_keys(&:to_sym)
       self.class.openapi_types.each_pair do |key, type|
-        if type =~ /\AArray<(.*)>/i
+        if attributes[self.class.attribute_map[key]].nil? && self.class.openapi_nullable.include?(key)
+          self.send("#{key}=", nil)
+        elsif type =~ /\AArray<(.*)>/i
           # check to ensure the input is an array given that the attribute
           # is documented as an array but the input is not
           if attributes[self.class.attribute_map[key]].is_a?(Array)
@@ -169,7 +168,7 @@ module CityPayApiClient
           end
         elsif !attributes[self.class.attribute_map[key]].nil?
           self.send("#{key}=", _deserialize(type, attributes[self.class.attribute_map[key]]))
-        end # or else data not found in attributes(hash), not an issue as the data can be optional
+        end
       end
 
       self
@@ -181,8 +180,8 @@ module CityPayApiClient
     # @return [Object] Deserialized data
     def _deserialize(type, value)
       case type.to_sym
-      when :DateTime
-        DateTime.parse(value)
+      when :Time
+        Time.parse(value)
       when :Date
         Date.parse(value)
       when :String
@@ -212,7 +211,9 @@ module CityPayApiClient
           end
         end
       else # model
-        CityPayApiClient.const_get(type).build_from_hash(value)
+        # models (e.g. Pet) or oneOf
+        klass = CityPayApiClient.const_get(type)
+        klass.respond_to?(:openapi_one_of) ? klass.build(value) : klass.build_from_hash(value)
       end
     end
 
@@ -238,7 +239,7 @@ module CityPayApiClient
           is_nullable = self.class.openapi_nullable.include?(attr)
           next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}"))
         end
-        
+
         hash[param] = _to_hash(value)
       end
       hash
@@ -261,5 +262,7 @@ module CityPayApiClient
         value
       end
     end
+
   end
+
 end

data/lib/citypay_api_client/utils/digest_utils.rb

@@ -0,0 +1,18 @@
+require 'digest'
+
+module DigestUtils
+  class << self
+    def validate_digest(auth_response, licence_key)
+
+      string_to_convert = auth_response.authcode +
+        auth_response.amount.to_s +
+        auth_response.result_code +
+        auth_response.merchantid.to_s +
+        auth_response.transno.to_s +
+        auth_response.identifier +
+        licence_key
+
+      auth_response.sha256 == Digest::SHA256.base64digest(string_to_convert)
+    end
+  end
+end

data/lib/citypay_api_client/utils/direct_post_mac.rb

@@ -0,0 +1,22 @@
+require 'openssl'
+
+module DirectPostMac
+  class << self
+
+    def validate(licence_key, nonce, amount, identifier, mac_to_validate)
+      mac = create(licence_key, nonce, amount, identifier)
+      mac === mac_to_validate
+    end
+
+    def create(licence_key, nonce, amount, identifier)
+      nonce_s = nonce.pack('c*').upcase
+
+      value = []
+      value.push(*nonce_s.bytes)
+      value.push(*amount.bytes)
+      value.push(*identifier.bytes)
+
+      OpenSSL::HMAC.hexdigest('sha256', licence_key, value.pack("c*")).upcase
+    end
+  end
+end

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 <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
+# This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security Your application will need to adhere to PCI-DSS standards to operate safely and to meet requirements set out by  Visa and MasterCard and the PCI Security Standards Council. These include  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.0.0-SNAPSHOT
+OpenAPI Generator version: 6.2.1
 
 =end
 
 module CityPayApiClient
-  VERSION = '1.0.2'
+  VERSION = '1.1.1'
 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 <aside class=\"notice\">   Before we begin a reminder that your application will need to adhere to PCI-DSS standards to operate safely   and to meet requirements set out by Visa and MasterCard and the PCI Security Standards Council including: </aside>  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
+# This CityPay API is a HTTP RESTful payment API used for direct server to server transactional processing. It provides a number of payment mechanisms including: Internet, MOTO, Continuous Authority transaction processing, 3-D Secure decision handling using RFA Secure, Authorisation, Refunding, Pre-Authorisation, Cancellation/Voids and Completion processing. The API is also capable of tokinsed payments using Card Holder Accounts.  ## Compliance and Security Your application will need to adhere to PCI-DSS standards to operate safely and to meet requirements set out by  Visa and MasterCard and the PCI Security Standards Council. These include  * Data must be collected using TLS version 1.2 using [strong cryptography](#enabled-tls-ciphers). We will not accept calls to our API at   lower grade encryption levels. We regularly scan our TLS endpoints for vulnerabilities and perform TLS assessments   as part of our compliance program. * The application must not store sensitive card holder data (CHD) such as the card security code (CSC) or   primary access number (PAN) * The application must not display the full card number on receipts, it is recommended to mask the PAN   and show the last 4 digits. The API will return this for you for ease of receipt creation * If you are developing a website, you will be required to perform regular scans on the network where you host the   application to meet your compliance obligations * You will be required to be PCI Compliant and the application must adhere to the security standard. Further information   is available from [https://www.pcisecuritystandards.org/](https://www.pcisecuritystandards.org/) * The API verifies that the request is for a valid account and originates from a trusted source using the remote IP   address. Our application firewalls analyse data that may be an attempt to break a large number of security common   security vulnerabilities. 
 
 Contact: support@citypay.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.0.0-SNAPSHOT
+OpenAPI Generator version: 6.2.1
 
 =end
 
@@ -19,39 +19,86 @@ require 'citypay_api_client/configuration'
 require 'citypay_api_client/models/account_create'
 require 'citypay_api_client/models/account_status'
 require 'citypay_api_client/models/acknowledgement'
+require 'citypay_api_client/models/acl_check_request'
+require 'citypay_api_client/models/acl_check_response_model'
 require 'citypay_api_client/models/airline_advice'
+require "citypay_api_client/models/api_key"
 require 'citypay_api_client/models/airline_segment'
 require 'citypay_api_client/models/auth_reference'
-require "citypay_api_client/models/api_key"
 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_result_model'
+require 'citypay_api_client/models/bin'
+require 'citypay_api_client/models/bin_lookup'
 require 'citypay_api_client/models/c_res_auth_request'
 require 'citypay_api_client/models/capture_request'
 require 'citypay_api_client/models/card'
 require 'citypay_api_client/models/card_holder_account'
 require 'citypay_api_client/models/card_status'
 require 'citypay_api_client/models/charge_request'
+require 'citypay_api_client/models/check_batch_status'
+require 'citypay_api_client/models/check_batch_status_response'
 require 'citypay_api_client/models/contact_details'
 require 'citypay_api_client/models/decision'
+require 'citypay_api_client/models/direct_post_request'
+require 'citypay_api_client/models/direct_token_auth_request'
+require 'citypay_api_client/models/domain_key_check_request'
+require 'citypay_api_client/models/domain_key_request'
+require 'citypay_api_client/models/domain_key_response'
 require 'citypay_api_client/models/error'
+require 'citypay_api_client/models/event_data_model'
+require 'citypay_api_client/models/exists'
 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/pa_res_auth_request'
+require 'citypay_api_client/models/paylink_address'
+require 'citypay_api_client/models/paylink_adjustment_request'
+require 'citypay_api_client/models/paylink_attachment_request'
+require 'citypay_api_client/models/paylink_attachment_result'
+require 'citypay_api_client/models/paylink_bill_payment_token_request'
+require 'citypay_api_client/models/paylink_card_holder'
+require 'citypay_api_client/models/paylink_cart'
+require 'citypay_api_client/models/paylink_cart_item_model'
+require 'citypay_api_client/models/paylink_config'
+require 'citypay_api_client/models/paylink_custom_param'
+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_sms_notification_path'
+require 'citypay_api_client/models/paylink_state_event'
+require 'citypay_api_client/models/paylink_token_created'
+require 'citypay_api_client/models/paylink_token_request_model'
+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/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/request_challenged'
 require 'citypay_api_client/models/retrieve_request'
 require 'citypay_api_client/models/three_d_secure'
+require 'citypay_api_client/models/tokenisation_response_model'
 require 'citypay_api_client/models/void_request'
 
 # APIs
-require 'citypay_api_client/api/card_holder_account_api'
-require 'citypay_api_client/api/operational_api'
-require 'citypay_api_client/api/payment_processing_api'
+require 'citypay_api_client/api/authorisation_and_payment_api__'
+require 'citypay_api_client/api/batch_processing_api__'
+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__'
 
 module CityPayApiClient
   class << self