Go-live checklist

Before accepting customer payments, check the following:

• Your API base URL is correct, your workspace is active, and your key has the permissions your application needs.
• Customers can authorize an eligible Deriv account and reconnect when authorization expires.
• Your server checks which customer owns each connection.
• Payment screens use current markets, rates and limits.
• You save idempotency keys and transfer UUIDs before submission, and recover the same transaction after a lost response.
• You handle deposit codes, checkout redirects and USSD instructions where available.
• Withdrawal verification, email resend and completion all use the same transaction.
• Errors and rate limits do not cause duplicate payments.
• Your application waits for completed before crediting a customer or fulfilling a payment. Unresolved payments stay pending until their outcome is confirmed.
• SSE reconnects after interruptions, with polling as a fallback.
• Customers confirm transfers and check their balances before dismissing an unresolved transfer.
• Reports group amounts by currency and calculation basis.
• API keys, access tokens and verification codes stay out of browser code and logs.

Arrange controlled payment tests with Deripay before launch. Validate actual collection, Wallet funding and payout for the payment methods you will offer; passing request-schema tests alone does not confirm settlement.