Developer platform

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.

Test mode

Test mode API keys start with `fp_test_`. They create test checkout sessions and subscription mandates that are safe for local integration work.

Use `http://localhost:3000` for local ForgePay development.
Use separate idempotency keys for separate test orders.
Test checkout confirmations do not debit live ForgeCredit balances or create live settlement.
Webhook delivery uses the same HMAC verification pattern in test and live mode.

Recommended local test

Create a checkout session, open the returned `checkout_url`, sign in as a demo user and confirm with the user's transaction PIN and displayed ForgeCode.

curlbash

curl -X POST http://localhost:3000/api/v1/checkout/sessions \
  -H "Authorization: Bearer fp_test_xxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order_1001" \
  -d '{
    "amount_fgc": "250.00",
    "currency": "FGC",
    "description": "AI writing package",
    "success_url": "https://merchant.example/success",
    "cancel_url": "https://merchant.example/cancel",
    "customer_reference": "customer_42",
    "metadata": {
      "order_id": "1001"
    }
  }'

Security checklist

Keep production credentials out of test fixtures and never paste real API keys into client-side code, issue trackers or logs.