velopayments 2.23.78.beta1 → 2.26.124.beta1

data/lib/velopayments/models/payment_rails.rb

@@ -3,10 +3,10 @@
 
 ### Terms and Definitions  Throughout this document and the Velo platform the following terms are used:  * **Payor.** An entity (typically a corporation) which wishes to pay funds to one or more payees via a payout. * **Payee.** The recipient of funds paid out by a payor. * **Payment.** A single transfer of funds from a payor to a payee. * **Payout.** A batch of Payments, typically used by a payor to logically group payments (e.g. by business day). Technically there need be no relationship between the payments in a payout - a single payout can contain payments to multiple payees and/or multiple payments to a single payee. * **Sandbox.** An integration environment provided by Velo Payments which offers a similar API experience to the production environment, but all funding and payment events are simulated, along with many other services such as OFAC sanctions list checking.  ## Overview  The Velo Payments API allows a payor to perform a number of operations. The following is a list of the main capabilities in a natural order of execution:  * Authenticate with the Velo platform * Maintain a collection of payees * Query the payor’s current balance of funds within the platform and perform additional funding * Issue payments to payees * Query the platform for a history of those payments  This document describes the main concepts and APIs required to get up and running with the Velo Payments platform. It is not an exhaustive API reference. For that, please see the separate Velo Payments API Reference.  ## API Considerations  The Velo Payments API is REST based and uses the JSON format for requests and responses.  Most calls are secured using OAuth 2 security and require a valid authentication access token for successful operation. See the Authentication section for details.  Where a dynamic value is required in the examples below, the {token} format is used, suggesting that the caller needs to supply the appropriate value of the token in question (without including the { or } characters).  Where curl examples are given, the –d @filename.json approach is used, indicating that the request body should be placed into a file named filename.json in the current directory. Each of the curl examples in this document should be considered a single line on the command-line, regardless of how they appear in print.  ## Authenticating with the Velo Platform  Once Velo backoffice staff have added your organization as a payor within the Velo platform sandbox, they will create you a payor Id, an API key and an API secret and share these with you in a secure manner.  You will need to use these values to authenticate with the Velo platform in order to gain access to the APIs. The steps to take are explained in the following:  create a string comprising the API key (e.g. 44a9537d-d55d-4b47-8082-14061c2bcdd8) and API secret (e.g. c396b26b-137a-44fd-87f5-34631f8fd529) with a colon between them. E.g. 44a9537d-d55d-4b47-8082-14061c2bcdd8:c396b26b-137a-44fd-87f5-34631f8fd529  base64 encode this string. E.g.: NDRhOTUzN2QtZDU1ZC00YjQ3LTgwODItMTQwNjFjMmJjZGQ4OmMzOTZiMjZiLTEzN2EtNDRmZC04N2Y1LTM0NjMxZjhmZDUyOQ==  create an HTTP **Authorization** header with the value set to e.g. Basic NDRhOTUzN2QtZDU1ZC00YjQ3LTgwODItMTQwNjFjMmJjZGQ4OmMzOTZiMjZiLTEzN2EtNDRmZC04N2Y1LTM0NjMxZjhmZDUyOQ==  perform the Velo authentication REST call using the HTTP header created above e.g. via curl:  ```   curl -X POST \\   -H \"Content-Type: application/json\" \\   -H \"Authorization: Basic NDRhOTUzN2QtZDU1ZC00YjQ3LTgwODItMTQwNjFjMmJjZGQ4OmMzOTZiMjZiLTEzN2EtNDRmZC04N2Y1LTM0NjMxZjhmZDUyOQ==\" \\   'https://api.sandbox.velopayments.com/v1/authenticate?grant_type=client_credentials' ```  If successful, this call will result in a **200** HTTP status code and a response body such as:  ```   {     \"access_token\":\"19f6bafd-93fd-4747-b229-00507bbc991f\",     \"token_type\":\"bearer\",     \"expires_in\":1799,     \"scope\":\"...\"   } ``` ## API access following authentication Following successful authentication, the value of the access_token field in the response (indicated in green above) should then be presented with all subsequent API calls to allow the Velo platform to validate that the caller is authenticated.  This is achieved by setting the HTTP Authorization header with the value set to e.g. Bearer 19f6bafd-93fd-4747-b229-00507bbc991f such as the curl example below:  ```   -H \"Authorization: Bearer 19f6bafd-93fd-4747-b229-00507bbc991f \" ```  If you make other Velo API calls which require authorization but the Authorization header is missing or invalid then you will get a **401** HTTP status response. 
 
