Developer platform

Build ForgePay payments into your AI product

Use ForgePay test mode to create API keys, hosted checkout sessions, recurring subscriptions and signed webhooks for ForgeCredit payments.

Test mode first. No live payout secrets required.

Developer guides

Start with API keys, then create hosted checkout sessions or recurring subscription mandates.

Quickstart

Create a test API key, call the checkout API and redirect your customer to ForgePay hosted checkout.

API keys

ForgePay API keys authenticate server-to-server merchant API requests.

One-time payments

Create hosted checkout sessions for one-time ForgeCredit payments.

Subscriptions

Create recurring payment mandates that users explicitly approve in ForgePay hosted checkout.

Webhooks

Use signed webhook events to update your application after ForgePay payment state changes.

Errors

ForgePay API errors use a consistent JSON shape with a request id for support and logging.

Testing

Use ForgePay test mode to build integrations without live payment provider secrets.

ForgePay is not a bank. ForgeCredit is an internal settlement unit for services available in the ForgePay ecosystem.

Security recommendations

ForgePay hosted checkout keeps the user's transaction PIN inside ForgePay. Merchants should still protect their own API keys, webhook secrets and idempotency keys.

Security recommendations

ForgePay hosted checkout keeps the user's transaction PIN inside ForgePay. Merchants should still protect their own API keys, webhook secrets and idempotency keys.

Store API keys only in server-side environment variables.
Use HTTPS URLs for success, cancel and webhook endpoints.
Send an Idempotency-Key on every POST request.
Verify webhook HMAC signatures before trusting event payloads.
Never ask users for their ForgePay transaction PIN outside ForgePay.