The API Report CardAPI Index
THE API REPORT CARD / Financial Services / Payment Depot
Payment Depot

Payment Depot API

paymentdepot.com

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.

Last verified: July 2026Financial Services
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceFAILNo Payment Depot API exists; integration means targeting the merchant's underlying gateway, not the brand.
AccessFAILNothing to sign up for at the Payment Depot layer; Stax Connect, the parent ISV surface, requires partner contracting.
CoveragePOORSurface depends on the merchant's gateway: Authorize.Net, NMI, USAePay, Stax, or Clover, each with different APIs.
AuthFAILNo credentials exist at the Payment Depot layer; keys and webhooks belong to each merchant's gateway account.
Docs & DXFAILNo developer portal, reference, or SDK under paymentdepot.com; documentation lives at each gateway's own site.
StabilityMIXEDMigration from legacy gateway rails onto Stax and Worldpay has produced credential and reconciliation churn for ISVs.
MORE FROM THE REPORT CARD
HelcimASquareAStripeAToastF
Supergood: Payment Depot isn't going to ship an API, so we did: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Payment Depot scores F on the 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.

Tried to integrate with Payment Depot?
SOURCES
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 paymentdepot.com ↗
Migration from Payment Depot's legacy gateway path onto Stax/Worldpay rails has produced reconciliation/credential issues for ISVs supporting long-tenured merchants merchantmaverick.com ↗
Clover-attached merchants are forced onto Fiserv rails and must integrate via Clover's developer platform, different SDKs, different webhook model, different merchant onboarding flow vs. the gateway-attached cohort docs.clover.com ↗
Authorize.Net's legacy AIM/CIM XML APIs are still the dominant integration path for many Payment Depot merchants; the newer JSON REST surface is partial and inconsistent developer.authorize.net ↗
Webhooks are gateway-scoped (Authorize.Net webhooks, NMI postback URLs, Stax webhooks), there is no unified 'Payment Depot' event stream that an ISV can subscribe to across the merchant base developer.authorize.net ↗
Stax Connect (the embedded-payments / ISV API surface from the parent) requires partner-program contracting rather than self-serve sign-up staxpayments.com ↗
Sandbox parity issues are inherited from each gateway, Authorize.Net sandbox does not exercise full risk/fraud signals; NMI/USAePay test modes differ from production timing developer.authorize.net ↗
No published rate limits or uptime SLA at the Payment Depot brand layer; SLAs are inherited from the underlying gateway and acquirer paymentdepot.com ↗
ISVs report difficulty getting authoritative answers from Payment Depot support on which gateway/rails a specific merchant is on, slowing initial integration work merchantmaverick.com ↗
The eventual consolidation onto Worldpay rails post-2024 acquisition introduces ongoing migration risk for any integration built against the current Stax/gateway surface staxpayments.com ↗
Post-Stax acquisition: effective rates climbed (one Trustpilot reviewer reports going from ~2.6% to ~3.5% blended) and the original 'no percentage markup' pitch no longer applies to new pricing trustpilot.com ↗
Unexpected/undisclosed fee additions on monthly statements, the opposite of the 'transparent membership' positioning the brand was built on bbb.org ↗
Customer support quality declined materially after the Stax acquisition: long hold times, hard to escalate, named account reps disappeared merchantmaverick.com ↗
Charges continued to be drawn from merchant bank accounts after merchants believed the account was closed; difficulty terminating the relationship bbb.org ↗
Limited pricing transparency on the website, published pricing no longer matches the historical $79/$99/$199 tiers and new pricing requires sales-quote merchantmaverick.com ↗
BBB shows 27 complaints closed in the last three years and the company is currently not BBB-accredited (despite an A letter grade) bbb.org ↗
Hardware/POS path forces specific platform choices: Clover deployments lock the merchant onto Fiserv rails; non-Clover defaults to TSYS merchantmaverick.com ↗
US-only, no international merchants accepted, no multi-currency settlement merchantmaverick.com ↗
No high-risk merchant categories accepted (CBD, firearms, adult, certain telemedicine, gambling) merchantmaverick.com ↗
Trustpilot average is ~3.4–4.6 depending on cohort, with a clear cliff in sentiment dated to the Stax acquisition trustpilot.com ↗
© Supergood Systems, Inc.