Start with your server
Create an intent with integer BDT amounts and a persisted idempotency key. Keep merchant secrets out of the browser.
Read the request example →Alzaf IT · Payment infrastructure
Connect, track
and manage
your payments.
Bring payment creation, checkout integration and status tracking into one merchant workspace. Start with a test integration and connect your application through the Alzaf Pay API.
Local sandbox implementation available. Live data reads are isolated; live payment processing requires activation and acceptance.
Your application → Alzaf Pay
Payment lifecycleCreate → VerifyServer-authoritative payment status
- 01Create a paymentYour server stores the order and operation key.
- 02Open hosted checkoutUse the returned restricted checkout URL.
- 03Verify, then fulfillRead canonical status and deduplicate signed events.
Illustrative flow · no transaction is executed here
Build locally. Keep environments separate.Sandbox execution verified for the local mock slice. Hosted sandbox and real-provider live processing remain separate acceptance gates.See current availability →
One API for your integration
Follow each payment from your application.
Use Alzaf Pay keys, payment IDs, normalized states and signed webhook events. Internal processing configuration stays with platform operations.
Follow the same payment
Use one canonical payment identifier through checkout, status checks and refund history. A browser return alone never proves success.
Understand payment states →Handle uncertainty safely
Reuse the original operation after a timeout. Durable receipt and fulfillment guards protect against duplicate notifications.
Build your receiver →A workspace for your business
Separate businesses.
Organized applications.
Merchant workspaces keep business access separate. Projects organize applications within a merchant, and roles determine who can read or manage each area.
Package-based features and limits are planned; commercial packages and pricing have not been finalized.
Merchant workspaceYour business
Application project AApplication project B
Sandbox and Live use separate keys and records. Nothing automatically promotes between environments.
Start with a test integration