Transaction Monitoring
Follow each transaction from creation to final status. Filter by method, status and environment, and export the results.
API-first payment transaction infrastructure
One record for every QRIS and USDT transaction: the API request that creates it, the webhook that confirms it and the settlement that closes it.
Your users can pay with USDT, BTC, ETH, BNB, SOL, TRX or LTC. You always receive USDT.
How it works
Creates a transaction with a scoped API key and your own order reference.
Validates, de-duplicates and records it, then tracks its status with the connected provider.
Receives a signed webhook on every status change. Your team works from the same record in the dashboard.
Who it is for
Your developers
One API to create payments, signed webhooks to confirm them, and a sandbox to test everything first.
Your customers
They pay by QRIS or USDT on their phone in seconds and see the result straight away.
Your finance team
Every payment, fee and withdrawal in one dashboard, ready to reconcile and export.
API integration
Two endpoints cover the whole lifecycle: create and retrieve. Every response has the same format and an X-Request-Id you can find in your API logs.
// create a transaction (sandbox key)
POST /api/v1/transactions
Authorization: Bearer pw_test_•••••••••
Content-Type: application/json
{
"merchant_reference": "ORDER-1042",
"amount": 250000,
"payment_method": "QRIS"
}
// response · 201 · X-Request-Id: 9f1c…
{
"success": true,
"data": {
"reference": "PW20260921143022AB3F",
"status": "pending",
"environment": "sandbox"
}
}
Operations
Follow each transaction from creation to final status. Filter by method, status and environment, and export the results.
Status changes are delivered to your endpoint with an HMAC signature. Every attempt is logged with its real response code.
Each paid transaction shows its gross amount, the PAYWISE fee and the net amount. Withdraw any part of your net amount and follow each payout until it arrives.
Alerts for failure-rate spikes, webhook delivery problems, transactions pending too long and inactive merchants.
Our team
Developer experience
Everything needed to go from first key to production lives inside the dashboard.
Send real requests with a sandbox key without writing any code.
Method, endpoint, status, latency, and request ID for every call made with your keys.
Endpoint reference, error codes, and webhook payloads next to your keys.
Copy-ready examples in cURL, PHP, and Node.js.
Security
Every connection to PAYWISE (API, payment page and dashboard) is encrypted with TLS 1.2/1.3 and HSTS, so data cannot be read in transit.
Bank account numbers and holder names are stored encrypted with AES-256, in every database backup too.
API keys are stored as hashes, limited to one merchant and environment, and can be locked to your server IPs. The full key is shown only once, when it is created.
Each delivery is signed with HMAC-SHA256 together with its send time, so your endpoint can verify it came from PAYWISE and refuse a replayed webhook.
The dashboard is protected by two-step verification (2FA) and trusted devices. Every new sign-in is logged and notified.
Web application firewall, DDoS protection, request limits, and automatic blocking of IPs that repeatedly try unauthorised access.
Merchant owners, staff, sales partners, and administrators each see only what their role allows.
API requests, webhook attempts and admin actions are all logged. The platform is monitored around the clock and backed up every hour.
Free · No app store · Same account as the website · Android · iPhone · Windows · Mac
Create an account, generate a sandbox key, and send your first transaction from the playground in minutes.
Usually replies within a minute
