Create Native Pre-order
Create a Web payment prepay order and return the prepay ID, QR content and Web payment component redirect URL.
Overview
This page documents thePOST /v1/pay/transactions/native endpoint. The full schema, parameters, and examples are rendered from the linked OpenAPI definition above.
Notes
- Authentication uses the standard GatePay signed headers.
- This page documents the standard merchant endpoint.
- For shared signing rules, see /api-reference/version/100/en/common/securityAndSignature.
Headers
Merchant client ID, obtained from GatePay platform
"4186d0c6-6a35-55a9-8dc6-5312769dbff8"
HMAC-SHA512 signature for request validation
"672d5650dcc9bb22ebf25fa16c28d03c0e159d742a9176d4340a5da326d75dc8a2ec24c97fa6fc5d1533dd6e968863747e1d86a45e562cbe899f9ed7e9ca7f77"
Millisecond timestamp; the difference from server time must not exceed 30 seconds.
"1672905655498"
Random nonce for replay attack prevention
"3525756760"
Body
Request body for creating a Web payment prepay order.
Merchant order number, up to 100 bytes.
Transaction source information.
Goods information.
Order currency, uppercase, such as USDT, BTC, etc.
Order amount, ranging from [0.0001, 5000000].
Fiat order currency in uppercase, such as EUR, GBP, USD, CNY, JPY, AUD, CAD, CHF.
Fiat order amount. Minimum 0.01 with maximum precision of 2 decimal places. When creating an order, you can use either crypto currency and amount, or fiat currency and amount. If fiat is used, the system queries the real-time exchange rate at order creation and converts it to crypto for collection.
Order expiration time, UTC timestamp in milliseconds. Defaults to 1 hour if omitted. If the provided value exceeds current time + 1 day, it is truncated to current time + 1 day.
The return URL for the order after successful payment, up to 256 characters long.
The return URL for the order after payment failure, up to 256 characters long.
Client name.
Source type of the order.

