Paylink provides cardholder account support for referencing a store payment card details. This can be used to facilitate discrete bill payments and subscription style payments made under the continuing authority of the Customer. Paylink provides support for the acquisition and updating of payment card and cardholder information using the hosted Payment Form.
The Paylink API allows Merchant Applications to
- specify, on an individual transaction basis, whether a Cardholder Account is to be created when a transaction is successfully authorised; and
- obtain updated payment card information for use with a particular Cardholder Account.
To enhance Paylink to create card holder accounts, your account will need to be setup to accept this option.
A cardholder account is identified using an account number parameter
accountNo which is used to reference the account once created. The account number is within the bounds of your Client account allowing multiple merchant ids to be used against a single card holder account. Should a Transaction, on processing, be found to match an existing account, the transaction will be marked against that account. Should the card details have changed, these values are also updated.
Transactions initiated using the Paylink Payment Form are processed and coded as e-commerce transactions which provides for full validation of the payment card holder using 3D-Secure, CSC and AVS. Subsequent transactions are ordinarily coded as continuing authority transactions using batch processing through the CityPay API .
To process payments under using the Cardholder Account features of Paylink, the Merchant must obtain the prior agreement of the relevant Acquirer to allow the Merchant to process transactions subject to continuing authority. Additionally, it is recommended that the Merchant Application expressly obtains the consent of the Customer to be able to perform transactions under continuing authority, and to provide a mechanism for resolving disputes to avoid unnecessary chargeback events.
Enabling Card Holder Account Transactions
This can be performed by contacting your support representative. Once you have been notified that this has been enabled, the following options are programmable by your API integration.
- construct the Token Request in accordance with the basic integration
- obtain and record prior consent of the Customer to process the Transaction associated with the Token Request, and future transactions under continuing authority;
- specify the
config.optionsfield and include the option "
- add the
accountNofield to individually reference the Cardholder Account used
- optionally specify the firstName of the account holder;
- optionally specify the lastName of the account holder;
Card Holder Account Extensions to the Response
cacis equal to 0 – no action is carried out
cacis equal to 1 – an account has been loaded and processed
cacis equal to 2 – an account was created using the value in the
cacis equal to 3 – an account was updated recording any change of the billing address, the expiry date or card number