-The version of the OpenAPI document: 2.23.78
+The version of the OpenAPI document: 2.26.124
 
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.0.0-SNAPSHOT
+OpenAPI Generator version: 5.2.0-SNAPSHOT
 
 =end
 

data/lib/velopayments/models/{company_v1.rb → payment_rejected_or_returned.rb}

@@ -3,10 +3,10 @@
 
 ### Terms and Definitions  Throughout this document and the Velo platform the following terms are used:  * **Payor.** An entity (typically a corporation) which wishes to pay funds to one or more payees via a payout. * **Payee.** The recipient of funds paid out by a payor. * **Payment.** A single transfer of funds from a payor to a payee. * **Payout.** A batch of Payments, typically used by a payor to logically group payments (e.g. by business day). Technically there need be no relationship between the payments in a payout - a single payout can contain payments to multiple payees and/or multiple payments to a single payee. * **Sandbox.** An integration environment provided by Velo Payments which offers a similar API experience to the production environment, but all funding and payment events are simulated, along with many other services such as OFAC sanctions list checking.  ## Overview  The Velo Payments API allows a payor to perform a number of operations. The following is a list of the main capabilities in a natural order of execution:  * Authenticate with the Velo platform * Maintain a collection of payees * Query the payor’s current balance of funds within the platform and perform additional funding * Issue payments to payees * Query the platform for a history of those payments  This document describes the main concepts and APIs required to get up and running with the Velo Payments platform. It is not an exhaustive API reference. For that, please see the separate Velo Payments API Reference.  ## API Considerations  The Velo Payments API is REST based and uses the JSON format for requests and responses.  Most calls are secured using OAuth 2 security and require a valid authentication access token for successful operation. See the Authentication section for details.  Where a dynamic value is required in the examples below, the {token} format is used, suggesting that the caller needs to supply the appropriate value of the token in question (without including the { or } characters).  Where curl examples are given, the –d @filename.json approach is used, indicating that the request body should be placed into a file named filename.json in the current directory. Each of the curl examples in this document should be considered a single line on the command-line, regardless of how they appear in print.  ## Authenticating with the Velo Platform  Once Velo backoffice staff have added your organization as a payor within the Velo platform sandbox, they will create you a payor Id, an API key and an API secret and share these with you in a secure manner.  You will need to use these values to authenticate with the Velo platform in order to gain access to the APIs. The steps to take are explained in the following:  create a string comprising the API key (e.g. 44a9537d-d55d-4b47-8082-14061c2bcdd8) and API secret (e.g. c396b26b-137a-44fd-87f5-34631f8fd529) with a colon between them. E.g. 44a9537d-d55d-4b47-8082-14061c2bcdd8:c396b26b-137a-44fd-87f5-34631f8fd529  base64 encode this string. E.g.: NDRhOTUzN2QtZDU1ZC00YjQ3LTgwODItMTQwNjFjMmJjZGQ4OmMzOTZiMjZiLTEzN2EtNDRmZC04N2Y1LTM0NjMxZjhmZDUyOQ==  create an HTTP **Authorization** header with the value set to e.g. Basic NDRhOTUzN2QtZDU1ZC00YjQ3LTgwODItMTQwNjFjMmJjZGQ4OmMzOTZiMjZiLTEzN2EtNDRmZC04N2Y1LTM0NjMxZjhmZDUyOQ==  perform the Velo authentication REST call using the HTTP header created above e.g. via curl:  ```   curl -X POST \\   -H \"Content-Type: application/json\" \\   -H \"Authorization: Basic NDRhOTUzN2QtZDU1ZC00YjQ3LTgwODItMTQwNjFjMmJjZGQ4OmMzOTZiMjZiLTEzN2EtNDRmZC04N2Y1LTM0NjMxZjhmZDUyOQ==\" \\   'https://api.sandbox.velopayments.com/v1/authenticate?grant_type=client_credentials' ```  If successful, this call will result in a **200** HTTP status code and a response body such as:  ```   {     \"access_token\":\"19f6bafd-93fd-4747-b229-00507bbc991f\",     \"token_type\":\"bearer\",     \"expires_in\":1799,     \"scope\":\"...\"   } ``` ## API access following authentication Following successful authentication, the value of the access_token field in the response (indicated in green above) should then be presented with all subsequent API calls to allow the Velo platform to validate that the caller is authenticated.  This is achieved by setting the HTTP Authorization header with the value set to e.g. Bearer 19f6bafd-93fd-4747-b229-00507bbc991f such as the curl example below:  ```   -H \"Authorization: Bearer 19f6bafd-93fd-4747-b229-00507bbc991f \" ```  If you make other Velo API calls which require authorization but the Authorization header is missing or invalid then you will get a **401** HTTP status response. 
 
