Available Request Methods
The following requests are used for information exchange between Partner and System:
Request Direction | Request Description | URL |
---|---|---|
Partner -> System | Payment request, POST | /acquiring/applepay/pay /acquiring/googlepay/pay /acquiring/samsungpay/pay |
Partner -> System | Payment status request, POST | /acquiring/{Service_ID}/check |
Partner -> System | Payment confirmation request (only for two-stage payments), POST | /acquiring/{Service_ID}/confirm |
Partner -> System | Hold cancellation request (only for two-stage payments), POST | /acquiring/{Service_ID}/unhold |
Partner -> System | Refund request | Contact technical support to issue refunds |
Partner -> System | Transaction registry request, GET | Request description provided below |
Where is the value of :
- Test environment:
https://int.8b.world
- Production environment:
https://api.8b.world
{Service_ID}
– The partner's identifier within the system, provided after onboarding.
Every request must include a
Content-Type
HTTP header with the valueapplication/x-www-form-urlencoded
.
The system validates the request for security and correctness. If the security check fails, the system returns HTTP Status 400. In the case of a request validation error, HTTP Status 401 or 403 is returned.
Updated about 1 month ago