Payments Overview

APICenter exposes provider-neutral payment resources. Your service sends domain references and amounts; provider-specific identifiers, secret keys, and raw provider payloads remain inside the platform boundary.

For TypeScript backends, use the server-side APICenter SDK. It handles service-token exchange and exposes typed methods for checkouts, intents, customers, refunds, subscriptions, and payment links. The REST examples in this section remain available for other runtimes.

Checkout

Create a checkout with a stable referenceId, a PHP amount in minor units, and registered return URLs.

POST /api/v1/payments/checkouts

Use the returned checkoutUrl for the customer redirect. A return to your application is not proof of payment; wait for payment.checkout.paid.

Intents, customers, refunds, and subscriptions

Use payment intents when your application owns confirmation state, customer records for billing identities, refunds for completed payments, and subscriptions/invoices for recurring billing. Reusable payment-method setup is not currently exposed by the public API.

All provider-impacting creates, confirmations, cancellations, and refunds use Idempotency-Key. Resources expose normalized statuses and aggregate versions rather than raw PayMongo fields.

Capabilities

Call GET /api/v1/payments/capabilities during onboarding to discover enabled operations and supported payment methods for the selected environment. Treat capabilities as runtime configuration, not as a license to bypass authorization or business rules.

Use payment links for a hosted checkout URL or create a QR Ph payment intent when you need to display a QR code in your application.