-The version of the OpenAPI document: 2.23.78
+The version of the OpenAPI document: 2.26.124
 
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.0.0-SNAPSHOT
+OpenAPI Generator version: 5.2.0-SNAPSHOT
 
 =end
 
@@ -14,153 +14,181 @@ require 'date'
 require 'time'
 
 module VeloPayments
-  class CompanyV1
-    attr_accessor :name
+  # Base type for all rejection or return payment events
+  class PaymentRejectedOrReturned
+    # OA3 Schema type name for the source info which is used as the discriminator value to ensure that data binding works correctly
+    attr_accessor :source_type
 
-    # Company Tax Id (EIN) must be 9 numeric characters. Must match the regular expression ```[\\d]{9}```.
-    attr_accessor :tax_id
+    # UUID id of the source event in the Velo platform
+    attr_accessor :event_id
 
-    attr_accessor :operating_name
+    # ISO8601 timestamp indicating when the source event was created
+    attr_accessor :created_at
+
+    # ID of this payment within the Velo platform
+    attr_accessor :payment_id
+
+    attr_accessor :payout_payor_ids
+
+    # ID of this payment in the payors system
+    attr_accessor :payor_payment_id
+
+    # The new status of the payment. One of \"SUBMITTED\" \"ACCEPTED\" \"REJECTED\" \"ACCEPTED_BY_RAILS\" \"CONFIRMED\" \"RETURNED\" \"WITHDRAWN\"
+    attr_accessor :status
+
+    # The Velo code that indicates why the payment was rejected or returned
+    attr_accessor :reason_code
+
+    # The description of why the payment was rejected or returned
+    attr_accessor :reason_message
 
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
-        :'name' => :'name',
-        :'tax_id' => :'taxId',
-        :'operating_name' => :'operatingName'
+        :'source_type' => :'sourceType',
+        :'event_id' => :'eventId',
+        :'created_at' => :'createdAt',
+        :'payment_id' => :'paymentId',
+        :'payout_payor_ids' => :'payoutPayorIds',
+        :'payor_payment_id' => :'payorPaymentId',
+        :'status' => :'status',
+        :'reason_code' => :'reasonCode',
+        :'reason_message' => :'reasonMessage'
       }
     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
       {
-        :'name' => :'String',
-        :'tax_id' => :'String',
-        :'operating_name' => :'String'
+        :'source_type' => :'String',
+        :'event_id' => :'String',
+        :'created_at' => :'Time',
+        :'payment_id' => :'String',
+        :'payout_payor_ids' => :'PayoutPayorIds',
+        :'payor_payment_id' => :'String',
+        :'status' => :'String',
+        :'reason_code' => :'String',
+        :'reason_message' => :'String'
       }
     end
 
     # List of attributes with nullable: true
     def self.openapi_nullable
       Set.new([
-        :'tax_id',
-        :'operating_name'
       ])
     end
 
