Skip to main content
Reach Gateway
Support avatar
Written by Support
Updated over a week ago

Created: July 26, 2024

Updated: September 4, 2024

To configure Reach Gateway into your sticky.io CRM, you will go to Payments>Gateways, under ACTIONS select Add New Provider Profile. Select the type = Payment/Gateway and select Reach from the drop down. Fill out the gateway parameters which are outlined below and click “Save”.

REACH Fingerprint Requirement

Please Note: The Reach Gateway requires custom scripts be added to your check out page.

Fingerprint - To combat fraud, Reach requires a script to be run on the buyer's machine to gather machine information and generate a fingerprint ID, which is then sent in the checkout request to Reach.

Reach provides a device data collector (DDC) script that collects customer machine information to help validate the legitimacy of the request. This DDC can be retrieved from the /fingerprint API. Details for the DDC fingerprint flow can be found in Reach’s Fingerprint documentation.

How to Send FingerPrint and Accept Liability info to sticky

Fingerprint = Need to send device_finger_print in new_order API call "device_finger_print": "4f9d91d6-6930-4c31-8f23-318d0510d096",

Please note that “4f9d91d6-6930-4c31-8f23-318d0510d096” is just for reference.

AcceptLiabilty = If you are using Reach's fraud services, you need to send `accept_liability=no` in the API call. If you are not using Reach’s fraud services and are providing your own fraud, you need to send `accept_liability=yes` or omit the field entirely.

Additional Information

  • Please note that the REACH Gateway will not work with the sticky Place Order Page. The Place order page will not generate the fingerprint ID.

  • All REACH orders remain in pending status until the Webhook update is received, at which point the order status will change to "Approved" or "Declined.

  • Presently REACH does not work with bundled products within sticky.

REFUND and VOID FACTS

  • Please note that only Authorized amounts can be VOIDED.

  • Please Note: Partial Refunds: Once First partial refund is settled at REACH side then another partial refunds can be initiated

For more information on this Gateway click here. These parameters are briefly described here for your reference:

Alias: name that you will assign to the gateway. This is for internal purposes only; it helps you identify a specific gateway account among several of them in your CRM.

Merchant ID: Reach will provide you with the Merchant Account ID.

Secret Key: This will be provided to you by Reach.

Currency: Reach currently supports dozens of currencies. Click the drop down when setting up the profile for the full list.

Enable Delayed Capture: allows you to authorize the payment on day 1 and capture it in “x” number of days. Applies to initials and recurring orders, it creates the orders in a “Pending” status and they won’t be sent to fulfillment until the charge is captured and the status is updated to “Approved”.
Delayed Capture Days: number of days in which you wish to capture the charge, this is to be used with Enable Delayed Capture.

Capture On Shipment?: Set to Yes if you want to capture an authorization once an order is marked a shipped in the CRM. Also, an order will remain as pending in the system until the authorization is captured upon shipment. Set to No if you want the standard authorization and capture process for your orders. Optional.

Sticky.io 3D Verify: Set to YES if you are using our 3D Verify service.

Test Mode: Set to YES if you would like to use this gateway in test mode.

ADDITIONALLY

There are 2 Required Fields on the Merchant Account Details tab.

· *Descriptor - This will be the MID Descriptor

· *Customer Service Number - The customer service number assigned to the MID

There is 1 Required Field on the Limits and Fees tab

· *Global Monthly Cap - This will be the sales amount allowed monthly on this MID

To maximize the efficiency of sticky.io Reporting Analytics we suggest you take a moment and fill out the rest of the fields. These will all be used in sticky.io’s profitability reports.

For field definitions on all of the fields on the Merchant Account Details Tab and the Limits & Fees Tab - click here- overview of gateway providers

Once your gateway profile has been created, then you will go through your campaigns and assign the gateway to the corresponding campaign(s).

Updated: July 26, 2024

Required 3DS2 Parameters

  • "cavv": "LXE+enY77l/G2UkP4q8Gzj+R3N4=",

  • "eci": "06",

  • "xid": "YmUyMnFoMmJpbHM1aGJzNjd2MGc=",

  • "ds_trans_id":"d65e93c3-35ab-41ba-b307-767bfc19eae3",

  • "acs_trans_id":"ca5f9649-b865-47ce-be6f-54422a0fce47",

  • "3d_version":"2"

Please note the values above are only for reference.

Reach Parameter New Order API

  • MessageVersion(Required) → 3d_version

  • TransStatus (Required) → True if ds_trans_id provided otherwise false

  • DsTransId (Required) → ds_trans_id

  • Eci (Required) → eci

  • AuthenticationValue (Required) → cavv

  • AcsTransId (Required) → acs_trans_id

Did this answer your question?