Changelog

Purchases and authorizations now take a three_d_secure object with the result of a 3-D Secure check from your own provider. OrderCard passes it to NMI, Authorize.net, Converge and Fortis in each gateway’s own fields, and records it on the transaction without its authentication value. The API, webhooks and the dashboard show what was sent.

Deluxe has no 3-D Secure fields for card payments, so its charges go through without the result and record forwarded: false. See 3-D Secure for the fields and rules.

OrderCard opens to its first teams. Collect cards with hosted fields, styled like your checkout and with an optional name, postal code or billing address, keep them in the vault, and charge them through Fortis, NMI, Authorize.net, Converge or Deluxe with one API. Purchases, authorizations, captures, voids, refunds and verifications all answer the same way on every gateway, with normalized decline codes and AVS and CVV results.

Also included: surcharging within the card network rules, a sandbox with test cards for every outcome and a built-in test gateway, signed webhooks with retries, and a dashboard with roles, API keys and an activity log.