Cash & Codes Bundle
Your bridge to mass-market acquisition via asynchronous payments.
The Cash & Codes bundle is your customer acquisition channel for emerging markets. It is purpose-built to connect you with the 876 million users who rely on cash, vouchers, or instant digital payments, a group that includes a large unbanked population.
Technically, this bundle is designed around an asynchronous payment flow. You generate a voucher or QR code at checkout, and the payment is confirmed later via a webhook when the user completes the transaction. This model is essential for reaching the 57% of adults in these regions who don't have a credit card.
Cash & Codes Bundle Payment Flow
This high-level flow illustrates the end-to-end process of how a payment is handled within this Payment Bundle. From the checkout initiation to the final confirmation, each step follows the same architectural logic shared by all payment methods in this bundle.
Available Payment Methods
Access 15+ essential cash and codes methods across 11 countries with the Cash & Codes bundle. Card & Codes methods included in this bundle:
Payloads Comparison
The core value of this bundle is its consistent integration pattern for all voucher and code-based payments. Building the webhook logic for one method means you've built it for all. The same pattern is reusable for any asynchronous payment, including those in other bundles like Trusted Redirects.
Using our Payload Comparison tool, you can select a payload and two bundles to easily spot key differencesin API behavior and integration details.
API Effort Score
API Effort Score shows the coding effort to integrate with another payment type, using a percentage-based thermometer and a qualitative description of the integration effort:
Very low effort: Same endpoint and structure; only parameter values change.
Low to very low effort: Nearly identical endpoint and structure; adjust parameters and a few fields.
Low effort: Same endpoint and flow; add or remove some fields.
Medium effort: New endpoint or new flow; requires writing new code.
The core API endpoint and logical flow remain the same. You may need to add or remove some fields in the request, but the overall data structure will feel very familiar.
- The main differences in the request are typically limited to the payment_type_code and currency_code fields to specify the local method.
- The overall asynchronous structure, using a webhook for payment confirmation, remains identical, making integration straightforward.
Still need help?
We hope this article was helpful. If you still have questions, you can explore the following options:
- Merchant support: Contact our support team at sales.engineering@ebanx.com for assistance.
- Not a partner yet? Please complete the Merchant Signup Form, and our commercial team will reach out to you.














