Developers
Integrate in a day, not a sprint.
A predictable REST API, hosted checkout for zero PCI scope, and plugins for the carts your team already runs. Sandbox on approval so you can build before you sign.
Create a payment
One request. Same shape across every language.
Mock endpoint, illustrative keys. Real keys are issued on approval.
curl -X POST https://api.rizkpay.com/v1/payments \
-H "Authorization: Bearer sk_test_xxxxxxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"amount": 4900,
"currency": "AUD",
"customer": "cus_9F2A",
"payment_method": "pm_card_visa",
"description": "Order #10245",
"capture": true
}'{
"id": "pay_01HZK7Q3D8N",
"object": "payment",
"amount": 4900,
"currency": "AUD",
"status": "succeeded",
"customer": "cus_9F2A",
"payment_method": "pm_card_visa",
"captured": true,
"created": 1721952000,
"livemode": false
}API surface
The endpoints you will actually use.
A small, boring API is a good API. Same request shape across payments, refunds, customers, and payouts.
- POST/v1/paymentsCreate a card payment
- GET/v1/payments/:idRetrieve a payment
- POST/v1/refundsRefund a payment in full or part
- POST/v1/customersCreate a saved customer with tokenised card
- GET/v1/payoutsList settlement payouts
Webhook events
Signed HMAC deliveries with automatic retries.
- payment.succeeded
- payment.failed
- payment.refunded
- chargeback.opened
- chargeback.won
- chargeback.lost
- payout.paid
- customer.updated
Integration options
Pick the depth that fits your team.
REST API
Full control over payments, customers, refunds, and payouts. Idempotency keys on every write. Typical build 2 to 5 days.
Hosted checkout
Redirect or embed. Zero PCI scope, 3DS2 handled for you. Live under a day for most merchants.
WooCommerce plugin
One-click install, configure keys, done. Supports refunds, subscriptions, and 3DS2 out of the box.
Other carts
OpenCart, PrestaShop, Magento, and Shopware modules maintained by the Rizk Pay team.
Webhooks
Signed event deliveries for payments, chargebacks, and payouts. Automatic retries with exponential backoff.
Before you switch keys
Sandbox first. Production second.
Every merchant runs the same checklist before we flip production keys. It catches the small stuff before real money moves.
Sandbox credentials
Test keys, dashboard access, and a virtual settlement ledger issued the day you are approved.
Test cards
Approval, decline, 3DS2 challenge, insufficient funds, and chargeback scenarios all callable with fixed card numbers.
Go-live checklist
Webhook signature verified, refund flow tested, descriptor confirmed, error handling reviewed. One call to switch keys.
Full reference documentation lands with your sandbox credentials. Reach out via contact for early access.
Get API keys with your approval.
Sandbox keys land in your inbox the day you are approved. Production keys go live after go-live checklist sign-off.