Alipay H5 payment: 稳付pay integration, callbacks and USDT settlement

An Alipay H5 checkout starts when a customer chooses Alipay on a mobile website. The website then verifies payment and credits a balance or activates a subscription. This guide explains official WAP payment alongside the actual 稳付pay merchant workflow, channel advantages and settlement arrangements.

Continue by topic

1. Where Alipay H5 payment fits

Mobile website top-ups, subscriptions and purchases can be assessed for Alipay WAP payment. The official method is alipay.trade.wap.pay. Desktop website and native APP payments are separate products; seeing a page on a phone does not justify mixing their interfaces.

Whether checkout opens the Alipay client, uses an intermediate page or offers another supported route depends on the device, client installation, browser restrictions and product configuration. Do not promise automatic launch in every embedded browser or describe launch as bypassing the customer’s payment confirmation.

For 稳付pay, first confirm that the assigned Alipay channel supports your web environment. Integrate its order and notification protocol and obtain supported checkout instructions from technical support. Do not add official Alipay parameters to an aggregation order yourself.

2. Integrate with 稳付pay: from channel setup to launch

Step 1: contact 稳付pay at @tonyyyds with your domain, business type, browser or app environment, top-up or subscription workflow, expected order volume and USDT settlement needs. Technical support confirms H5 availability, channels, fees, settlement rules and testing. A channel name alone does not establish activation.

Step 2: obtain the actual gateway, merchant mchId, authorized wayCode and server-side secret. Prepare a public notifyUrl and a local order table. Keep secrets on the backend. Example aggregation codes are 90001 for WeChat and 80001 for Alipay; they require merchant authorization, and a specific channel code may be assigned instead.

Step 3: persist a unique outTradeNo and a trusted price, then send JSON from the backend to POST /api/pay/collect/create. amount uses integer CNY fen: 1000 means CNY 10. reqTime must be the current Unix time in milliseconds as an integer; generate sign using the documented MD5 rules. The example contains placeholders for this payment method: replace them and sign on the server.

Illustrative collection fields: replace placeholders, use the current millisecond integer for reqTime and sign on the backend. Do not submit this example unchanged.
{
  "mchId": "YOUR_MERCHANT_ID",
  "wayCode": "80001",
  "outTradeNo": "YOUR_UNIQUE_ORDER_NO",
  "amount": 1000,
  "currencyCode": "CNY",
  "notifyUrl": "https://merchant.example.com/pay/notify",
  "subject": "WENFUPAY_H5_DEMO",
  "reqTime": "CURRENT_UNIX_MILLISECONDS",
  "sign": "GENERATE_MD5_ON_SERVER"
}

Step 4: retain the platform order reference and use a valid returned payUrl according to the agreed integration. Do not invent checkout URLs. code=0 means request acceptance, not payment, so it must not trigger a credit. Actual channel and browser testing determines whether checkout opens the client directly.

Step 5: receive 稳付pay’s normalized JSON notification. Verify its signature and match merchant, order, amount and currency before recording payment once. After durable acceptance, respond with HTTP 200 and plain-text OK. For a missing callback or an uncertain creation result, query the original order through GET /api/pay/collect/query from the backend. Confirm query amount units during onboarding.

Step 6: use the technical team’s testing arrangement to verify payment, cancellation, timeouts, repeated notifications and balance updates. Reconcile the first production orders before gradually increasing traffic. The links below provide onboarding and full documentation.

3. Why use 稳付pay: channel and service advantages

Payment choices: current channels include WeChat personal-code collection, native WeChat collection and native Alipay collection, with aggregation integration. Configure the methods appropriate to your business and reduce separate channel integrations. H5 availability still depends on the enabled channel. Current channel performance is stable, but results depend on orders, user environments and channel conditions; no fixed success percentage is promised.

