Payment Depot API
No standalone API. Payment Depot delegates developer integration to whichever gateway the merchant is provisioned on: Authorize.Net, NMI, USAePay, Stax, or Clover. There is no api.paymentdepot.com, no developer portal, and no unified webhook stream across the merchant base.
Frequently asked questions
Payment Depot scores F on Supergood's API Report Card. No standalone API. Payment Depot delegates developer integration to whichever gateway the merchant is provisioned on: Authorize.Net, NMI, USAePay, Stax, or Clover. There is no api.paymentdepot.com, no developer portal, and no unified webhook stream across the merchant base.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Payment Depot is a US merchant services provider founded in 2013 in Orange County, California by Danny Choi.
Vertical: Financial Services (merchant services / card acquiring resale). Card-present sales via Clover, Dejavoo, SwipeSimple, and other countertop/mobile terminals. Card-not-present sales via virtual terminal (Authorize.Net / NMI / USAePay-backed).
Low-to-medium in the SMB processing tier; negligible as a developer surface.
Data flowing through a Payment Depot merchant account (via the underlying gateway / processor / acquirer): Payment instruments: Card PANs (tokenized through the gateway vault, Authorize.Net CIM, NMI Customer Vault, USAePay Customer DB, or Stax tokens), expiry, CVV (transient), bank account/routing numbers (ACH), wallet tokens (Apple Pay, Google Pay via the gateway)..
Founded 2013; ~13 years old as of 2026. Payment Depot itself is not a technology platform, it is a merchant-services brand that sits on top of horizontal infrastructure (Authorize.Net, NMI, USAePay gateways; TSYS and Fiserv processors; Stax/Worldpay rails).
No branded Payment Depot developer portal, developers must figure out which gateway the merchant is on (Authorize.Net vs NMI vs USAePay vs Stax) before they can write any integration code. Migration from Payment Depot's legacy gateway path onto Stax/Worldpay rails has produced reconciliation/credential issues for ISVs supporting long-tenured merchants. Full sourced list under Sources below.
Common alternatives include Stax (sibling brand, same parent), Helcim, Square, Stripe, PayPal / Braintree, Clover (Fiserv). Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Not that we could find. As of August 2026 there is no official Payment Depot MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Payment Depot doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.