Preauth Request

Please see below for information on configuring the Preauth Request, as well as the expected Preauth Response.

txPreauthRequest

Supported on PayDroid terminals only, not compatible with Linux devices.

For a typical pre-auth request the client must provide the same info as for txSaleRequest except for the following:

Field Type Length (chars) Description Example Card terminal support
msgType String 3 '100' '100' Android Card Terminals

The above information elements must be joined into one single string using ‘|’ as a separator. i.e.

0063|002690|100|00|12345678901234567890123456789012|123.50|0000||||

If the resulting string gets appropriately transmitted to the terminal, the terminal will respond with a txPreauthResponse message.

txPreauthResponse

Supported on PayDroid terminals only, not compatible with Linux devices.

After executing a Pre-auth transaction the terminal responds with a txPreauthResponse to indicate if the transaction has been approved or not.

A txPreauthResponse for an approved transaction looks as follows:

Android Card Terminals:

0248|000042|110|00|00|Contactless/None~RRN:204814800832|MASTERCARD|537535******9228|800832|008179|000001|10.00|00|00|00|00|00|00|00| 16000281|2048160114000202|2048160114||||||||1cf9a839-7dcd-49f1-937c-bb47dfda67b2|2022-02-17T16:42:26.1290935+02:00|3

The contents of the response is the same as for txSaleResponse with the exception of the following:

Field Type Length (chars) Description Example Card terminal support
msgTypeResp String 3 ‘110’ ‘110’ Android Card Terminals

Failure reasons

See Failure reasons and ISO codes under txSaleResponse. These are the same for all transaction types (Sales, Cancelations and Pre-auths).

Get Support

If you have any questions about our solutions, or questions about how to integrate with our solutions, please refer to our Get Support page.