OrderCard is a portable card vault. Your checkout collects the card with hosted fields served from OrderCard’s own domain, so card numbers never touch your servers. You get back a token, and your server charges that token through any of your gateways: Fortis, NMI, Authorize.net, Converge (Elavon) or Deluxe. Switch or add processors without asking customers for their cards again.
Start here
- Getting started takes you from a new account to a first sandbox charge.
- Hosted fields is the checkout side: one script, a card form you can restyle, a token.
- Payments is the server side: purchase, authorize and capture, void, refund, verify.
- API reference lists every endpoint.
What OrderCard does for you
- Keeps card data out of your systems. Card numbers are encrypted in a vault that only OrderCard’s vault servers can read. Every time a number is read to charge it, the read is logged.
- Speaks every gateway the same way. One request shape, one set of decline codes, normalized AVS and CVV results, whichever processor you charge through.
- Surcharges correctly. Credit cards only, at most 3%, never in states that ban it, and in proportion on refunds. Fortis and Converge decide their own surcharges and OrderCard follows them.
- Keeps sandbox and live apart. Separate keys, cards, gateways and transactions, with test cards for every outcome and a built-in test gateway.
- Tells you what happened. Signed webhooks for every card and transaction event, and a dashboard showing every transaction and the exact (sanitized) gateway call behind it.