Skip to content
Docs简体中文Website ↗
Docs/API conventions
INTEGRATION GUIDE

API conventions

Request format, identifiers, amounts and response interpretation.

Request format#

HTTP
Content-Type: application/x-www-form-urlencoded

All source-documented endpoints use POST forms. An example JSON block does not imply a JSON request body.

Orders and idempotency#

Keep merchant order identifiers unique. When the result is uncertain, query the original order instead of creating a payout with a new identifier.

Amount representation#

Use the currency unit required by the assigned channel. Do not multiply or divide by 100 without explicit instructions. Keep decimal places and the exact string unchanged between signing and submission.

Transport success vs business success#

Read the status reference
© 2026 88Pay API field names and response values remain unchanged across languages.
Searches this documentation only · No data is sent to the server