Deliver SDK receipts
Use the returned receipt content and keep delivery status separate from the financial outcome.
Wait for the result
Issue the receipt after the transaction result is returned. The SDK supports receipt data for the completed sale or refund; do not generate an approval receipt from a progress callback.
Choose the delivery route
Email and SMS may be sent from the mobile application using the returned data, or from central servers when enabled through TMS. processReceipt starts delivery; observe its completion event. Server delivery can carry costs and requires configuration.
Preserve certified content
The documented receipt content is scheme/acquirer certified and must not be modified. Keep any custom order confirmation separate from the payment receipt. Ask for the destination at the appropriate point in your checkout instead of embedding it in logs.
Normalize telephone destinations
For central-server SMS, provide an international dialing code. The documented fallback is UK +44 with leading trunk zero removal unless TMS defines another default. Supply the country code explicitly for US and multi-country customers; a successful payment does not imply a successfully delivered SMS.