...
You can develop the application in one of two ways:
- by By yourself using the information provided in this document
- use merchant Plus By using merchantPlus sample code available for free from our Developer Center.
...
| Field Name | Description |
|---|---|
| x_login | Value: The merchant’s unique Login ID Format: Up to 20 character Notes: The merchant API Login ID is provided in the Merchant Interface and must be stored securely. The Login ID and Transaction Key together provide the merchant the authentication required for access to the payment gateway. |
| x_tran_key | Value: The merchant’s unique Transaction Key Format: 16 character Notes: The merchant Transaction Key is provided in the Merchant Interface and must be stored securely. The API Login ID and Transaction Key together provide the merchant the authentication required for access to the payment gateway. |
| x_Method | Value: The Method of credit card transaction Format; CC , SVP Notes :If this field is not submitted or the value is blank, the payment gateway will generate a an error "x_Method cannot be left blank". |
| x_type | Value: The type of credit card transaction Format; AUTH_CAPTURE (default), AUTH_ONLY, CREDIT, PRIOR_AUTH_CAPTURE, VOID ( for FirstData and Tsys transaction ) Notes: If the value submitted does not match a supported value, the transaction is rejected. If this field is not submitted or the value is blank, the payment gateway will generate a an error "x_type cannot be left blank". |
| x_amount | Value: The amount of the transaction Format; Up to 15 digits (no dollar symbol). For example, 102 Notes: This is the total amount and must include tax, shipping, and any other charges, . If this field is not submitted or the value is blank, the payment gateway will generate a an error "x_amount cannot be left blank". |
| x_card_num | Value: The customer’s credit card number Format; Between 13 and 16 digits without spaces. Notes: This is sensitive cardholder information and must be stored securely and in accordance with the Payment Card Industry (PCI) Data Security Standard. If this field is not submitted or the value is blank, the payment gateway will generate a an error "x_card_num cannot be left blank". |
| x_exp_date | Value: The customer’s credit card expiration date. Format; MMYY Notes: This is sensitive cardholder information and must be stored securely and in accordance with the Payment Card Industry (PCI) Data Security Standard. If this field is not submitted or the value is blank, the payment gateway will generate a an error "x_exp_date cannot be left blank". |
| x_trans_id | Value: The payment gateway-assigned ID that links the current authorization request to the original authorization request. Format; Numeric Notes: This value applies only to partial authorization transactions, and is returned in the reply message from the original authorization request. If this field is not submitted or the value is blank, the payment gateway will generate a an error "x_trans_id cannot be left blank".
|
| x_delim_data | Value: Indicates whether a delimited transaction response is required Format; TRUE, T, YES, Y Notes: A value of TRUE indicates a request for delimited response from the payment gateway. Since all AIM transactions are direct response, a value of TRUE is required. Submit this field for each transaction to be sure that transaction responses are returned in the correct format. See "Transaction Response," for more about delimited response. |
...