Account Binding
POST
/snap/v{version}/registration-account-binding
POST
/snap/v{version}/registration-account-bindingUse this API to store card information
Structure
A message consists of a header and body. The following sections are focused on the body structure. For the header structure, see:
Request Parameters
partnerReferenceNo String
Required
String
RequiredUnique invoice number to identify the order on the merchant side, which is assigned by the merchant.
action String
Required
String
RequiredPossible values: StoreCard
merchantId String
Required
String
RequiredUnique merchant ID that is registered with 2C2P
phoneNo String
Required
String
RequiredPhone number of Customer
additionalData Object
Required
Object
RequiredShow Child Parameters
userId String
Required
Full name of customer
email String
Required
Customer's email address
additionalInfo Object
Required
Object
RequiredShow Child Parameters
key Object
Required
Encrypted Key
cardNo String
Required
Encrypted Card Number
expiryMonth String
Required
Encrypted Card Expiry Month
expiryYear String
Required
Encrypted Card Expiry Year
Response Parameters
responseCode String
Required
String
RequiredResponse code.
Possible values are listed in the response codes table on this page.
responseMessage String
Required
String
RequiredResponse message that explains the response code.
accountToken String
String
Customer Token of the saved card details
Updated 2 days ago