Sign in
secureTokens

Update account details

Use this method to update a secure token if you have a single-use token from Hosted Fields.

Note: If you don't have a single-use token, you can update saved payment details with our Update Secure Token method. For more information about our two options to update a secure token, go to Update saved payment details.

post/processing-terminals/{processingTerminalId}/secure-tokens/{secureTokenId}/update-account

Path parameters

processingTerminalIdstring required

Unique identifier that we assigned to the terminal.

secureTokenIdstring required

Unique identifier that the merchant assigned to the secure token.

Headers

Authorizationstring required

Bearer authentication

Idempotency-Keystring uuid required

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 body

type'singleUseToken' required

Discriminator value: singleUseToken

tokenstring required

Single-use token that the gateway assigned to the payment details.

Response

Successful request. We updated the payment details represented by the secure token.

secureTokenIdstring required

Unique identifier that the merchant created for the secure token that represents the customer's payment details.

processingTerminalIdstring required

Unique identifier that we assigned to the terminal.

mitAgreement'unscheduled' | 'recurring' | 'installment'

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.
tokenstring required

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'notValidated' | 'cvvValidated' | 'validationFailed' | 'issueNumberValidated' | 'cardNumberValidated' | 'bankAccountValidated' required

Outcome of a security check on the status of the customer's payment card or bank account.

Note: Depending on the merchant's account settings, this feature may be unavailable.

Changes