Reach integration guide

ReachReach 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 ( API )
  • Auth Only ( API )
  • Capture (partial) ( API )
  • Void ( API )
  • Refund (partial and multiple) ( API )
Supported processing currenciesAED, 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 supportedYes
3D Secure 2.x supportedYes
Installments supportedNo

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.

BrandCard numberExpiration dateSecurity codeCardholder namecheck3ds3DS Password3DS ResultTransaction result
Visa424242424242424203/30100AnyfalseN/AN/ASuccess
Visa424242424242424203/30000AnyfalseN/AN/AFailure
Visa424242424242424203/30100AnytrueCheckout1!SuccessSuccess
Visa424242424242424203/30000AnytrueCheckout1!SuccessFailure
Visa424242424242424203/30100Anytrue123FailureFailure
Mastercard5436031030606378Any future date257AnyfalseN/ASuccessSuccess
Mastercard5436031030606378Any future date000AnyfalseN/AFailureFailure
Mastercard5436031030606378Any future date257Anytrue(frictionless)SuccessSuccess
Mastercard5436031030606378Any future date000Anytrue(frictionless)FailureFailure
American Express345678901234564Any future date1051AnyfalseN/ASuccessSuccess
American Express345678901234564Any future date0000AnyfalseN/AFailureFailure
American Express345678901234564Any future date1051Anytrue(frictionless)SuccessSuccess
American Express345678901234564Any future date0000Anytrue(frictionless)FailureFailure
Discover601111111111111703/30100AnyN/AN/AN/ASuccess
Diners3012345678901903/30257AnyN/AN/AN/ASuccess

Status workflows

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

SaleWhen isAuthOnly is false, successful sale transactions will have the following statuses:
  • pending*
  • settled
Auth onlyWhen isAuthOnly is true, successful sale transactions will have the following status:
  • authOnly
CaptureSuccessful capture transactions will have the following statuses:
  • pending*
  • settled
VoidSuccessful void transactions will have the following status:
  • voided
RefundSuccessful refund transactions will have the following statuses:
  • pending*
  • 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.


Did this page help you?