---
title: "Gateways"
description: "Connect the payment gateway accounts you charge cards through."
image: "https://docs.ordercard.io/og.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.ordercard.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Gateways

A gateway in OrderCard is one of your own merchant accounts. You can connect several, in sandbox and in live, and charge any vaulted card through any of them.

| Gateway | Guide |
| --- | --- |
| Built-in test gateway | [Test gateway](/gateways/test) (sandbox only) |
| Fortis | [Fortis](/gateways/fortis) |
| NMI | [NMI](/gateways/nmi) |
| Authorize.net | [Authorize.net](/gateways/authorize-net) |
| Converge (Elavon) | [Converge](/gateways/converge) |
| Deluxe | [Deluxe](/gateways/deluxe) |

## Connecting one

In the dashboard, open **Gateways → Connect a gateway**, choose the type, name it and enter the credentials from your gateway account. Or use [the API](/api/gateways). Then choose **Test connection**: OrderCard checks the credentials with the gateway without moving money and shows the result next to the gateway.

The gateway's environment follows the dashboard's environment switch (or the API key you use). Connect your gateway's sandbox account in sandbox and its production account in live.

## Credentials

Credentials are encrypted in the vault as soon as you save them and only ever shown masked: secrets show their last four characters. To change one, enter the new value; fields you leave blank keep their current value. Changing a credential clears the last connection test, so test again.

## Default and turned-off gateways

The first gateway in an environment becomes its default; you can choose another. A gateway that is turned off refuses new charges, but captures, voids and refunds of its earlier transactions still work. Removing a gateway works the same way: its transactions stay and can still be refunded.

## What OrderCard records

Every request OrderCard sends to a gateway is recorded with the gateway's answer, after card numbers, security codes and credentials are removed. Team owners and admins see these calls on each transaction's page in the dashboard, which is the quickest way to see exactly why a gateway refused something.

## Status updates from the gateway

Each gateway has an **events URL** (shown when you edit it, and as `events_url` in the API). Gateways that can post transaction status updates can send them there; OrderCard stores them, sanitized, against the matching transaction.

Source: https://docs.ordercard.io/gateways/index.mdx