citypay_api_client 1.1.2 → 1.1.3

data/docs/ChargeRequest.md

@@ -5,17 +5,17 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **amount** | **Integer** | The amount to authorise in the lowest unit of currency with a variable length to a maximum of 12 digits.  No decimal points are to be included and no divisional characters such as 1,024.  The amount should be the total amount required for the transaction.  For example with GBP £1,021.95 the amount value is 102195.  |  |
-| **avs_postcode_policy** | **String** | A policy value which determines whether an AVS postcode policy is enforced or bypassed.  Values are  `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the AVS postcode numeric value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the postcode did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send postcode details for authorisation.  | [optional] |
+| **avs_postcode_policy** | **String** | A policy value which determines whether an AVS postcode policy is enforced or bypassed.  Values are:   `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the AVS postcode numeric value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the postcode did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send postcode details for authorisation.  | [optional] |
 | **cardholder_agreement** | **String** | Merchant-initiated transactions (MITs) are payments you trigger, where the cardholder has previously consented to you carrying out such payments. These may be scheduled (such as recurring payments and installments) or unscheduled (like account top-ups triggered by balance thresholds and no-show charges).  Scheduled --- These are regular payments using stored card details, like installments or a monthly subscription fee.  - `I` Instalment - A single purchase of goods or services billed to a cardholder in multiple transactions, over a period of time agreed by the cardholder and you.  - `R` Recurring - Transactions processed at fixed, regular intervals not to exceed one year between transactions, representing an agreement between a cardholder and you to purchase goods or services provided over a period of time.  Unscheduled --- These are payments using stored card details that do not occur on a regular schedule, like top-ups for a digital wallet triggered by the balance falling below a certain threshold.  - `A` Reauthorisation - a purchase made after the original purchase. A common scenario is delayed/split shipments.  - `C` Unscheduled Payment - A transaction using a stored credential for a fixed or variable amount that does not occur on a scheduled or regularly occurring transaction date. This includes account top-ups triggered by balance thresholds.  - `D` Delayed Charge - A delayed charge is typically used in hotel, cruise lines and vehicle rental environments to perform a supplemental account charge after original services are rendered.  - `L` Incremental - An incremental authorisation is typically found in hotel and car rental environments, where the cardholder has agreed to pay for any service incurred during the duration of the contract. An incremental authorisation is where you need to seek authorisation of further funds in addition to what you have originally requested. A common scenario is additional services charged to the contract, such as extending a stay in a hotel.  - `S` Resubmission - When the original purchase occurred, but you were not able to get authorisation at the time the goods or services were provided. It should be only used where the goods or services have already been provided, but the authorisation request is declined for insufficient funds.  - `X` No-show - A no-show is a transaction where you are enabled to charge for services which the cardholder entered into an agreement to purchase, but the cardholder did not meet the terms of the agreement.  | [optional] |
-| **csc** | **String** | The Card Security Code (CSC) (also known as CV2/CVV2) is normally found on the back of the card (American Express has it on the front). The value helps to identify posession of the card as it is not available within the chip or magnetic swipe.  When forwarding the CSC, please ensure the value is a string as some values start with 0 and this will be stripped out by any integer parsing.  The CSC number aids fraud prevention in Mail Order and Internet payments.  Business rules are available on your account to identify whether to accept or decline transactions based on mismatched results of the CSC.  The Payment Card Industry (PCI) requires that at no stage of a transaction should the CSC be stored.  This applies to all entities handling card data.  It should also not be used in any hashing process.  CityPay do not store the value and have no method of retrieving the value once the transaction has been processed. For this reason, duplicate checking is unable to determine the CSC in its duplication check algorithm.  | [optional] |
-| **csc_policy** | **String** | A policy value which determines whether a CSC policy is enforced or bypassed.  Values are  `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the CSC value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the CSC did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send the CSC details for authorisation.  | [optional] |
+| **csc** | **String** | The Card Security Code (CSC) (also known as CV2/CVV2) is normally found on the back of the card (American Express has it on the front). The value helps to identify possession of the card as it is not available within the chip or magnetic swipe.  When forwarding the CSC, please ensure the value is a string as some values start with 0 and this will be stripped out by any integer parsing.  The CSC number aids fraud prevention in Mail Order and Internet payments.  Business rules are available on your account to identify whether to accept or decline transactions based on mismatched results of the CSC.  The Payment Card Industry (PCI) requires that at no stage of a transaction should the CSC be stored.  This applies to all entities handling card data.  It should also not be used in any hashing process.  CityPay do not store the value and have no method of retrieving the value once the transaction has been processed. For this reason, duplicate checking is unable to determine the CSC in its duplication check algorithm.  | [optional] |
+| **csc_policy** | **String** | A policy value which determines whether a CSC policy is enforced or bypassed.  Values are:   `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the CSC value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the CSC did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send the CSC details for authorisation.  | [optional] |
 | **currency** | **String** | The processing currency for the transaction. Will default to the merchant account currency. | [optional] |
