Binance Pay's Merchant API documentation defines payment-order creation and management, QR checkout, authentication and webhook notifications. Merchant acquiring and partner transfer or collection scenarios connect payment requests with result codes, status handling and journeys.
TL;DR:
- Binance Pay’s merchant API covers payment orders, authentication and notifications.
- The reviewed create-order endpoint is version 2.
- That endpoint label does not version every API in the family.
Summary
Merchant integration
Binance’s developer documentation describes Binance Pay merchant and partner integration, including QR acquiring and supported transfer or collection scenarios.
Create-order endpoint
The reviewed version 2 create-order endpoint defines request and response fields for a payment order. Its outputs include QR and checkout-related information.
Results and notifications
Authentication and webhook references accompany order creation, with result codes defining possible API outcomes. These support the merchant’s handling of payment initiation and subsequent events.
Endpoint-level versioning
The version 2 label belongs to the named create-order endpoint. The living API family is not uniformly version 2, and its proprietary QR output does not itself establish an EMVCo QR payload specification.
Keywords
- Merchant APIs
- Payment Orders
- QR Acquiring
- Authentication
- Webhooks
- Checkout URLs
- Result Codes
- Order Responses
- Partner Integration
- Binance Pay