# 

## How processor routing works

When you create a transaction through `POST /v1/transactions`, Reefpay determines the correct processor based on the payment method type. Card transactions route to TSYS and bank account transactions route to Vericheck. The routing is automatic — you do not need to specify a processor in the request.

![image](https://files.modern-mermaid.live/images/1776269909184-mermaid-diagram-1776269909366.png)

## TSYS

[TSYS](https://www.tsys.com/) (now [FIS Total Issuing Solutions](https://www.fisglobal.com/products/total-issuing)) is a global payment processor that handles credit and debit card transactions.

### Supported transaction types

| Transaction type | Description |
|  --- | --- |
| `sale` | Authorize and capture in one step |
| `auth` | Authorize only; capture separately via `POST /v1/transactions/{id}/capture` |
| `capture` | Capture (complete) a prior authorization |
| `cancel` | Cancel before settlement via `POST /v1/transactions/{id}/cancel` |
| `refund` | Return funds for a settled transaction |


### Supported card brands

| Brand | Supported |
|  --- | --- |
| Visa | Yes |
| Mastercard | Yes |
| American Express | Yes |
| Discover | Yes |


### Processor response fields

TSYS responses are returned in the `processor_response` object within the transaction response. Key fields include:

| Field | Description |
|  --- | --- |
| `response_code` | Processor result code (e.g., `00` for approved) |
| `authorization_code` | Six-digit authorization code from the issuing bank |
| `response_message` | Human-readable description of the result |


### Connecting to TSYS

Merchants connect to TSYS by creating an integration through `POST /v1/integrations` with the appropriate Merchant Identifier (MID) and Terminal Identifier (TID) credentials. For step-by-step instructions, see [Add an integration](/docs/how-tos/integrations/add-integration).

## Vericheck

[Vericheck](https://www.vericheck.com/) is an [ACH Network](https://en.wikipedia.org/wiki/ACH_Network) payment processor that handles bank account debits and credits through an automated clearing house (ACH) for electronic funds transfers.

### Supported transaction types in Vericheck

| Transaction type | Description | Fund flow |
|  --- | --- | --- |
| `payment` | Debit (pull funds) | Person → Merchant |
| `payout` | Credit (push funds) | Merchant → Person |
| `cancel` | Cancel before settlement via `POST /v1/transactions/{id}/cancel` |  |


### ACH processing timeline in Vericheck

ACH transactions do not settle in real time. Typical timelines:

| Event | Timeline |
|  --- | --- |
| Transaction submitted | Immediate API response |
| Batch sent to ACH network | Next business day |
| Funds settled | 2–3 business days |
| Returns (NSF, closed account) | Up to 60 days |


### How to connect to Vericheck

Merchants connect to Vericheck by creating an integration through `POST /v1/integrations`. For step-by-step instructions, see [Add an integration](/docs/how-tos/integrations/add-integration).

## Processor account management

Manage processor connections (integrations) through the following endpoints.

| Endpoint | Method | Description |
|  --- | --- | --- |
| `/v1/integrations` | GET | List all processor integrations |
| `/v1/integrations` | POST | Create a new processor integration |
| `/v1/integrations/{id}` | GET | Retrieve integration details |
| `/v1/integrations/{id}` | PUT | Update integration credentials |
| `/v1/integrations/{id}` | DELETE | Remove a processor integration |


## Further reading

* [Supported payment methods](/docs/get-started/supported-payment-methods)
* [About features overview](/docs/get-started/features-overview)
* [About batch settlement](/docs/concepts/transactions/batch-settlement)