Register the website
Reference site, postback URL, fees, and sandbox or live mode belong to that website.
Payment collection for registered websites
A website posts the order to Webpay. Webpay checks the signature, takes the payment, and sends the result to your server. The buyer does not carry that result back.
The secret key stays on your server. It is never placed in the page.
How it works
Four steps from your checkout to a result your server can record.
Reference site, postback URL, fees, and sandbox or live mode belong to that website.
Your server creates the transaction id and the digest. The secret never goes in the browser.
They use the Webpay page, or they pick a channel on your site and Webpay opens that method.
Webpay posts the outcome to your postback URL. The buyer then sees the result here.
Channels
A channel is offered only when it is enabled for that website and for the platform.
Wallet
Card
Online
Wallet
Wallet
Over the counter
Online banking
Wallet
Also available: WeChat, UnionPay, Bitcoin, wallet, cash on delivery, bank transfer, and corporate payment.
Integration
Both paths use the same signed request. Only the place where the buyer picks a method changes.
Leave the channel empty. Webpay shows the methods turned on for that website, then continues to the one the buyer selects.
Load the enabled channels, show them beside your order, and post the code the buyer chose. Webpay opens that method.
Security
A return page can be closed, refreshed, or edited. The postback is the record.
Try a payment
The simulator posts a request through this Webpay installation, on the hosted page or with a channel chosen up front.