Field Definitions
Common Field and their definitions
Last updated
Common Field and their definitions
Last updated
data type | min length | max length |
---|---|---|
The account number, used for bank transfers.
data type | min length | max length |
---|---|---|
The customers address. e.g. 123 Customer Street.
data type | min length | max length |
---|---|---|
Used in special cases.
data type | min length | max length |
---|---|---|
The amount processed in the system for this transaction against this sid.
Any discounts that you want recorded in the system, this . This will be deducted from the total of the transaction. Refer to amounttotal for calculation details.
Any amount being charged for shipping, that you want recorded in the system. This will be added to the total of the transaction. Refer to amounttotal for calculation details.
Any amount of tax being charged that you want recorded in the system. This will be added to the transaction. Refer to amounttotal for calculation details.
The amounttotal field is the calculated total of the transaction based on all information sent in, the total value of the cart items, shipping, tax minus any coupon amount.
The amounttotal is always used displaying any all minor units. e.g. USD$17 is used as 17.00 JPY¥17 is used as 17
Calculating the amounttotal follows this pseudocode:
This is a campaign code as provided by the associated affiliate system. Only use if information is provided.
The security code on the customers cards. Also known as, CCV, CVV, CVC and CSC. This is not the Card PIN.
The expiry month for the customers card. Should be 0 filled. e.g. 1 (January) should be sent as 01. 2 should be sent as 02.
The expiry year for the customers card. Should be 0 filled. And is only 2 digits long. e.g. 2001 should be 01. 2022 should be 22..
Also known as the PAN. This is the full credit card number. It should not have any punctuation or separators when sent. The system will not filter for any punctuation or separators and will just fail the transaction.
This is the payment method. It should be indicative of the payment type.
e.g.
visa
mastercard
bank
They paymethod should be provided to you at onboarding time. The payment methods available for your sid can also be retrieved using the rawfee API.
The country code that belongs to the customers credit card. This should be the Alpha 3 ISO 3166 country code.
The 3 Alpha character ISO 4217 code for the currency.
The name of the payment descriptor that was used on the SID to complete the payment. This should be indicative of the Name / Title that will appear on the customers Bank Statement.
The customers email address.
If the error is generated by TxProcess this is a 3 character integer number corresponding to our internal error code list. If created by an external system this can be of any length.
Where possible, an extended explanation of what caused the error / details about it.
The raw error message generated.
Where possible, the module that generated the error.
The customers first name.
The hash is a secure signature that is generated when you communicate with TxProcess. Every time you communicate with TxProcess and will create a Payment Record / Transaction in the system you will be required to create a hash to verify the contents of the transaction it self, and to complete your authentication with the system.
The hash is the md5 of
sid
i.e. md5('22'.'1234568995265421'.'17.00'.'USD'.'222b6c')
Required for ACH transactions.
A short text description of the item being purchase. e.g. A shiny Red Delicious
The cost of the item, per each unit. This is used in the amounttotal calculation. If you are selling 1 bag of apples, then it's the price per bag. If you are charging for each individual apple, it's the price per apple.
The item name. E.g. Apple_Red
The identification number / stock number for the item.
How many of the item was bought. This is used in the amounttotal calculation.
The customers lastname.
The customers mobile number.
The parent transaction id of the transaction. If this transaction is part of a series of transactions (Asynchronous transactions for e.g.) this is the parent transaction id that can be used to link all transactions together.
The customers land line phone number. Not their mobile phone number. For mobile phone number see mobile.
The postcode / zip code of the customer.
The URL to POST data to, when a transaction type has finished, or receives an update. For e.g. if an transaction has a status of PENDING and a final status is determined, you should receive a postback notification of both states. First the PENDING state, and then when a final status is determined a second notification. Handling this endpoint on the merchants end is very important, particularly for Asynchronous transactions that will have no other way to communicate the final result to the merchant.
The rcode will be provided to you at onboarding. The rcode should never be sent in as plain text with the payment data. It is the equivalent to your password and should never be accessible / viewable online.
A complete URL of the page that you want the customer redirected too, after the transaction has completed processing. They will be redirected with the data from the corresponding responses section.
An extra reference field on top of the tid field that the merchant can use to store a reference. Note, that this does not replace the tid.
An extra reference field on top of the tid field that the merchant can use to store a reference. Note, that this does not replace the tid.
An extra reference field on top of the tid field that the merchant can use to store a reference. Note, that this does not replace the tid.
An extra reference field on top of the tid field that the merchant can use to store a reference. Note, that this does not replace the tid.
The routing or transit number, used for bank transfers.
The shipping address. e.g. 123 Customer Street.
The shipping country code. This should be the Alpha 3 ISO 3166 country code.
The first name of the person receiving the parcel.
The first name of the person receiving the parcel.
The shipping postcode / zip code of the customer.
The shipping state for the transaction.
The shipping suburb or city of the transaction.
The sid (Site ID) will be provided to you at onboarding.
The customers billing state.
The result of the transaction
The billing suburb or city of the customer.
Expects be a JSON object with a collection of ThreeDSecure(3DS) fields and their values. This is for the Authorization transaction, after a 3DS Authentication transaction has already occurred. To complete a 3DS Authentication, please contact support and they will help guide you for your specific integration. The particular fields and their naming can be different depending on how the Authentication is done, and the payment processor being used.
The txid (transaction id) that the system generated for this transaction.
The timestamp is to be a Unix timestamp
the transaction type. e.g. PAYMENT
or SETTLEMENT
The transaction id for this transaction. If this is the first in a series of transactions, this could be the same as the parent_txid . If it is not the first, there will be a parent_txid that will be used to group all of the series together.
Some response form TxProcess, in particular in response to a call that generated a transaction, will return a vrfy field, so that you can validate the response hasn't been tampered with before receiving it. All the values except the rcode will be in the response returned.
Note that the vrfy string in contrast to the hash string has a separator(;) in between the values.
The vrfy is the sha256 of
sid
tx_action
sha256(sid;rcode;txid;status;amount;currency;txaction)
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
data type | min length | max length |
---|---|---|
string
0
-
string
0
255
string
0
30
decimal
0
9
decimal
0
9
decimal
0
9
decimal
0
9
decimal
0
-
string
0
-
integer
3
6
integer
2
2
integer
2
2
integer
13
20
string
0
255
string
3
3
string
3
3
string
1
50
string
0
150
string
0
-
string
0
-
string
0
-
string
0
-
string
0
-
string
0
100
string
32
32
string
3
3
string
0
255
decimal
0
9
string
0
255
string
0
255
integer
0
10
string
0
100
string
0
25
string
16
16
string
0
25
string
0
16
string
0
255
string
0
40
string
0
255
string
0
255
string
0
255
string
0
255
string
0
2048
string
0
14
string
0
255
string
3
3
string
0
100
string
0
100
string
0
16
string
0
32
string
0
60
string
0
11
string
0
32
string
0
10
string
0
60
string
0
-
string
0
255
string
10
10
string
0
15
string
16
16
string
256
256