Payment collection for registered websites

Collect the payment. Confirm it on your server.

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.

  • Verified digest Checkout opens only when the signature matches.
  • Server postback Your site receives the payment result directly.
  • Same transaction One id keeps one order, amount, and description.
  • Sandbox or live Each website chooses its own mode.

How it works

How a payment moves

Four steps from your checkout to a result your server can record.

  1. 01

    Register the website

    Reference site, postback URL, fees, and sandbox or live mode belong to that website.

  2. 02

    Sign the amount

    Your server creates the transaction id and the digest. The secret never goes in the browser.

  3. 03

    The buyer pays

    They use the Webpay page, or they pick a channel on your site and Webpay opens that method.

  4. 04

    Your server is told

    Webpay posts the outcome to your postback URL. The buyer then sees the result here.

Channels

Ways your customers already pay

A channel is offered only when it is enabled for that website and for the platform.

GCash

Wallet

Credit card

Card

PayPal

Online

GrabPay

Wallet

ShopeePay

Wallet

7-Eleven

Over the counter

BancNet

Online banking

Alipay

Wallet

Also available: WeChat, UnionPay, Bitcoin, wallet, cash on delivery, bank transfer, and corporate payment.

Integration

Start on Webpay, or on your own page

Both paths use the same signed request. Only the place where the buyer picks a method changes.

Hosted checkout

Leave the channel empty. Webpay shows the methods turned on for that website, then continues to the one the buyer selects.

Methods on your website

Load the enabled channels, show them beside your order, and post the code the buyer chose. Webpay opens that method.

Security

The browser is not the source of truth

A return page can be closed, refreshed, or edited. The postback is the record.

  • Digest first. Checkout opens only when the signature matches the amount, currency, and reference.
  • One order per transaction. Sending the same id again reopens that order. The amount and description stay as they were.
  • A completed payment stays completed. That order is not offered for payment a second time.
  • Live results use HTTPS. Sandbox and live are separate, and each website keeps its own postback address.

Try a payment

Run a sample before you go live

The simulator posts a request through this Webpay installation, on the hosted page or with a channel chosen up front.