Forta
Quick Start
- Sign up at forta.com and obtain API credentials
- Create a terminal in the Admin Console with the parameters below
- Start processing — the adapter is pre-built and ready to use
Overview
Forta payment integration
| Provider ID | forta |
| Category | Card Processors |
| Website | forta.com |
Configuration
Required Parameters
| Parameter | Description |
|---|---|
token | token for authentication API-requests |
channel | channel for access to API (for example: default) |
Example Configuration
{
"env": "prod",
"token": "your-static-token",
"channel": "default",
"redirection_remap": true
}
Payment Flow
Payments (one-phase):
-
invoice - payment invoice creation via POST
/invoice:- orderId (transaction ID), amount, payerHash
- callbackUrl, returnUrl
- Retrieval guid and paymentUrl
- Refund URL for redirect client
-
invoice_status - status check via GET
/invoice?id={guid}:- Parsing status from response.data
- Status mapping
Payouts (one-phase):
-
create_payout - payout creation:
- POST
/toCard/{tx_id}for card payouts - POST
/toSBP/{tx_id}for SBP payouts - amount, currency, card/phone, bank (for SBP)
- Refund status code (201, 418, 429, 503)
- POST
-
status - status check:
- GET
/toCard/{tx_id}or GET/toSBP/{tx_id} - Status codes: 202/404 → charging, 201 → check amount vs paidAmount, 503 → rate limit
- GET
Status Mapping
| Provider Status | 4pay Status | Description |
|---|---|---|
INIT | new | |
INPROGRESS | charging | |
PAID | charged | |
CANCELED | rejected |