Describe your checkout
Tell the team which website or platform you use, how orders are created and where crypto payment collection should appear. Include whether you need a shared payment link or payment creation inside your own checkout.
- Describe your order reference and amount/currency rules.
- Identify who will implement and maintain the integration.
- Agree how your system will handle pending, completed, expired and cancelled requests.
Keep payment creation separate from fulfilment
A created request or a browser return is not proof of payment. Define how your integration checks payment state and when your business will fulfil an order. Handle repeated notifications or retries without creating duplicate fulfilments.
Test the complete journey
Use the integration materials and test setup agreed with the BOS.PAY team. Test success, abandonment, expired requests and interruptions, including a customer closing the browser. Keep credentials on the server where required and never put secret tokens in support messages or screenshots.
Request technical help
Provide the platform, environment, order/payment reference, timestamp, error code and a redacted example of the request/response. Explain the expected and actual behaviour. Ask for the current API materials instead of relying on an example from an unrelated provider.