API Reference

Create Payment Request

post
https://gw.payracks.com/cashier/virtual-terminal
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required
≤ 32

Name of the agent performing the VT login on behalf of the customer.

string
required
length ≤ 50

Merchant API client account identifier.

string
required
length ≤ 32

Identifier of your application (website).

string
required
length ≤ 3

API version.

integer
required

Request time (unix timestamp, seconds).

string
required
length ≤ 10

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

integer
≤ 20

Customer's withdrawable balance in cents. Can be used for automatic amount validation during the withdrawal request submission (send null to bypass the validation).

string
length ≤ 256

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

string
enum
required
length ≤ 32

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.
Allowed:
customer_data
object

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.

string
length ≤ 32

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.

string
length ≤ 50

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.

string
length ≤ 32

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.

integer

Transaction amount in cents.

Note: For certain currencies there is a fraction other than 100 cents per unit, this is important if you multiply by 100 to send the amount in cents.

string
required
length ≤ 50

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.

string
enum
required
length ≤ 5

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.

string
required
length ≤ 50

Transaction or session identifier in your system.

string
required
length ≤ 256

URL to which the deposit status notification will be sent.

string
required
length ≤ 256

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

string
length ≤ 256

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

string
length ≤ 256

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

string
length ≤ 256

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

Headers
string
required

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
  • agent_name
Responses

Updated 20 days ago

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 20 days ago