|
|
Unique merchant-generated identifier. Must be unique for each transaction. Used to check for duplicate transaction attempts
|
|
|
Indicates the language to use for the payment page content
|
|
|
The type of transaction and the permissible applications (sale, authorization, create_payment_token, update_payment_token)
|
|
|
Unique merchant-generated order reference for each transaction
|
|
|
Defines the value of the order. Must be 0 or greater
|
|
|
Defines the currency of the order. 3 characters
|
|
|
The date and time that the signature was generated. Must be in UTC Date and Time format and is used to validate against duplicate requests.
|
|
|
Method of payment. Valid values can either be 'card', 'echeck' or 'paypal'
|
|
|
Customer First Name. Maximum 60 characters
|
|
|
Customer Last Name. Maximum 60 characters
|
|
|
Customer email address. Maximum 255 characters
|
|
|
Customer phone number. Between 6 and 15 characters
|
|
|
Customer's first line of their address. Maximum 60 characters
|
|
|
Customer city. Maximum 50 characters
|
|
|
Customer country. 2-character ISO country code
|
|
|
Customer postcode. Characters region dependant, but generally 10 characters
|
| Unsigned data |
|
|
Scheme/issuer. 001=VISA, 002=Mastercard, 003=Amex, 004=Discover, 005=Diners, 007=JCB, 024 Maestro UK. 3 characters
|
|
|
Customer card number. Maximum 20 characters
|
|
|
Customer card expiry date. Must follow MM-YYYY format. 7 characters
|
|
|
Customer's card verification number. Maximum 4 characters
|
| Do not change unless absolutely necessary |
|
|
Key data required for payment submission
|
|
|
Profile reference associated with the Fuse MID and keys
|
| Signed/unsigned names |
|
|
This field is used to generate a signature that is used to verify the content of the transaction
|
|
|
A comma-separated list of request fields that are not signed.
|
|
|