+    # List of class defined in allOf (OpenAPI v3)
+    def self.openapi_all_of
+      [
+      :'PaymentRejectedOrReturnedAllOf',
+      :'PaymentStatusChanged'
+      ]
+    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 `VeloPayments::CompanyV1` initialize method"
+        fail ArgumentError, "The input argument (attributes) must be a hash in `VeloPayments::PaymentRejectedOrReturned` 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 `VeloPayments::CompanyV1`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
+          fail ArgumentError, "`#{k}` is not a valid attribute in `VeloPayments::PaymentRejectedOrReturned`. 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?(:'name')
-        self.name = attributes[:'name']
+      if attributes.key?(:'source_type')
+        self.source_type = attributes[:'source_type']
       end
 
-      if attributes.key?(:'tax_id')
-        self.tax_id = attributes[:'tax_id']
+      if attributes.key?(:'event_id')
+        self.event_id = attributes[:'event_id']
       end
 
-      if attributes.key?(:'operating_name')
-        self.operating_name = attributes[:'operating_name']
+      if attributes.key?(:'created_at')
+        self.created_at = attributes[:'created_at']
       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 @name.nil?
-        invalid_properties.push('invalid value for "name", name cannot be nil.')
+      if attributes.key?(:'payment_id')
+        self.payment_id = attributes[:'payment_id']
       end
 
-      if @name.to_s.length > 40
-        invalid_properties.push('invalid value for "name", the character length must be smaller than or equal to 40.')
+      if attributes.key?(:'payout_payor_ids')
+        self.payout_payor_ids = attributes[:'payout_payor_ids']
       end
 
-      if @name.to_s.length < 3
-        invalid_properties.push('invalid value for "name", the character length must be great than or equal to 3.')
+      if attributes.key?(:'payor_payment_id')
+        self.payor_payment_id = attributes[:'payor_payment_id']
       end
 
-      pattern = Regexp.new(/^[\d]{9}$/)
-      if !@tax_id.nil? && @tax_id !~ pattern
-        invalid_properties.push("invalid value for \"tax_id\", must conform to the pattern #{pattern}.")
+      if attributes.key?(:'status')
+        self.status = attributes[:'status']
       end
 
-      if !@operating_name.nil? && @operating_name.to_s.length > 100
-        invalid_properties.push('invalid value for "operating_name", the character length must be smaller than or equal to 100.')
+      if attributes.key?(:'reason_code')
+        self.reason_code = attributes[:'reason_code']
       end
 
-      if !@operating_name.nil? && @operating_name.to_s.length < 1
-        invalid_properties.push('invalid value for "operating_name", the character length must be great than or equal to 1.')
+      if attributes.key?(:'reason_message')
+        self.reason_message = attributes[:'reason_message']
       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 @name.nil?
-      return false if @name.to_s.length > 40
-      return false if @name.to_s.length < 3
-      return false if !@tax_id.nil? && @tax_id !~ Regexp.new(/^[\d]{9}$/)
-      return false if !@operating_name.nil? && @operating_name.to_s.length > 100
-      return false if !@operating_name.nil? && @operating_name.to_s.length < 1
-      true
     end
 
-    # Custom attribute writer method with validation
-    # @param [Object] name Value to be assigned
-    def name=(name)
-      if name.nil?
-        fail ArgumentError, 'name cannot be nil'
+    # 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 @source_type.nil?
+        invalid_properties.push('invalid value for "source_type", source_type cannot be nil.')
       end
 
-      if name.to_s.length > 40
-        fail ArgumentError, 'invalid value for "name", the character length must be smaller than or equal to 40.'
+      if @event_id.nil?
+        invalid_properties.push('invalid value for "event_id", event_id cannot be nil.')
       end
 