Consistent orders and notifications: use the returned checkout entry and one creation, query and JSON notification workflow to connect website top-ups, subscriptions, card delivery or TG bot orders to your own system. The platform reports payment status; the merchant updates balances and entitlements from verified results. Receiving a callback does not automatically fulfill every business operation.

T0 real-time USDT settlement: after customer payment is confirmed, USDT can be settled to the merchant under the agreed arrangement. Confirm eligible amounts, fees, conversion rules, network and address during onboarding. Processing and blockchain arrival remain subject to conditions and confirmations; this does not mean zero fees, zero confirmations or unconditional instant arrival.

Technical assistance: the team helps confirm merchant settings, channel selection, signatures, queries and notification issues. WeChat or Alipay collection settled in USDT is distinct from USDT monitoring of a merchant-owned address. In the latter, the customer pays the merchant wallet directly and 稳付pay monitors confirmation and sends a callback. Do not describe both as the same funds flow.

4. Separate official WAP from the 稳付pay gateway

A direct official integration configures application identity and signing material for the contracted product, then generates the WAP payment request on the server. The official Easy SDK uses alipay.trade.wap.pay and QUICK_WAP_WAY. Its totalAmount is in yuan: CNY 10 is 10.00. The browser receives the SDK-generated payment form or page output. Signing material must remain on the backend.

Official return_url handles the post-payment browser return, quit_url handles an interrupted checkout return, and notify_url receives asynchronous notifications. A browser return is not proof of payment. WeChat h5_url and redirect_url are not Alipay protocol fields, and APP payment is not a substitute for WAP.

The 稳付pay merchant protocol uses mchId, wayCode, outTradeNo and integer-fen amount, with the assigned gateway and documented MD5 signing. Use the returned payUrl. Official Alipay RSA2 and aggregate MD5 operate at different integration layers; do not exchange their parameters or secrets. Confirm actual response fields and enabled capabilities in testing.

5. Confirm payment before callbacks and balance updates

Order acceptance or a return to the website does not establish payment. After confirming the channel result, 稳付pay sends a normalized notification to merchant notifyUrl. Verify the signature, merchant, original order, platform reference, amount, currency and success state before processing. A screenshot, browser button or code=0 must not credit a user.

After durable acceptance, create a credit ledger record, subscription activation or fulfillment task with a unique order key. Queries and repeated notifications must use one handler, ensuring one balance credit. If payment succeeded but fulfillment failed, retain a recoverable task rather than asking for another payment.

A return-page status button should ask the backend to query the original order. Use the same approach for late callbacks, uncertain creation requests and pending results. Convert query amount units according to the confirmed interface instead of comparing them directly with creation amounts in fen. If confirmation is unavailable, show pending review rather than a definite failure that encourages repeated payment.

6. Acceptance checks before launching Alipay H5

Test the actual iOS and Android browsers your customers use. Check checkout access, cancellation and exit returns, recovery of the original order and independence from unsaved browser state. For restricted embedded browsers, follow the technical guidance for opening the page differently; do not spoof origins or force bypasses.

Test duplicate callbacks, queries before and after notifications, temporary database failures and fulfillment recovery. Reconcile orders, payments, user balances and merchant USDT settlement records. User crediting and merchant settlement are different states and must not overwrite each other.

Keep redacted order references, times, errors and request identifiers in testing records. Do not expose merchant secrets or complete payment links. 稳付pay provides integration assistance; final channels, fees and settlement conditions follow the confirmed arrangement.

Frequently asked questions

How do I enable Alipay H5, and are fees fixed?

Contact @tonyyyds with the website, business, opening environment, expected orders and settlement needs. The team confirms channel availability, parameters, fees and testing before integration. This guide does not invent a universal rate or activate H5 for all merchants.

Does USDT settlement mean customers pay my wallet directly in USDT?

These are different flows. Here, the customer pays with Alipay and the platform settles USDT under the agreed arrangement. Merchant-owned-address monitoring instead involves a direct USDT transfer from the customer to the merchant wallet, followed by monitoring and notification. Confirm the rules separately.

References