Developer docs
Use a test key to run your first test payment in 30 minutes.
Choose an integration method
Direct API payments
Best if you already have your own payment page and the platform has enabled direct card for your account. Your server calls the API to create and confirm the payment.
Get startedHosted checkout
Best if you don't want to handle card data. Create a checkout session and send the payer to the platform's checkout page to pay and complete 3DS authentication.
Get startedQuick links
- QuickstartGet a test key and run your first test payment
- API referenceParameters, examples and error codes for all 16 endpoints
- Webhook events and signaturesEvent types, the signing protocol and test vectors
- Testing guideTest card scenarios and a 33-item self-test checklist
- Go-live checklistConfirm each item before you go live
Warning: Read before you integrate
- An HTTP 2xx response doesn't mean the charge succeeded. Rely on the payment's
statusor a webhook with a verified signature (HTTP status). - Never treat an unknown status as success. Handle any status, event or error code you don't recognize as "incomplete" (Compatibility).
- Amounts are integers in the smallest currency unit:
USD 10000means 100.00 andJPY 10000means 10,000 (Key rules). - When the outcome is unknown, don't retry with a new idempotency key. Retry with the original key or query the payment, because a new key can cause a duplicate charge (Idempotency).