AWDPay

AWDPay checkout for credit packs and plan purchases, confirmed twice before anything is credited.

AWDPay registers itself as a payment platform alongside your existing processors, with two independent switches: one for prepaid credit packs and one for plan purchases. Turn on either, both, or use it purely as a fallback processor. At checkout the buyer is handed to AWDPay's hosted payment page — which carries your own dashboard logo, so the handoff does not look like a detour to a stranger's site — and returns to your success or cancel route when they are done.

The part worth caring about is what happens after the redirect. Nothing is trusted from the browser: the transaction id is held server-side and re-checked against AWDPay's payment status endpoint before credits move. In parallel, AWDPay posts a signed callback to your webhook URL carrying the invoice id and a custom payload identifying user, plan and purchase type — so an order still completes correctly when the buyer closes the tab before returning. Authentication is a per-request token exchange rather than a static secret travelling with every call, and the finance tax rate is folded into the charged amount automatically. From there the order rejoins the platform's normal pipeline: credits applied, subscriber activated where relevant, referral bonus fired against your first-payment-only or every-payment policy, and receipts emailed to both buyer and admin.

Key features

• Two independent switches — offer AWDPay on prepaid credit packs, on plans, or on both.
• Branded hosted checkout — your dashboard logo is passed on every payment request, and card data never touches your server.
• Server-side verification — the returning transaction is re-checked against AWDPay's status endpoint before credits are released.
• Signed callback webhook — orders reconcile even when the buyer never comes back to your site.
• Token-based auth — the API key is exchanged for a short-lived bearer token per request.
• Sandbox and production — switch environments from the same settings screen and test end to end before going live.
• Tax-aware totals — the platform tax rate is applied to the amount sent for authorisation.
• Standard payment pipeline — credits, subscriber records, referral bonuses and receipt emails all behave exactly as they do on every other gateway.

Powered by

Powered by AWDPay. AWDPay owns the checkout page, the payment methods available to your buyers and the settlement. The extension supplies your API key, webhook secret and environment, then verifies and records every result on your side.

Ideal for

• Operators whose buyers already have an AWDPay relationship.
• Platforms that want a hosted checkout so card data stays out of scope.
• Anyone who needs a second processor running behind their primary one.
• Teams who insist on testing a full payment cycle in sandbox before launch.