-      if name.to_s.length < 3
-        fail ArgumentError, 'invalid value for "name", the character length must be great than or equal to 3.'
+      if @created_at.nil?
+        invalid_properties.push('invalid value for "created_at", created_at cannot be nil.')
       end
 
-      @name = name
-    end
-
-    # Custom attribute writer method with validation
-    # @param [Object] tax_id Value to be assigned
-    def tax_id=(tax_id)
-      pattern = Regexp.new(/^[\d]{9}$/)
-      if !tax_id.nil? && tax_id !~ pattern
-        fail ArgumentError, "invalid value for \"tax_id\", must conform to the pattern #{pattern}."
+      if @payment_id.nil?
+        invalid_properties.push('invalid value for "payment_id", payment_id cannot be nil.')
       end
 
-      @tax_id = tax_id
-    end
+      if @status.nil?
+        invalid_properties.push('invalid value for "status", status cannot be nil.')
+      end
 
-    # Custom attribute writer method with validation
-    # @param [Object] operating_name Value to be assigned
-    def operating_name=(operating_name)
-      if !operating_name.nil? && operating_name.to_s.length > 100
-        fail ArgumentError, 'invalid value for "operating_name", the character length must be smaller than or equal to 100.'
+      if @reason_code.nil?
+        invalid_properties.push('invalid value for "reason_code", reason_code cannot be nil.')
       end
 
-      if !operating_name.nil? && operating_name.to_s.length < 1
-        fail ArgumentError, 'invalid value for "operating_name", the character length must be great than or equal to 1.'
+      if @reason_message.nil?
+        invalid_properties.push('invalid value for "reason_message", reason_message cannot be nil.')
       end
 
-      @operating_name = operating_name
+      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 @source_type.nil?
+      return false if @event_id.nil?
+      return false if @created_at.nil?
+      return false if @payment_id.nil?
+      return false if @status.nil?
+      return false if @reason_code.nil?
+      return false if @reason_message.nil?
+      true
     end
 
     # Checks equality by comparing each attribute.
@@ -168,9 +196,15 @@ module VeloPayments
     def ==(o)
       return true if self.equal?(o)
       self.class == o.class &&
-          name == o.name &&
-          tax_id == o.tax_id &&
-          operating_name == o.operating_name
+          source_type == o.source_type &&
+          event_id == o.event_id &&
+          created_at == o.created_at &&
+          payment_id == o.payment_id &&
+          payout_payor_ids == o.payout_payor_ids &&
+          payor_payment_id == o.payor_payment_id &&
+          status == o.status &&
+          reason_code == o.reason_code &&
+          reason_message == o.reason_message
     end
 
     # @see the `==` method
@@ -182,7 +216,7 @@ module VeloPayments
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [name, tax_id, operating_name].hash
+      [source_type, event_id, created_at, payment_id, payout_payor_ids, payor_payment_id, status, reason_code, reason_message].hash
     end
 
     # Builds the object from hash
@@ -251,7 +285,9 @@ module VeloPayments
           end
         end
       else # model
-        VeloPayments.const_get(type).build_from_hash(value)
+        # models (e.g. Pet) or oneOf
+        klass = VeloPayments.const_get(type)
+        klass.respond_to?(:openapi_one_of) ? klass.build(value) : klass.build_from_hash(value)
       end
     end
 
@@ -277,7 +313,7 @@ module VeloPayments
           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
@@ -302,4 +338,5 @@ module VeloPayments
     end
 
   end
+
 end

data/lib/velopayments/models/{inline_response400_errors.rb → payment_rejected_or_returned_all_of.rb}

