Developer documentation

Developer integration guide: connect 稳付pay to your product

Your website, digital delivery platform or app creates business orders and delivers products; 稳付pay connects payment channels and notifies you of payment results. This guide explains configuration, API calls and when you may mark an order as paid, in the order you will actually integrate them.

Contents

First confirm the service you want to integrate

These documents cover collection order creation, order queries and successful payment notifications for enabled payment channels. Payouts are not currently available. During onboarding, 稳付pay technical staff will confirm available channels, production gateways, settlement arrangements and merchant permissions with you.

Settlement after channel collection and on-chain monitoring of payments made directly to the merchant's own USDT wallet are different business processes. These collection APIs do not represent the direct on-chain USDT collection APIs.

URLs, order numbers and credentials in this article are examples. Complete technical onboarding and obtain your own configuration first; do not use demonstration parameters directly in production.

Step 1: obtain merchant configuration

Configuration itemWhere it is usedWhat to confirm
API_BASE_URLMerchant backendThe actual assigned gateway; this article uses https://gateway.example.com as an example.
MERCHANT_IDMerchant backendYour merchant number; the request field is named mchId。
MD5_SECRETEnvironment variables or secret managementThe API key used for order creation and queries.
CALLBACK_SECRETBackend secret managementA separately configured callback key; falls back to the API key if not configured.
wayCodePayment method mappingActual channel or aggregate codes enabled for this merchant.
notifyUrlPublic HTTPS backend endpointFor example, https://merchant.example.com/pay/notify。

Keep keys only on the backend. The frontend should receive only business orders and payment links permitted for display. Store test and production configurations separately, and redact keys and the key portion of signature input strings in logs.

Step 2: connect the complete payment workflow

  1. Create a business orderThe server determines the product, amount, currency and unique merchant order number, then saves a pending payment record.
  2. Sign and create the order on the serverGenerate a current millisecond timestamp, calculate the signature and call the collection creation endpoint.
  3. Display a valid payment linkCheck the actual returned payUrl before guiding payment; if there is no link, query the order or handle the exception.
  4. Verify the successful notificationThe backend verifies the signature and checks the merchant, order, currency and amount; it does not infer receipt of funds from a browser redirect.
  5. Update and fulfill idempotentlyPersist the payment state and use a unique fulfillment record to prevent duplicate code delivery, credits or shipments.
  6. Query and reconcileActively query orders affected by timeouts, missing notifications or a prolonged pending state, and keep processing records.
Successful order creation is not successful payment; fulfillment must be triggered by a trusted server-side payment result.

Step 3: prepare four integration points in your product

System componentIntegration responsibilityRecords to retain
Order creation serviceValidate the business order, sign the request and call the creation endpoint.Merchant order number, amount in fen, currency and platform order number.
Payment display pageDisplay the actual payment link and local state.The associated order and customer access permissions.
Asynchronous notification endpointVerify the signature, check the order and persist the successful result idempotently.Notification summary, validation result and receipt timestamp.
Order query taskResolve unknown results and enter the same fulfillment workflow.Query results, attempt counts and the last verification timestamp.

When using an existing digital delivery platform, integrate this logic into its payment plugin or server-side extension. Confirm that the platform stores an independent merchant order number, verifies signatures using original parameter values and supports idempotent fulfillment. Adding a redirect link alone does not complete the integration.

Integration acceptance checklist before launch

  • Complete the agreed test orders, submit order amounts in fen and associate the correct platform order and payment entry.
  • Valid signatures pass; missing fields, modified amounts and invalid signatures are identified and recorded.
  • The server can still update order states through notifications or queries after the customer closes the browser.
  • Duplicate notifications and simultaneous successful notifications and queries all result in only one fulfillment.
  • After an order request times out, query the original order first instead of blindly creating another under a new order number. Keep unknown results pending verification.
  • Fulfillment failures after successful payment can be retried safely, with records for both payment and product delivery.
  • The notification endpoint is publicly accessible, and keys never appear in page source, public attachments or logs.

Technical staff confirm test limits, channel permissions and exception handling with you. When requesting help, provide redacted order numbers, request times and error summaries; do not show keys in screenshots.

Continue the API integration

Read in order: collection order creation and queries、request signing rules and callback verification and idempotent fulfillment. Technical staff provide integration support for your development framework, digital delivery system and enabled channels.

This article is based on the 稳付pay integration specification. Examples explain where to make calls and how parameters are structured; use the configuration assigned to you for formal integration testing.

Confirm integration for your business scenario

Describe your products, order volume, payment methods and settlement needs to confirm the APIs, movement of funds and exception handling item by item.

Contact 稳付pay ↗