Guides

Trust My Travel integration guide

Trust My Travel 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
  • Card
Supported transaction types
  • Sale (saved card token) ( API )
  • Auth Only (saved card token) ( API )
  • Capture (partial and greater than) ( API )
  • Void ( API )
  • Refund (partial and multiple) ( API )
Supported processing currenciesAED, 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 supportedYes
3D Secure 2.x supportedYes
External 3D Secure supportedNo
Installments supportedNo

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 the pay/v3/process call.

Testing data

Use the following test card information to test your Trust My Travel configuration.

BrandCard numberExpiration dateSecurity codeCardholder name3DSTransaction result
Visa4242424242424242Any future date100AnyN/AN/A
Visa4111111111111111Any future date123AnyN/ASuccess
Mastercard5436031030606378Any future date257AnyN/AN/A
Mastercard5105105105105100Any future date123AnyN/AFailure
Amex345678901234564Any future date1051AnyN/AN/A
Discover6011111111111117Any future date100AnyN/AN/A
JCB3530111333300000Any future date100AnyN/AN/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).

AmountDecline Reason
xxx.05Do not honor
xxx.12Invalid payment
xxx.14Invalid card number
xxx.51Insufficient funds
65.10Soft 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.

SaleWhen isAuthOnly is false, successful sale transactions will have the following statuses:
  • pending* or authorized
  • settled
Auth onlyWhen isAuthOnly is true, successful sale transactions will have the following status:
  • authOnly
CaptureSuccessful capture transactions will have the following statuses:
  • pending* or authorized
  • settled
VoidSuccessful void transactions will have the following status:
  • voided
RefundSuccessful refund transactions will have the following statuses:
  • pending* or authorized
  • settled

*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 about 1 month ago