@@ -3,10 +3,10 @@
 
 ### Terms and Definitions  Throughout this document and the Velo platform the following terms are used:  * **Payor.** An entity (typically a corporation) which wishes to pay funds to one or more payees via a payout. * **Payee.** The recipient of funds paid out by a payor. * **Payment.** A single transfer of funds from a payor to a payee. * **Payout.** A batch of Payments, typically used by a payor to logically group payments (e.g. by business day). Technically there need be no relationship between the payments in a payout - a single payout can contain payments to multiple payees and/or multiple payments to a single payee. * **Sandbox.** An integration environment provided by Velo Payments which offers a similar API experience to the production environment, but all funding and payment events are simulated, along with many other services such as OFAC sanctions list checking.  ## Overview  The Velo Payments API allows a payor to perform a number of operations. The following is a list of the main capabilities in a natural order of execution:  * Authenticate with the Velo platform * Maintain a collection of payees * Query the payor’s current balance of funds within the platform and perform additional funding * Issue payments to payees * Query the platform for a history of those payments  This document describes the main concepts and APIs required to get up and running with the Velo Payments platform. It is not an exhaustive API reference. For that, please see the separate Velo Payments API Reference.  ## API Considerations  The Velo Payments API is REST based and uses the JSON format for requests and responses.  Most calls are secured using OAuth 2 security and require a valid authentication access token for successful operation. See the Authentication section for details.  Where a dynamic value is required in the examples below, the {token} format is used, suggesting that the caller needs to supply the appropriate value of the token in question (without including the { or } characters).  Where curl examples are given, the –d @filename.json approach is used, indicating that the request body should be placed into a file named filename.json in the current directory. Each of the curl examples in this document should be considered a single line on the command-line, regardless of how they appear in print.  ## Authenticating with the Velo Platform  Once Velo backoffice staff have added your organization as a payor within the Velo platform sandbox, they will create you a payor Id, an API key and an API secret and share these with you in a secure manner.  You will need to use these values to authenticate with the Velo platform in order to gain access to the APIs. The steps to take are explained in the following:  create a string comprising the API key (e.g. 44a9537d-d55d-4b47-8082-14061c2bcdd8) and API secret (e.g. c396b26b-137a-44fd-87f5-34631f8fd529) with a colon between them. E.g. 44a9537d-d55d-4b47-8082-14061c2bcdd8:c396b26b-137a-44fd-87f5-34631f8fd529  base64 encode this string. E.g.: NDRhOTUzN2QtZDU1ZC00YjQ3LTgwODItMTQwNjFjMmJjZGQ4OmMzOTZiMjZiLTEzN2EtNDRmZC04N2Y1LTM0NjMxZjhmZDUyOQ==  create an HTTP **Authorization** header with the value set to e.g. Basic NDRhOTUzN2QtZDU1ZC00YjQ3LTgwODItMTQwNjFjMmJjZGQ4OmMzOTZiMjZiLTEzN2EtNDRmZC04N2Y1LTM0NjMxZjhmZDUyOQ==  perform the Velo authentication REST call using the HTTP header created above e.g. via curl:  ```   curl -X POST \\   -H \"Content-Type: application/json\" \\   -H \"Authorization: Basic NDRhOTUzN2QtZDU1ZC00YjQ3LTgwODItMTQwNjFjMmJjZGQ4OmMzOTZiMjZiLTEzN2EtNDRmZC04N2Y1LTM0NjMxZjhmZDUyOQ==\" \\   'https://api.sandbox.velopayments.com/v1/authenticate?grant_type=client_credentials' ```  If successful, this call will result in a **200** HTTP status code and a response body such as:  ```   {     \"access_token\":\"19f6bafd-93fd-4747-b229-00507bbc991f\",     \"token_type\":\"bearer\",     \"expires_in\":1799,     \"scope\":\"...\"   } ``` ## API access following authentication Following successful authentication, the value of the access_token field in the response (indicated in green above) should then be presented with all subsequent API calls to allow the Velo platform to validate that the caller is authenticated.  This is achieved by setting the HTTP Authorization header with the value set to e.g. Bearer 19f6bafd-93fd-4747-b229-00507bbc991f such as the curl example below:  ```   -H \"Authorization: Bearer 19f6bafd-93fd-4747-b229-00507bbc991f \" ```  If you make other Velo API calls which require authorization but the Authorization header is missing or invalid then you will get a **401** HTTP status response. 
 
