DocumentationRecipesAPI ReferenceChangelog
Documentation

QuickPay Send Link Request Parameters

📘

Data Attribute Reference

Data Type

  • A: Alphabet
  • AN: Alphanumeric
  • NT: NText
  • C: Characters
  • B: Boolean
  • D: Decimal
  • N: Numeric

Mandatory attributes

  • M: Mandatory
  • C: Conditional
  • O: Optional
🚧

Sending Method

Merchants must indicate whether to send the link via email OR sms (only one can be used per call)

Set the Sending parameter to either toEmails or toMobiles

ParameterData Type / LengthMandatoryDescription
versionAN 3MRequest version number
  • Current version:* 2.4
timeStampAN 14MRequest time stamp
  • In yyyyMMddHHmmss format
merchantIDAN 15MMerchant ID provided by 2C2P
qpIDAN 10MQuickPay ID
toEmailsAN 255OEmail address to receive QuickPay link
  • Separate multiple email addresses with a semicolon (“;”)
ccEmailsAN 255OEmail address to receive CC of QuickPay link
  • Separate multiple email addresses with a semicolon (“;”)
bccEmailsAN 255OEmail address to receive BCC of QuickPay link
  • Separate multiple email addresses with a semicolon (“;”)
emailSubjectAN 255CSubject of email*Accepts all characters except special characters of > and <
  • Mandatory when toEmails is supplied
emailMessageAN 255CBody of email*Accepts all characters except special characters of > and <
  • Mandatory when toEmails is supplied
toMobilesAN 255OMobile number to receive QuickPay link
  • Separate multiple mobile numbers with a semicolon (“;”)
  • In international format: CountryCodeAreaCode-TelephoneNumber
  • Example: +66889999999
smsMessageAN 60CBody of SMS*Accepts all characters except special characters of > and <
  • Mandatory when toMobiles is supplied
hashValueAN 150MHMACSHA1 cryptographic hash value of:
version + timeStamp + merchantID +
qpID + toEmails + ccEmails +
bccEmails + emailSubject + emailMessage + toMobiles +
smsMessage
  • Uses secret key provided by 2C2P to merchant

Updated 8 months ago