Reach Reach is a gateway that allows you to collect card payments. This guide is intended to help you implement Reach 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) ( API ) Void ( API ) Refund (partial and multiple) ( API )
Supported processing currencies	AED, ALL, AMD, ANG, AOA, ARS, AUD, AWG, AZN, BAM, BBD, BDT, BGN, BHD, BMD, BND, BOB, BRL, BSD, BWP, BYN, BZD, CAD, 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, LYD, MAD, MDL, MNT, MOP, MRU, MUR, MVR, MWK, MXN, MYR, 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, STN, SVC, SZL, THB, 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

Your system must support the 3D Secure (3DS) customer redirect flow. For more information, view the 3DS requirements tutorial.
You must configure and use webhooks as part of the 3DS workflow. For more information, view the Webhooks tutorial.
Reach has an asynchronous workflow. It's sometimes necessary to present a "pending" status to the user instead of a confirmation message because the bank authorization isn't always immediate. It's important to pay attention to the actual transaction status to ensure the correct message is displayed. For information about the possible values, see the Transaction status reference table.
The security code must be present for the first transaction through Reach, meaning customers on file need to re-enter the security code.
paymentType is supported.

Configuration

Work with Integrations Support to add Reach as a connection. You will need the following credentials from Reach:

merchant ID
secret

Required fields

The following fields are additionally required when processing a payment request with Reach:

data.customer.firstname
data.customer.lastName
data.customer.email
data.customer.billToAddressOne
data.customer.billToCity
data.customer.billToCountry
data.customer.shipToAddressOne
data.customer.shipToCountry
data.customer.shipToCity
card.cardHolderName

Testing data

Use the following test card information to test your Reach configuration.

Brand	Card number	Expiration date	Security code	Cardholder name	`check3ds`	3DS Password	3DS Result	Transaction result
Visa	4242424242424242	03/30	100	Any	`false`	N/A	N/A	Success
Visa	4242424242424242	03/30	000	Any	`false`	N/A	N/A	Failure
Visa	4242424242424242	03/30	100	Any	`true`	Checkout1!	Success	Success
Visa	4242424242424242	03/30	000	Any	`true`	Checkout1!	Success	Failure
Visa	4242424242424242	03/30	100	Any	`true`	123	Failure	Failure
Mastercard	5436031030606378	Any future date	257	Any	`false`	N/A	Success	Success
Mastercard	5436031030606378	Any future date	000	Any	`false`	N/A	Failure	Failure
Mastercard	5436031030606378	Any future date	257	Any	`true`	(frictionless)	Success	Success
Mastercard	5436031030606378	Any future date	000	Any	`true`	(frictionless)	Failure	Failure
American Express	345678901234564	Any future date	1051	Any	`false`	N/A	Success	Success
American Express	345678901234564	Any future date	0000	Any	`false`	N/A	Failure	Failure
American Express	345678901234564	Any future date	1051	Any	`true`	(frictionless)	Success	Success
American Express	345678901234564	Any future date	0000	Any	`true`	(frictionless)	Failure	Failure
Discover	6011111111111117	03/30	100	Any	N/A	N/A	N/A	Success
Diners	30123456789019	03/30	257	Any	N/A	N/A	N/A	Success

Status workflows

The status of a successful transaction with Reach varies, depending on the options you choose.


Sale	When `isAuthOnly` is `false`, successful sale transactions will have the following statuses: pending* or authorized settled
Auth only	When `isAuthOnly` is `true`, successful sale transactions will have the following status: authOnly
Capture	Successful capture transactions will have the following statuses: pending* or authorized settled
Void	Successful void transactions will have the following status: voided
Refund	Successful 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.