Trust My Travel integration guide
Trust My Travel is a gateway that allows travel providers a way to protect customers and accept global payments. This guide is intended to help you implement Trust My Travel based on your preferred integration workflow.
Services and compatibility
Supported payment types |
|
Supported transaction types | |
Supported processing currencies | AED, AFN, ALL, AMD, ANG, AOA, ARS, AUD, AWG, AZN, BAM, BBD, BDT, BGN, BHD, BIF, BMD, BND, BOB, BRL, BSD, BWP, BYN, BZD, CAD, CDF, CHF, CLP, CNY, COP, CRC, CVE, CZK, DJF, DKK, DOP, DZD, EGP, ETB, EUR, FJD, FKP, GBP, GEL, GHS, GIP, GMD, GNF, GTQ, GYD, HKD, HNL, HRK, HTG, HUF, IDR, ILS, INR, ISK, JMD, JOD, JPY, KES, KGS, KHR, KMF, KRW, KWD, KYD, KZT, LAK, LBP, LKR, LRD, LSL, LYD, MAD, MDL, MGA, MKD, MMK, MNT, MOP, MUR, MVR, MWK, MXN, MYR, MZN, NAD, NGN, NIO, NOK, NPR, NZD, OMR, PAB, PEN, PGK, PHP, PKR, PLN, PYG, QAR, RON, RSD, RUB, RWF, SAR, SBD, SCR, SEK, SGD, SHP, SLL, SOS, SRD, SVC, SZL, THB, TJS, TND, TOP, TRY, TTD, TWD, TZS, UAH, UGX, USD, UYU, UZS, VND, VUV, WST, XAF, XCD, XOF, XPF, YER, ZAR, ZMW |
3D Secure 1.x supported | Yes |
3D Secure 2.x supported | Yes |
External 3D Secure supported | No |
Installments supported | No |
Gateway-specific information
paymentType
is supported.- You must support the customer redirect flow for 3DS. For more information, see the 3D Secure overview.
- Configuring and utilizing webhooks is necessary as part of the 3DS workflow.
- Allocations for merchant bank account deposits can be designated on a per-transaction basis. For more information, contact Integrations Support.
Configuration
Work with Integrations Support to add Trust My Travel as a connection. You will need the following credentials from Trust My Travel:
- Username for Trust My Travel
- Password for Trust My Travel
- Site Path - Find this value in the Settings in the Trust My Travel dashboard.
- TokenEx ID - Find this value by going to a Channel, selecting the Gateways tab, and finding the Tokenex ID field (note that this is not the same as the Nexio TokenEx credential).
- TokenEx API Key - Find this value by going to a Channel, selecting the Gateways tab, and finding the Tokenex API Key field (note that this is not the same as the Nexio TokenEx credential).
Required fields
The following fields are required when processing a payment request with Trust My Travel:
card.securityCode
- Required for Save card token (pay/v3/saveCard) endpoint.data.amount
data.currency
data.customer.billToAddressOne
*data.customer.billToCity
*data.customer.billToState
*data.customer.billToPostal
*data.customer.billToCountry
*data.customer.firstName
*data.customer.lastName
*data.customer.email
*data.customer.orderNumber
data.customer.orderDate
- In YYYY-MM-DD format.processingOptions.paymentType
processingOptions.requireCvc
- Required for Create one-time-use token (pay/v3/token) endpoint when using Nexio iframe for Save card token or Run card transaction.
Note
* If these data points are included in the
pay/v3/token
call, they will be stored with the card token and will not need to be passed with thepay/v3/process
call.
Testing data
Use the following test card information to test your Trust My Travel configuration.
Brand | Card number | Expiration date | Security code | Cardholder name | 3DS | Transaction result |
---|---|---|---|---|---|---|
Visa | 4242424242424242 | Any future date | 100 | Any | N/A | N/A |
Visa | 4111111111111111 | Any future date | 123 | Any | N/A | Success |
Mastercard | 5436031030606378 | Any future date | 257 | Any | N/A | N/A |
Mastercard | 5105105105105100 | Any future date | 123 | Any | N/A | Failure |
Amex | 345678901234564 | Any future date | 1051 | Any | N/A | N/A |
Discover | 6011111111111117 | Any future date | 100 | Any | N/A | N/A |
JCB | 3530111333300000 | Any future date | 100 | Any | N/A | N/A |
In addition, you can test Transaction failure using the following values for amount
and the expiration date at least one month in the future. Replace the "xxx" with three digits (for example, with xxx.05
you could use 123.05
).
Amount | Decline Reason |
---|---|
xxx.05 | Do not honor |
xxx.12 | Invalid payment |
xxx.14 | Invalid card number |
xxx.51 | Insufficient funds |
65.10 | Soft decline (Enable 3DS) |
For additional testing information, see Test Credit Cards on the Trust My Travel website.
Status workflows
The status of a successful transaction with Trust My Travel varies, depending on the options you choose.
Sale | When isAuthOnly is false , successful sale transactions will have the following statuses:
|
Auth only | When isAuthOnly is true , successful sale transactions will have the following status:
|
Capture | Successful capture transactions will have the following statuses:
|
Void | Successful void transactions will have the following status:
|
Refund | Successful refund transactions will have the following statuses:
|
*Pending status displays as "authorized" or "AUTHORIZED" in the Nexio Dashboard; it displays as 10
, meaning "authorized", in the response when querying transactions (for more information about transactionStatus
, see the appropriate transactionStatus
table).
If you have any additional questions or feedback, contact us.
Updated 14 days ago