Merchant API client account identifier.

Identifier of your application (website).

API version.

Base Currency: The user's account currency on the merchant site.

URL to which the pre-deposit validation will be sent.

Action to be taken within the cashier. Allowed values are:

• authorization for authorization (hold) for the following capture.
• payment for payment transaction.
• withdrawal for withdrawal request.

intent defines the primary Cashier intent and the initial Cashier view opened for the user. If secondary_intents is provided, the user can switch inside Cashier between the primary intent and the additional intent configured in secondary_intents.

HASH value of customer's identity.

Note: Either customer_token or customer_data must be provided. If both are missing, the request will trigger a validation error.

Payment method. The gateway will override this value if provided.

1. The gateway parameter is not applicable for Credit Card method for payouts;

2. The predefined gateway hash value: "credit_card_cascade_gateway_0000" can be used instead of payment_method: "Credit Card" for payments.

3. Either gateway or payment_method should be provided in case of 0-Auth and CIT transactions.

Gateway hash

1. For authorization,payment: hash of the gateway doing the processing.

2. For withdrawal: hash of non-credit card gateway doing the processing.

3. Either gateway or payment_method should be provided in case of 0-Auth and CIT transactions.

Type of the session. Allowed values are: - cashier, - payment_link. Payment Link type allows to initiate Cashier session with an extended lifetime (expires) - up to 72 hours.

Cashier UI Preset. If empty, the default preset for Cashier UI from the application configuration will be used. If not empty, the value will override the application configuration.

Unique customer id in your system.

Note: Personally Identifiable Information (PII), such as email addresses, is strictly forbidden. If your user identifier contains any PII, you must hash or encrypt it before sending it to the API.

User locale, specified as a BCP 47 Language Tag (e.g., 'en-GB'). The first component is the ISO 639-1 language code, and the second is the ISO 3166-1 country code.

Note: Contact [email protected] to add new locale if not available in the list.

Transaction or session identifier in your system.

URL to which the deposit status notification will be sent.

User will be redirected to a specified URL(relevant for cashier login, virtual terminal, 3D Secure and E-Wallet login redirect).

Deep link of your mobile app (a URI with a custom scheme, for example yourbrand://checkout/callback, not an http or https address), to which the payment provider returns the customer after the payment in the provider's app. Pass it when Cashier is opened in a WebView of your app and the customer pays with a method that needs it, for example Revolut Pay.

Note: for Revolut Pay in a WebView, your app must intercept the deep link (on Android, also the links that start with merchant.revolut.com), return the customer to the same WebView with Cashier (not a new one), and check the final status of the transaction on your backend: the deep link is not a confirmation of the payment.

Your custom field to tag the transaction with some necessary information.

Your custom field to tag the transaction with some necessary information.

Your custom field to tag the transaction with some necessary information.

Authentication HTTP header of your outgoing request to the API.
Below request parameters should be used for creating signature in request header.

• merchant_id
• application_key
• timestamp
• intent
• cid
• order_id