Introduction

Gateway Connect is an API that lets a third-party server receive and process payment requests. A Gateway Connect integration acts as a layer between the provider’s API and the Reactivepay API.

From the merchant’s perspective, the operation-handling flow stays the same.

Merchant <--> Reactivepay <--> Integration <--> Provider's API

Motivation

Building an integration the standard way takes a lot of time and resources. Although the standard approach can potentially produce a higher-quality result, it’s often the case that an integration is needed on a very short timeline, or that it requires frequent changes.

When you build an integration on Gateway Connect, you get the following advantages:

• You own the integration’s code and tech stack — the integration can be written in any programming language or stack (Go, Python, Java, JavaScript, Ruby).
• Making changes becomes easy. No synchronization with the Reactivepay team is required — you can publish any settings or changes yourself.
• It’s a good fit for unusually complex integrations that require access to an SDK supported only by a specific stack.

Reference

The reference materials are collected in the Reference / Gateway Connect section:

• Core Contracts — the Request and Response structures, the logs format, and redirect_request
• Endpoints: Status and Payout — the POST /status and POST /payout specifications
• Callbacks and JWT — webhook handling, authentication, and the callback request format
• Error Handling — how the core interprets errors and rejections
• Settings and Statuses — the settings block, status codes, and sign_key