-| **duplicate_policy** | **String** | A policy value which determines whether a duplication policy is enforced or bypassed. A duplication check has a window of time set against your account within which it can action. If a previous transaction with matching values occurred within the window, any subsequent transaction will result in a T001 result.  Values are  `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be checked for duplication within the duplication window.   `2` to bypass. Transactions that are bypassed will not be checked for duplication within the duplication window.   `3` to ignore. Transactions that are ignored will have the same affect as bypass.  | [optional] |
+| **duplicate_policy** | **String** | A policy value which determines whether a duplication policy is enforced or bypassed. A duplication check has a window of time set against your account within which it can action. If a previous transaction with matching values occurred within the window, any subsequent transaction will result in a T001 result.  Values are   `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be checked for duplication within the duplication window.   `2` to bypass. Transactions that are bypassed will not be checked for duplication within the duplication window.   `3` to ignore. Transactions that are ignored will have the same affect as bypass.  | [optional] |
 | **identifier** | **String** | The identifier of the transaction to process. The value should be a valid reference and may be used to perform  post processing actions and to aid in reconciliation of transactions.  The value should be a valid printable string with ASCII character ranges from 0x32 to 0x127.  The identifier is recommended to be distinct for each transaction such as a [random unique identifier](https://en.wikipedia.org/wiki/Universally_unique_identifier) this will aid in ensuring each transaction is identifiable.  When transactions are processed they are also checked for duplicate requests. Changing the identifier on a subsequent request will ensure that a transaction is considered as different.  |  |
 | **initiation** | **String** | Transactions charged using the API are defined as:  **Cardholder Initiated**: A _cardholder initiated transaction_ (CIT) is where the cardholder selects the card for use for a purchase using previously stored details. An example would be a customer buying an item from your website after being present with their saved card details at checkout.  **Merchant Intiated**: A _merchant initiated transaction_ (MIT) is an authorisation initiated where you as the  merchant submit a cardholders previously stored details without the cardholder's participation. An example would  be a subscription to a membership scheme to debit their card monthly.  MITs have different reasons such as reauthorisation, delayed, unscheduled, incremental, recurring, instalment, no-show or resubmission.  The following values apply   - `M` - specifies that the transaction is initiated by the merchant   - `C` - specifies that the transaction is initiated by the cardholder  Where transactions are merchant initiated, a valid cardholder agreement must be defined.  | [optional] |
-| **match_avsa** | **String** | A policy value which determines whether an AVS address policy is enforced, bypassed or ignored.  Values are  `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the AVS address numeric value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the address did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send address numeric details for authorisation.  | [optional] |
+| **match_avsa** | **String** | A policy value which determines whether an AVS address policy is enforced, bypassed or ignored.  Values are:   `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the AVS address numeric value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the address did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send address numeric details for authorisation.  | [optional] |
 | **merchantid** | **Integer** | Identifies the merchant account to perform processing for. |  |
-| **tag** | **String** | A \"tag\" is a label that you can attach to a payment authorization. Tags can help you group transactions together based on certain criteria, like a work job or a ticket number. They can also assist in filtering transactions when you're generating reports.  Multiple Tags You can add more than one tag to a transaction by separating them with commas.  Limitations There is a maximum limit of 3 tags that can be added to a single transaction. Each tag can be no longer than 20 characters and alphanumeric with no spaces.  Example: Let's say you're a software company and you have different teams working on various projects. When a team makes a purchase or incurs an expense, they can tag the transaction with the project name, the team name, and the type of expense.  Project Name: Project_X Team Name: Team_A Type of Expense: Hardware So, the tag for a transaction might look like: Project_X,Team_A,Hardware  This way, when you're looking at your financial reports, you can easily filter transactions based on these tags to see how much each project or team is spending on different types of expenses.  | [optional] |
+| **tag** | **Array<String>** |  | [optional] |
 | **threedsecure** | [**ThreeDSecure**](ThreeDSecure.md) |  | [optional] |
 | **token** | **String** | A tokenised form of a card that belongs to a card holder's account and that has been previously registered. The token is time based and will only be active for a short duration. The value is therefore designed not to be stored remotely for future use.   Tokens will start with ct and are resiliently tamper proof using HMacSHA-256. No sensitive card data is stored internally within the token.   Each card will contain a different token and the value may be different on any retrieval call.   The value can be presented for payment as a selection value to an end user in a web application.  |  |
 | **trans_info** | **String** | Further information that can be added to the transaction will display in reporting. Can be used for flexible values such as operator id. | [optional] |
@@ -27,7 +27,7 @@
 require 'citypay_api_client'
 
 instance = CityPayApiClient::ChargeRequest.new(
-  amount: 3600,
+  amount: 19995,
   avs_postcode_policy: null,
   cardholder_agreement: null,
   csc: 10,

data/docs/Decision.md

@@ -4,7 +4,6 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **authen_required** | [**AuthenRequired**](AuthenRequired.md) |  | [optional] |
 | **auth_response** | [**AuthResponse**](AuthResponse.md) |  | [optional] |
 | **request_challenged** | [**RequestChallenged**](RequestChallenged.md) |  | [optional] |
 
@@ -14,7 +13,6 @@
 require 'citypay_api_client'
 
 instance = CityPayApiClient::Decision.new(
-  authen_required: null,
   auth_response: null,
   request_challenged: null
 )

data/docs/DirectPostApi.md

@@ -165,13 +165,6 @@ Direct Post Auth Request
 
 Used to initiate a direct post request transaction flow.
 
-<pre class="inline-code language-bash">
-<code>
-curl https://api.citypay.com/direct/auth?cp-domain-key=n834ytqp84y... \
- -d "amount=7500&identifier=example_trans&cardnumber=4000000000000002&expmonth=9&expyear=2028&bill_to_postcode=L1+7ZW
-</code>
-</pre>.
-
 
 ### Examples
 
@@ -187,7 +180,7 @@ CityPayApiClient.configure do |config|
 end
 
 api_instance = CityPayApiClient::DirectPostApi.new
-direct_post_request = CityPayApiClient::DirectPostRequest.new({amount: 3600, cardnumber: '4000 0000 0000 0002', expmonth: 9, expyear: 2027, identifier: '95b857a1-5955-4b86-963c-5a6dbfc4fb95', mac: '3896FBC43674AF59478DAF7F546FA4D4CB89981A936E6AAE997E43B55DF6C39D'}) # DirectPostRequest | 
+direct_post_request = CityPayApiClient::DirectPostRequest.new({amount: 19995, cardnumber: '4000 0000 0000 0002', expmonth: 9, expyear: 2027, identifier: '95b857a1-5955-4b86-963c-5a6dbfc4fb95', mac: '3896FBC43674AF59478DAF7F546FA4D4CB89981A936E6AAE997E43B55DF6C39D'}) # DirectPostRequest | 
 
 begin
   # Direct Post Auth Request
@@ -244,13 +237,6 @@ Direct Post Tokenise Request
 
 Used to initiate a direct post request transaction flow.
 
-<pre class="inline-code language-bash">
-<code>
-curl https://api.citypay.com/v6/direct?cp-domain-key=n834ytqp84y... \
- -d "amount=7500&identifier=example_trans&cardnumber=4000000000000002&expmonth=9&expyear=2028&bill_to_postcode=L1+7ZW
-</code>
-</pre>.
-
 
 ### Examples
 
@@ -266,7 +252,7 @@ CityPayApiClient.configure do |config|
 end
 
 api_instance = CityPayApiClient::DirectPostApi.new
-direct_post_request = CityPayApiClient::DirectPostRequest.new({amount: 3600, cardnumber: '4000 0000 0000 0002', expmonth: 9, expyear: 2027, identifier: '95b857a1-5955-4b86-963c-5a6dbfc4fb95', mac: '3896FBC43674AF59478DAF7F546FA4D4CB89981A936E6AAE997E43B55DF6C39D'}) # DirectPostRequest | 
+direct_post_request = CityPayApiClient::DirectPostRequest.new({amount: 19995, cardnumber: '4000 0000 0000 0002', expmonth: 9, expyear: 2027, identifier: '95b857a1-5955-4b86-963c-5a6dbfc4fb95', mac: '3896FBC43674AF59478DAF7F546FA4D4CB89981A936E6AAE997E43B55DF6C39D'}) # DirectPostRequest | 
 
 begin
   # Direct Post Tokenise Request

data/docs/DirectPostRequest.md

@@ -5,24 +5,24 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **amount** | **Integer** | The amount to authorise in the lowest unit of currency with a variable length to a maximum of 12 digits.  No decimal points are to be included and no divisional characters such as 1,024.  The amount should be the total amount required for the transaction.  For example with GBP £1,021.95 the amount value is 102195.  |  |
-| **avs_postcode_policy** | **String** | A policy value which determines whether an AVS postcode policy is enforced or bypassed.  Values are  `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the AVS postcode numeric value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the postcode did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send postcode details for authorisation.  | [optional] |
+| **avs_postcode_policy** | **String** | A policy value which determines whether an AVS postcode policy is enforced or bypassed.  Values are:   `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the AVS postcode numeric value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the postcode did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send postcode details for authorisation.  | [optional] |
 | **bill_to** | [**ContactDetails**](ContactDetails.md) |  | [optional] |
 | **cardnumber** | **String** | The card number (PAN) with a variable length to a maximum of 21 digits in numerical form. Any non numeric characters will be stripped out of the card number, this includes whitespace or separators internal of the provided value.  The card number must be treated as sensitive data. We only provide an obfuscated value in logging and reporting.  The plaintext value is encrypted in our database using AES 256 GMC bit encryption for settlement or refund purposes.  When providing the card number to our gateway through the authorisation API you will be handling the card data on your application. This will require further PCI controls to be in place and this value must never be stored.  |  |
-| **csc** | **String** | The Card Security Code (CSC) (also known as CV2/CVV2) is normally found on the back of the card (American Express has it on the front). The value helps to identify posession of the card as it is not available within the chip or magnetic swipe.  When forwarding the CSC, please ensure the value is a string as some values start with 0 and this will be stripped out by any integer parsing.  The CSC number aids fraud prevention in Mail Order and Internet payments.  Business rules are available on your account to identify whether to accept or decline transactions based on mismatched results of the CSC.  The Payment Card Industry (PCI) requires that at no stage of a transaction should the CSC be stored.  This applies to all entities handling card data.  It should also not be used in any hashing process.  CityPay do not store the value and have no method of retrieving the value once the transaction has been processed. For this reason, duplicate checking is unable to determine the CSC in its duplication check algorithm.  | [optional] |
-| **csc_policy** | **String** | A policy value which determines whether a CSC policy is enforced or bypassed.  Values are  `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the CSC value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the CSC did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send the CSC details for authorisation.  | [optional] |
+| **csc** | **String** | The Card Security Code (CSC) (also known as CV2/CVV2) is normally found on the back of the card (American Express has it on the front). The value helps to identify possession of the card as it is not available within the chip or magnetic swipe.  When forwarding the CSC, please ensure the value is a string as some values start with 0 and this will be stripped out by any integer parsing.  The CSC number aids fraud prevention in Mail Order and Internet payments.  Business rules are available on your account to identify whether to accept or decline transactions based on mismatched results of the CSC.  The Payment Card Industry (PCI) requires that at no stage of a transaction should the CSC be stored.  This applies to all entities handling card data.  It should also not be used in any hashing process.  CityPay do not store the value and have no method of retrieving the value once the transaction has been processed. For this reason, duplicate checking is unable to determine the CSC in its duplication check algorithm.  | [optional] |
+| **csc_policy** | **String** | A policy value which determines whether a CSC policy is enforced or bypassed.  Values are:   `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the CSC value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the CSC did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send the CSC details for authorisation.  | [optional] |
 | **currency** | **String** | The processing currency for the transaction. Will default to the merchant account currency. | [optional] |
-| **duplicate_policy** | **String** | A policy value which determines whether a duplication policy is enforced or bypassed. A duplication check has a window of time set against your account within which it can action. If a previous transaction with matching values occurred within the window, any subsequent transaction will result in a T001 result.  Values are  `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be checked for duplication within the duplication window.   `2` to bypass. Transactions that are bypassed will not be checked for duplication within the duplication window.   `3` to ignore. Transactions that are ignored will have the same affect as bypass.  | [optional] |
+| **duplicate_policy** | **String** | A policy value which determines whether a duplication policy is enforced or bypassed. A duplication check has a window of time set against your account within which it can action. If a previous transaction with matching values occurred within the window, any subsequent transaction will result in a T001 result.  Values are   `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be checked for duplication within the duplication window.   `2` to bypass. Transactions that are bypassed will not be checked for duplication within the duplication window.   `3` to ignore. Transactions that are ignored will have the same affect as bypass.  | [optional] |
 | **expmonth** | **Integer** | The month of expiry of the card. The month value should be a numerical value between 1 and 12.  |  |
 | **expyear** | **Integer** | The year of expiry of the card.  |  |
 | **identifier** | **String** | The identifier of the transaction to process. The value should be a valid reference and may be used to perform  post processing actions and to aid in reconciliation of transactions.  The value should be a valid printable string with ASCII character ranges from 0x32 to 0x127.  The identifier is recommended to be distinct for each transaction such as a [random unique identifier](https://en.wikipedia.org/wiki/Universally_unique_identifier) this will aid in ensuring each transaction is identifiable.  When transactions are processed they are also checked for duplicate requests. Changing the identifier on a subsequent request will ensure that a transaction is considered as different.  |  |
 | **mac** | **String** | A message authentication code ensures the data is authentic and that the intended amount has not been tampered with. The mac value is generated using a hash-based mac value. The following algorithm is used. - A key (k) is derived from your licence key - A value (v) is produced by concatenating the nonce, amount value and identifier, such as a purchase   with nonce `0123456789ABCDEF` an amount of £275.95 and an identifier of OD-12345678 would become   `0123456789ABCDEF27595OD-12345678` and extracting the UTF-8 byte values - The result from HMAC_SHA256(k, v) is hex-encoded (upper-case) - For instance, a licence key of `LK123456789`, a nonce of `0123456789ABCDEF`, an amount of `27595` and an identifier of `OD-12345678`  would generate a MAC of `163DBAB194D743866A9BCC7FC9C8A88FCD99C6BBBF08D619291212D1B91EE12E`.  |  |
-| **match_avsa** | **String** | A policy value which determines whether an AVS address policy is enforced, bypassed or ignored.  Values are  `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the AVS address numeric value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the address did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send address numeric details for authorisation.  | [optional] |
+| **match_avsa** | **String** | A policy value which determines whether an AVS address policy is enforced, bypassed or ignored.  Values are:   `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account.   `1` for an enforced policy. Transactions that are enforced will be rejected if the AVS address numeric value does not match.   `2` to bypass. Transactions that are bypassed will be allowed through even if the address did not match.   `3` to ignore. Transactions that are ignored will bypass the result and not send address numeric details for authorisation.  | [optional] |
 | **name_on_card** | **String** | The card holder name as appears on the card such as MR N E BODY. Required for some acquirers.  | [optional] |
 | **nonce** | **String** | A random value Hex string (uppercase) which is provided to the API to perform a digest. The value will be used in any digest function.  | [optional] |
 | **redirect_failure** | **String** | The URL used to redirect back to your site when a transaction has been rejected or declined. Required if a url-encoded request.  | [optional] |
 | **redirect_success** | **String** | The URL used to redirect back to your site when a transaction has been tokenised or authorised. Required if a url-encoded request.  | [optional] |
 | **ship_to** | [**ContactDetails**](ContactDetails.md) |  | [optional] |
-| **tag** | **String** | A \"tag\" is a label that you can attach to a payment authorization. Tags can help you group transactions together based on certain criteria, like a work job or a ticket number. They can also assist in filtering transactions when you're generating reports.  Multiple Tags You can add more than one tag to a transaction by separating them with commas.  Limitations There is a maximum limit of 3 tags that can be added to a single transaction. Each tag can be no longer than 20 characters and alphanumeric with no spaces.  Example: Let's say you're a software company and you have different teams working on various projects. When a team makes a purchase or incurs an expense, they can tag the transaction with the project name, the team name, and the type of expense.  Project Name: Project_X Team Name: Team_A Type of Expense: Hardware So, the tag for a transaction might look like: Project_X,Team_A,Hardware  This way, when you're looking at your financial reports, you can easily filter transactions based on these tags to see how much each project or team is spending on different types of expenses.  | [optional] |
+| **tag** | **Array<String>** |  | [optional] |
 | **threedsecure** | [**ThreeDSecure**](ThreeDSecure.md) |  | [optional] |
 | **trans_info** | **String** | Further information that can be added to the transaction will display in reporting. Can be used for flexible values such as operator id. | [optional] |
 | **trans_type** | **String** | The type of transaction being submitted. Normally this value is not required and your account manager may request that you set this field. | [optional] |
@@ -33,7 +33,7 @@
 require 'citypay_api_client'
 
 instance = CityPayApiClient::DirectPostRequest.new(
-  amount: 3600,
+  amount: 19995,
   avs_postcode_policy: null,
   bill_to: null,
   cardnumber: 4000 0000 0000 0002,

data/docs/EventDataModel.md

@@ -16,10 +16,10 @@
 require 'citypay_api_client'
 
 instance = CityPayApiClient::EventDataModel.new(
-  event_end_date: null,
+  event_end_date: Mon Apr 22 00:00:00 UTC 2024,
   event_id: null,
   event_organiser_id: null,
-  event_start_date: null,
+  event_start_date: Mon Apr 22 00:00:00 UTC 2024,
   payment_type: null
 )
 ```

data/docs/MerchantBatchReportRequest.md

@@ -0,0 +1,28 @@
+# CityPayApiClient::MerchantBatchReportRequest
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **date_from** | **Date** | Start date (YYYY-MM-DD) for batch retrieval range, inclusive. Maximum value is 3 years ago. | [optional] |
+| **date_until** | **Date** | End date (YYYY-MM-DD) for batch retrieval range, inclusive. | [optional] |
+| **max_results** | **Integer** | The maximum number of results to return in a single response. This value is used to limit the size of data returned by the API, enhancing performance and manageability. Values should be between 5 and 250. | [optional] |
+| **merchant_id** | **Array<Integer>** |  | [optional] |
+| **next_token** | **String** | A token that identifies the starting point of the page of results to be returned. An empty value indicates the start of the dataset. When supplied, it is validated and used to fetch the subsequent page of results. This token is typically obtained from the response of a previous pagination request. | [optional] |
+| **order_by** | **String** | Specifies the field by which results are ordered. Available fields are [merchant_id,batch_no,net_amount]. By default, fields are ordered by OrderByExpression(merchant_id,ASC),OrderByExpression(batch_no,ASC). To order in descending order, prefix with '-' or suffix with ' DESC'. | [optional] |
+
+## Example
+
+```ruby
+require 'citypay_api_client'
+
+instance = CityPayApiClient::MerchantBatchReportRequest.new(
+  date_from: Wed Jan 24 00:00:00 UTC 2024,
+  date_until: Wed Jan 31 00:00:00 UTC 2024,
+  max_results: 50,
+  merchant_id: null,
+  next_token: n34liuwn435tUAGFNg34yn...,
+  order_by: date
+)
+```
+

data/docs/MerchantBatchReportResponse.md

@@ -0,0 +1,24 @@
+# CityPayApiClient::MerchantBatchReportResponse
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **batches** | [**Array<MerchantBatchResponse>**](MerchantBatchResponse.md) |  |  |
+| **count** | **Integer** | The count of items returned in this page. | [optional] |
+| **max_results** | **Integer** | The max results requested in this page. | [optional] |
+| **next_token** | **String** | A token that identifies the starting point of the page of results to be returned. An empty value indicates the start of the dataset. When supplied, it is validated and used to fetch the subsequent page of results. This token is typically obtained from the response of a previous pagination request. | [optional] |
+
+## Example
+
+```ruby
+require 'citypay_api_client'
+
+instance = CityPayApiClient::MerchantBatchReportResponse.new(
+  batches: null,
+  count: 25,
+  max_results: 50,
+  next_token: n34liuwn435tUAGFNg34yn...
+)
+```
+

data/docs/MerchantBatchResponse.md

@@ -0,0 +1,30 @@
+# CityPayApiClient::MerchantBatchResponse
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **batch_closed** | **Time** | The date and time when the batch was closed. This is represented in ISO 8601 format (e.g., YYYY-MM-DDTHH:MM:SSZ) and indicates when the batch processing was completed. | [optional] |
+| **batch_no** | **String** | The incremental identifier of the batch. This number is used to track and reference the batch in subsequent operations or inquiries. | [optional] |
+| **batch_status** | **String** | A descriptive string detailing the current status of the batch. This status provides a human-readable explanation of the batch's processing state. | [optional] |
+| **batch_status_code** | **String** | A batch status code that represents the processing state of the batch. Batches will be one of  - 'O' defining the batch is open for settlement and not yet settled  - 'X' defines that the batch is external to our systems and managed elsewhere  - 'C' defines that the batch is cancelled and not settled  - 'S' defines that the batch has been settled and remitted.  | [optional] |
+| **currency** | **String** | The currency of the batch. | [optional] |
+| **merchantid** | **Integer** | The Merchant ID (MID) associated with the batch. This identifier specifies which merchant account the batch was processed for, linking transactions to the merchant. | [optional] |
+| **net_summary** | [**NetSummaryResponse**](NetSummaryResponse.md) |  | [optional] |
+
+## Example
+
+```ruby
+require 'citypay_api_client'
+
+instance = CityPayApiClient::MerchantBatchResponse.new(
+  batch_closed: 2024-04-22T13:29:14Z,
+  batch_no: null,
+  batch_status: null,
+  batch_status_code: null,
+  currency: GBP,
+  merchantid: 11223344,
+  net_summary: null
+)
+```
+

data/docs/NetSummaryResponse.md

@@ -0,0 +1,32 @@
+# CityPayApiClient::NetSummaryResponse
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **credit_items_amount** | **String** | The total value of refund (credit) transaction items. Represents the sum of funds returned to customers. | [optional] |
+| **credit_items_count** | **Integer** | The count of refund (credit) transaction items. Reflects the number of refund transactions processed. | [optional] |
+| **credit_items_value** | **Integer** | The total value of refund (credit) transaction items. Represents the sum of funds returned to customers. | [optional] |
+| **debit_items_amount** | **String** | The total value of charge (debit) transaction items. Represents the sum of funds received from charges. | [optional] |
+| **debit_items_count** | **Integer** | The count of charge (debit) transaction items. Indicates the number of charge transactions processed. | [optional] |
+| **debit_items_value** | **Integer** | The total value of charge (debit) transaction items. Represents the sum of funds received from charges. | [optional] |
+| **net_amount** | **Integer** | The absolute net value, reflecting the net gain or loss from transactions. | [optional] |
+| **total_count** | **Integer** | The total count of all transaction items. | [optional] |
+
+## Example
+
+```ruby
+require 'citypay_api_client'
+
+instance = CityPayApiClient::NetSummaryResponse.new(
+  credit_items_amount: £75.89,
+  credit_items_count: 12345,
+  credit_items_value: 11874500,
+  debit_items_amount: £75.89,
+  debit_items_count: 12345,
+  debit_items_value: 11874500,
+  net_amount: 11874500,
+  total_count: 12345
+)
+```
+

data/docs/PaylinkAdjustmentRequest.md

@@ -14,7 +14,7 @@
 require 'citypay_api_client'
 
 instance = CityPayApiClient::PaylinkAdjustmentRequest.new(
-  amount: 3600,
+  amount: 19995,
   identifier: 95b857a1-5955-4b86-963c-5a6dbfc4fb95,
   reason: null
 )

data/docs/PaylinkApi.md

@@ -5,6 +5,7 @@ All URIs are relative to *https://api.citypay.com*
 | Method | HTTP request | Description |
 | ------ | ------------ | ----------- |
 | [**token_adjustment_request**](PaylinkApi.md#token_adjustment_request) | **POST** /paylink/{token}/adjustment | Paylink Token Adjustment |
+| [**token_cancel_request**](PaylinkApi.md#token_cancel_request) | **PUT** /paylink/{token}/cancel | Cancel a Paylink Token |
 | [**token_changes_request**](PaylinkApi.md#token_changes_request) | **POST** /paylink/token/changes | Paylink Token Audit |
 | [**token_close_request**](PaylinkApi.md#token_close_request) | **PUT** /paylink/{token}/close | Close Paylink Token |
 | [**token_create_bill_payment_request**](PaylinkApi.md#token_create_bill_payment_request) | **POST** /paylink/bill-payment | Create Bill Payment Paylink Token |
@@ -12,6 +13,7 @@ All URIs are relative to *https://api.citypay.com*
 | [**token_purge_attachments_request**](PaylinkApi.md#token_purge_attachments_request) | **PUT** /paylink/{token}/purge-attachments | Purges any attachments for a Paylink Token |
 | [**token_reconciled_request**](PaylinkApi.md#token_reconciled_request) | **PUT** /paylink/{token}/reconciled | Reconcile Paylink Token |
 | [**token_reopen_request**](PaylinkApi.md#token_reopen_request) | **PUT** /paylink/{token}/reopen | Reopen Paylink Token |
+| [**token_resend_notification_request**](PaylinkApi.md#token_resend_notification_request) | **POST** /paylink/{token}/resend-notification | Resend a notification for Paylink Token |
 | [**token_status_request**](PaylinkApi.md#token_status_request) | **GET** /paylink/{token}/status | Paylink Token Status |
 
 
@@ -89,6 +91,74 @@ end
 - **Accept**: application/json, text/xml
 
 
+## token_cancel_request
+
+> <Acknowledgement> token_cancel_request(token)
+
+Cancel a Paylink Token
+
+Marks a Paylink Token as cancelled. This cancels the Token for any future request for processing.
+
+### Examples
+
+```ruby
+require 'time'
+require 'citypay_api_client'
+# setup authorization
+CityPayApiClient.configure do |config|
+  config.api_key['cp-api-key'] = CityPayApiClient::ApiKey.new(client_id: 'YourClientId', licence_key: 'YourLicenceKey').generate
+end
+
+api_instance = CityPayApiClient::PaylinkApi.new
+token = 'token_example' # String | The token returned by the create token process.
+
+begin
+  # Cancel a Paylink Token
+  result = api_instance.token_cancel_request(token)
+  p result
+rescue CityPayApiClient::ApiError => e
+  puts "Error when calling PaylinkApi->token_cancel_request: #{e}"
+end
+```
+
+#### Using the token_cancel_request_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<Acknowledgement>, Integer, Hash)> token_cancel_request_with_http_info(token)
+
+```ruby
+begin
+  # Cancel a Paylink Token
+  data, status_code, headers = api_instance.token_cancel_request_with_http_info(token)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <Acknowledgement>
+rescue CityPayApiClient::ApiError => e
+  puts "Error when calling PaylinkApi->token_cancel_request_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **token** | **String** | The token returned by the create token process. |  |
+
+### Return type
+
+[**Acknowledgement**](Acknowledgement.md)
+
+### Authorization
+
+[cp-api-key](../README.md#cp-api-key)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json, text/xml
+
+
 ## token_changes_request
 
 > <PaylinkTokenStatusChangeResponse> token_changes_request(paylink_token_status_change_request)
@@ -108,7 +178,7 @@ CityPayApiClient.configure do |config|
 end
 
 api_instance = CityPayApiClient::PaylinkApi.new
-paylink_token_status_change_request = CityPayApiClient::PaylinkTokenStatusChangeRequest.new({after: Time.now, merchantid: 11223344}) # PaylinkTokenStatusChangeRequest | 
+paylink_token_status_change_request = CityPayApiClient::PaylinkTokenStatusChangeRequest.new({after: Time.parse('2024-04-22T13:29:14Z'), merchantid: 11223344}) # PaylinkTokenStatusChangeRequest | 
 
 begin
   # Paylink Token Audit
@@ -737,6 +807,76 @@ end
 - **Accept**: application/json, text/xml
 
 
+## token_resend_notification_request
+
+> <Acknowledgement> token_resend_notification_request(token, paylink_resend_notification_request)
+
+Resend a notification for Paylink Token
+
+Resend a notification for Paylink Token.
+
+### Examples
+
+```ruby
+require 'time'
+require 'citypay_api_client'
+# setup authorization
+CityPayApiClient.configure do |config|
+  config.api_key['cp-api-key'] = CityPayApiClient::ApiKey.new(client_id: 'YourClientId', licence_key: 'YourLicenceKey').generate
+end
+
+api_instance = CityPayApiClient::PaylinkApi.new
+token = 'token_example' # String | The token returned by the create token process.
+paylink_resend_notification_request = CityPayApiClient::PaylinkResendNotificationRequest.new # PaylinkResendNotificationRequest | 
+
+begin
+  # Resend a notification for Paylink Token
+  result = api_instance.token_resend_notification_request(token, paylink_resend_notification_request)
+  p result
+rescue CityPayApiClient::ApiError => e
+  puts "Error when calling PaylinkApi->token_resend_notification_request: #{e}"
+end
+```
+
+#### Using the token_resend_notification_request_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<Acknowledgement>, Integer, Hash)> token_resend_notification_request_with_http_info(token, paylink_resend_notification_request)
+
+```ruby
+begin
+  # Resend a notification for Paylink Token
+  data, status_code, headers = api_instance.token_resend_notification_request_with_http_info(token, paylink_resend_notification_request)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <Acknowledgement>
+rescue CityPayApiClient::ApiError => e
+  puts "Error when calling PaylinkApi->token_resend_notification_request_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **token** | **String** | The token returned by the create token process. |  |
+| **paylink_resend_notification_request** | [**PaylinkResendNotificationRequest**](PaylinkResendNotificationRequest.md) |  |  |
+
+### Return type
+
+[**Acknowledgement**](Acknowledgement.md)
+
+### Authorization
+
+[cp-api-key](../README.md#cp-api-key)
+
+### HTTP request headers
+
+- **Content-Type**: application/json, text/xml
+- **Accept**: application/json, text/xml
+
+
 ## token_status_request
 
 > <PaylinkTokenStatus> token_status_request(token)

data/docs/PaylinkBillPaymentTokenRequest.md

@@ -22,7 +22,7 @@ instance = CityPayApiClient::PaylinkBillPaymentTokenRequest.new(
   addressee: null,
   attachments: null,
   descriptor: null,
-  due: null,
+  due: Mon Apr 22 00:00:00 UTC 2024,
   email_notification_path: null,
   memo: null,
   request: null,

data/docs/PaylinkErrorCode.md

@@ -13,8 +13,8 @@
 require 'citypay_api_client'
 
 instance = CityPayApiClient::PaylinkErrorCode.new(
-  code: null,
-  msg: null
+  code: 1,
+  msg: An example error response
 )
 ```
 

data/docs/PaylinkResendNotificationRequest.md

@@ -0,0 +1,20 @@
+# CityPayApiClient::PaylinkResendNotificationRequest
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **email** | **Boolean** | Resends the bill payment email provided on the Paylink create token notification path. Emails can be sent up to 5 times per token. | [optional] |
+| **sms** | **Boolean** | Resends the bill payment SMS provided on the Paylink create token notification path. An SMS cannot be resent if it was previously sent less than 1 minute ago. There is a limit of 3 retries per token.  | [optional] |
+
+## Example
+
+```ruby
+require 'citypay_api_client'
+
+instance = CityPayApiClient::PaylinkResendNotificationRequest.new(
+  email: null,
+  sms: null
+)
+```
+

data/docs/PaylinkStateEvent.md

@@ -6,7 +6,7 @@
 | ---- | ---- | ----------- | ----- |
 | **datetime** | **Time** | the date and time of the event. | [optional] |
 | **message** | **String** | a message associated with the event. | [optional] |
-| **state** | **Time** | The name of the event that was actioned. | [optional] |
+| **state** | **String** | The name of the event that was actioned. | [optional] |
 
 ## Example
 
@@ -14,9 +14,9 @@
 require 'citypay_api_client'
 
 instance = CityPayApiClient::PaylinkStateEvent.new(
-  datetime: null,
-  message: null,
-  state: null
+  datetime: 2024-04-22T13:29:14Z,
+  message: message on this state,
+  state: FormInput
 )
 ```
 

data/docs/PaylinkTokenCreated.md

@@ -11,7 +11,7 @@
 | **id** | **String** | A unique id of the request. |  |
 | **identifier** | **String** | The identifier as presented in the TokenRequest. | [optional] |
 | **mode** | **String** | Determines whether the token is `live` or `test`. | [optional] |
-| **qr_code** | **String** | A URL of a qrcode which can be used to refer to the token URL. | [optional] |
+| **qrcode** | **String** | A URL of a qrcode which can be used to refer to the token URL. | [optional] |
 | **result** | **Integer** | The result field contains the result for the Paylink Token Request. 0 - indicates that an error was encountered while creating the token. 1 - which indicates that a Token was successfully created. |  |
 | **server_version** | **String** | the version of the server performing the call. | [optional] |
 | **source** | **String** | The incoming IP address of the call. | [optional] |
@@ -27,17 +27,17 @@ require 'citypay_api_client'
 instance = CityPayApiClient::PaylinkTokenCreated.new(
   attachments: null,
   bps: null,
-  date_created: null,
+  date_created: 2024-04-22T13:29:14Z,
   errors: null,
-  id: null,
-  identifier: null,
-  mode: null,
-  qr_code: null,
-  result: null,
-  server_version: null,
-  source: null,
-  token: null,
-  url: null,
+  id: 00000000-0000-0000-0000-000000000000,
+  identifier: 95b857a1-5955-4b86-963c-5a6dbfc4fb95,
+  mode: test,
+  qrcode: https://payments.citypay.com/AAAAAAA/AAAZZZCCCDDDEEE/qrcode,
+  result: 0,
+  server_version: x.x.x,
+  source: x.x.x.x,
+  token: AAAZZZCCCDDDEEE,
+  url: https://payments.citypay.com/AAAAAAA/AAAZZZCCCDDDEEE,
   usc: null
 )
 ```

data/docs/PaylinkTokenStatus.md

@@ -27,7 +27,7 @@
 | **is_validated** | **Boolean** | whether the token generation was successfully validated. | [optional] |
 | **last_event_date_time** | **Time** | the date and time that the session last had an event actioned against it. | [optional] |
 | **last_payment_result** | **String** | the result of the last payment if one exists. | [optional] |
-| **mid** | **String** | identifies the merchant account. | [optional] |
+| **mid** | **Integer** | identifies the merchant account. | [optional] |
 | **payment_attempts_count** | **Integer** | the number of attempts made to pay. | [optional] |
 | **state_history** | [**Array<PaylinkStateEvent>**](PaylinkStateEvent.md) |  | [optional] |
 | **token** | **String** | the token value which uniquely identifies the session. | [optional] |
@@ -41,10 +41,10 @@ require 'citypay_api_client'
 instance = CityPayApiClient::PaylinkTokenStatus.new(
   amount_paid: null,
   auth_code: null,
-  card: null,
-  created: null,
-  datetime: null,
-  identifier: null,
+  card: Visa/0002,
+  created: 2024-04-22T13:29:14Z,
+  datetime: 2024-04-22T13:29:14Z,
+  identifier: 95b857a1-5955-4b86-963c-5a6dbfc4fb95,
   is_attachment: null,
   is_cancelled: null,
   is_closed: null,
@@ -60,9 +60,9 @@ instance = CityPayApiClient::PaylinkTokenStatus.new(
   is_request_challenged: null,
   is_sms_sent: null,
   is_validated: null,
-  last_event_date_time: null,
+  last_event_date_time: 2024-04-22T13:29:14Z,
   last_payment_result: null,
-  mid: null,
+  mid: 11223344,
   payment_attempts_count: null,
   state_history: null,
   token: null,