Create secure token
Save the customer’s payment details to use in future transactions.
Path parameters
Unique identifier that we assigned to the terminal.
Headers
Bearer authentication of the form Bearer <token>, where token is your auth token.
Unique identifier that you generate for each request. You must use the UUID v4 format for the identifier. For more information about the idempotency key, go to Idempotency.
Request
Object that contains information about the payment method to tokenize.
Unique identifier that the merchant created for the secure token that represents the customer’s payment details. If the merchant doesn’t create a secureTokenId, the gateway generates one and returns it in the response.
Operator who saved the customer’s payment details.
Indicates how the merchant can use the customer’s card details, as agreed by the customer:
unscheduled
- Transactions for a fixed or variable amount that are run at a certain pre-defined event.recurring
- Transactions for a fixed amount that are run at regular intervals, for example, monthly. Recurring transactions don’t have a fixed duration and run until the customer cancels the agreement.installment
- Transactions for a fixed amount that are run at regular intervals, for example, monthly. Installment transactions have a fixed duration.
Customer contact and address details.
Object that contains information about the IP address of the device that sent the request.
Object that contains information for an authentication check on the customer’s payment details using the 3-D Secure protocol.
Array of customField objects.
Response
Successful request. We created a secure token that represents your customer’s payment details.
Unique identifier that the merchant created for the secure token that represents the customer’s payment details.
Unique identifier that we assigned to the terminal.
Object that contains information about the payment method that we tokenized.
Token that the merchant can use in future transactions to represent the customer’s payment details. The token:
- Begins with the six-digit identification number 296753.
- Contains up to 12 digits.
- Contains a single check digit that we calculate using the Luhn algorithm.
Status of the customer’s bank account. The processor performs a security check on the customer’s bank account and returns the status of the account.
Note: Depending on the merchant’s account settings, this feature may be unavailable.
Indicates how the merchant can use the customer’s card details, as agreed by the customer:
unscheduled
- Transactions for a fixed or variable amount that are run at a certain pre-defined event.recurring
- Transactions for a fixed amount that are run at regular intervals, for example, monthly. Recurring transactions don’t have a fixed duration and run until the customer cancels the agreement.installment
- Transactions for a fixed amount that are run at regular intervals, for example, monthly. Installment transactions have a fixed duration.
Customer contact and address details.
Array of customField objects.