This guide shows the minimum integration path for a merchant or developer: create a payment intent, send the customer to a payment link, and receive a signed webhook when payment completes.Documentation Index
Fetch the complete documentation index at: https://docs.ababilpay.xyz/llms.txt
Use this file to discover all available pages before exploring further.
The production implementation is expected to use API keys, HMAC-signed webhooks, Circle testnet or mainnet configuration, and Supabase-backed merchant records.
Integration flow
Create a merchant account
Sign in with Google OAuth. AbabilPay creates the Supabase user record, provisions a Circle developer-controlled wallet, and stores the merchant profile.
Create a payment intent
Call
POST /v1/payments/intent with the USDC amount, customer reference, and optional metadata.Redirect the customer
Send the customer to the returned
payment_url. The customer can pay with supported tokens, while AbabilPay handles auto-conversion to USDC.Example payment intent response
Webhook payload
Webhook verification
Each webhook request should include a timestamp and HMAC signature header. Recompute the signature over the raw body and reject requests with invalid signatures or stale timestamps.Common next steps
Invoices
Create invoices, send branded payment links, and track payment state.
Shopify and WooCommerce
Use hosted commerce plugins instead of a direct API integration.
Transfers
Send USDC to a wallet address or email recipient.
Webhooks
Register an endpoint for payment and operational events.
