One-Click Checkout


Here’s a different scenario - the cardholder is present on your website, but you still need us to decrypt a previously stored card number for the payment method. Just set the subscription_type parameter to REUSE.



Time to play - access your API using these endpoints:

Here’s an example of a REUSE authorisation request including both CVV and 3-D Secure:


REUSE Request Parameters

Parameter Format Length Description
subscription_type string 4 - 14 Set to REUSE to use an exisitng token.
Acceptable Characters: a-Z A-Z _
original_transaction_id int 1 - 11 transaction_id value we generated and returned in the original INIT request.
Acceptable Characters: 0-9
amount int 1 - 11 Transaction amount.
Acceptable Characters: 0-9 in the format DDDDDD.CC
currency_code_iso3 string 3 Transaction currency, an ISO 4217 3-digit code.
Acceptable Characters: a-z A-Z
billing object
cardcvv int 3 - 4 The 3 - 4 digit card verification number.
Acceptable Characters: 0-9
tds object
action string 7 - 10 Set value to ENQUIRE

But wait, you may say. REUSE is the same as REBILL, right? Not quite. Using REUSE instead of REBILL lets the card issuer know that the cardholder was present on your website when the payment initiates and you process an adhoc payment. It’s a security thing.

Here’s some information on implementing 3-D Secure as part of a REUSE request. If you go that route, the resulting ENQUIRE response will follow the typical 3D Secure format and flow.

Otherwise, the REUSE response is the same as a standard authorisation transaction type. You can look that up here.

Key info - When processing a reuse request, the transaction will be required to be authenticated using 3-D Secure 2.1 from 14th September 2019 and onwards due to SCA requirements.

Hosted Payment Page


Time to play - access your API using these endpoints:

Coming Soon!