-The version of the OpenAPI document: 2.23.78
+The version of the OpenAPI document: 2.26.124
 
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.0.0-SNAPSHOT
+OpenAPI Generator version: 5.2.0-SNAPSHOT
 
 =end
 
@@ -14,35 +14,31 @@ require 'date'
 require 'time'
 
 module VeloPayments
-  class InlineResponse400Errors
-    # verbose message indicating the nature of the error Will be localised 
-    attr_accessor :error_message
-
-    # the property or object that caused the error
-    attr_accessor :location
-
-    attr_accessor :location_type
-
-    # a camel-cased string that can be used by clients to localise client error messages
+  class PaymentRejectedOrReturnedAllOf
+    # The Velo code that indicates why the payment was rejected or returned
     attr_accessor :reason_code
 
+    # The description of why the payment was rejected or returned
+    attr_accessor :reason_message
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
-        :'error_message' => :'errorMessage',
-        :'location' => :'location',
-        :'location_type' => :'locationType',
-        :'reason_code' => :'reasonCode'
+        :'reason_code' => :'reasonCode',
+        :'reason_message' => :'reasonMessage'
       }
     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
       {
-        :'error_message' => :'String',
-        :'location' => :'String',
-        :'location_type' => :'LocationType',
-        :'reason_code' => :'String'
+        :'reason_code' => :'String',
+        :'reason_message' => :'String'
       }
     end
 
@@ -56,44 +52,46 @@ module VeloPayments
     # @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 `VeloPayments::InlineResponse400Errors` initialize method"
+        fail ArgumentError, "The input argument (attributes) must be a hash in `VeloPayments::PaymentRejectedOrReturnedAllOf` 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 `VeloPayments::InlineResponse400Errors`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
+          fail ArgumentError, "`#{k}` is not a valid attribute in `VeloPayments::PaymentRejectedOrReturnedAllOf`. 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?(:'error_message')
-        self.error_message = attributes[:'error_message']
-      end
-
-      if attributes.key?(:'location')
-        self.location = attributes[:'location']
-      end
-
-      if attributes.key?(:'location_type')
-        self.location_type = attributes[:'location_type']
-      end
-
       if attributes.key?(:'reason_code')
         self.reason_code = attributes[:'reason_code']
       end
+
+      if attributes.key?(:'reason_message')
+        self.reason_message = attributes[:'reason_message']
+      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 @reason_code.nil?
+        invalid_properties.push('invalid value for "reason_code", reason_code cannot be nil.')
+      end
+
+      if @reason_message.nil?
+        invalid_properties.push('invalid value for "reason_message", reason_message cannot be nil.')
+      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 @reason_code.nil?
+      return false if @reason_message.nil?
       true
     end
 
@@ -102,10 +100,8 @@ module VeloPayments
     def ==(o)
       return true if self.equal?(o)
       self.class == o.class &&
-          error_message == o.error_message &&
-          location == o.location &&
-          location_type == o.location_type &&
-          reason_code == o.reason_code
+          reason_code == o.reason_code &&
+          reason_message == o.reason_message
     end
 
     # @see the `==` method
@@ -117,7 +113,7 @@ module VeloPayments
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [error_message, location, location_type, reason_code].hash
+      [reason_code, reason_message].hash
     end
 
     # Builds the object from hash
@@ -186,7 +182,9 @@ module VeloPayments
           end
         end
       else # model
-        VeloPayments.const_get(type).build_from_hash(value)
+        # models (e.g. Pet) or oneOf
+        klass = VeloPayments.const_get(type)
+        klass.respond_to?(:openapi_one_of) ? klass.build(value) : klass.build_from_hash(value)
       end
     end
 
@@ -212,7 +210,7 @@ module VeloPayments
           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
@@ -237,4 +235,5 @@ module VeloPayments
     end
 
   end
+
 end