Request Fields
You can perform a new transaction, such as a sale, by sending a request with the required action and transaction type together with details about the order and payment method.
| Field Name | Mandatory? | Description |
|---|---|---|
| merchantID | Yes | Your Gateway Merchant Account ID. |
| merchantPwd | No[1] | Any password used to secure this account. Refer to the Password Authentication section for details. |
| signature | Yes[2] | Any hash used to sign this request. Refer to the Message Signing section for details. |
| action | Yes | The action requested. Refer to the Supported Actions section for details. Possible values are: PREAUTH, VERIFY, SALE, REFUND, REFUND_SALE. If a REFUND_SALE action is used, then the request must not attempt to change the payment details, or it will fail with a |
| amount | Yes[3] | The amount of the transaction. |
| type | Yes[3] | The type of transaction. Refer to the Transaction Types section for details. Possible values are: 1 – E-commerce (ECOM) 2 – Mail Order/Telephone Order (MOTO) or Card Not Present (CNP) 9 – Continuous Authority (CA) |
| countryCode | Yes[3] | The country where the transaction takes place. |
| currencyCode | Yes[3] | Transaction currency. |
| paymentMethod | No | The payment method required. For card payments either omit this field or use the value card. |
| cardNumber | Yes[3,4] | The primary account number (PAN) as printed on the front of the payment card. Digits and spaces only. |
| cardExpiryMonth | Yes[3,4] | Payment card’s expiry month from 1 to 12. |
| cardExpiryYear | Yes[3,4] | Payment card’s expiry year from 00 to 99. |
| cardExpiryDate | No[3,4] | Payment card’s expiry date in MMYY format as an alternative to sending a separate cardExpiryMonth and cardExpiryYear. |
| cardCVV | Yes[3,4] | Payment card’s security number. The 3-digit number printed on the signature strip. |
| transactionUnique | No[3] | You can supply a unique identifier for this transaction. This is an added security feature to combat transaction spoofing. |
| orderRef | No[3] | Free format text field to store order details, reference numbers, etc for the Merchant’s records. |
| orderDate | No | Optional date to record with the transaction. |
| captureDelay | No | Number of days to wait between authorisation of a payment and subsequent settlement. Refer to the Duplicate Transaction Checking section for details. |
| xref | No[5] | Reference to a previous transaction. Refer to the Payment Tokenisation section for details. |
| redirectURL | No[6] | URL to which the hosted form will redirect the Customer’s browser after the transaction has been completed. The URL must be fully qualified and include at least the scheme and host components. Refer to the Redirect URL section for details. |
| callbackURL | No[6] | URL which will receive a copy of the transaction result by POST. The URL must be fully qualified and include at least the scheme and host components. Refer to the Callback URL section for details. |
| deviceIpAddress | No[7] | IP address of client making the transaction using dotted decimal notation (eg. 1.12.123.255) or an IP v6 address using colon hexadecimal notation (eg 2011:0db8:85a3:0101: 0101:8a2e:0370:7334). This should be provided where possible to aid fraud prevention. |
| rtAgreementType | No[8] | Agreement between Merchant and Cardholder for the storage of, or subsequent use of, payment details. Refer to the Credentials on File section further details. |