Card payments
Intents prefixed pi_card_. Create → (authorize) → commit/capture → refund, or
cancel. Card data is client-side encrypted.
See the Card Payments reference.
Paygasus Pay
One API for payments that know about the network. Card and ACH under a single, unified interface.
API version 2026-06-26 · base https://api.paygasus.com
Build payments in minutes
Section titled “Build payments in minutes”Paygasus Pay exposes payment intents on two rails — cards and ACH — behind one consistent API. Create an intent, drive it through its lifecycle, and read a single, predictable object shape back.
QuickstartCreate and commit your first card payment with curl.
AuthenticationSecret keys, live vs. test mode, and how to send them.
Test modeDeterministic amounts to simulate declines and pending ACH.
ErrorsThe error envelope and what each status code means.
EncryptionEncrypting payment data at client level
The two rails
Section titled “The two rails”ACH payments
Intents prefixed pi_ach_. Create a draft → submit to the bank → settles
asynchronously (pending → processing → processed), or cancel/reverse. See
the ACH Payments reference.
Managing keys, viewing transactions, and inviting your team happens in the Paygasus dashboard. This site documents the API.