Recurring Alternatives Bundle
Your engine for predictable revenue via tokenized, recurring-native APMs.
The Recurring Alternatives Bundle is designed for businesses that rely on predictable revenue, such as SaaS, streaming, and gaming. It provides an alternative to card-based recurrence, helping merchants to bypass common roadblocks like credit limit availability and reduce involuntary churn. This bundle offers the most reliable path to enable both scheduled subscription and frictionless on-file, one-click payments.
Technically, this bundle is built around a tokenization and mandate flow. This allows you to perform server-to-server charges against a customer's account without requiring them to be present for every transaction, dramatically reducing churn and improving the user experience.
Recurring 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.
The first flow illustrates the initial Enrollment Process, where the customer is registered in the system and the involved parties exchange the necessary information to securely enable future payments:
Once enrollment is complete, the following flow shows the Payment Process, where transactions are processed automatically in the background for a fast, frictionless checkout:
Available Payment Methods
Enable 6+ powerful recurring methods across 8 countries with the Recurring Alternatives bundle. Recurring methods included in this bundle:
Argentina
Brazil
Chile
Colombia
India
Mexico
Peru
UruguayPayloads Comparison
The core efficiency of this bundle is its consistent architectural pattern for creating andcharging mandates. Once you have implemented the logic for one method, expanding to another is straightforward.
Using our Payload Comparison tool, you can select a payload and two bundles to easily spot key differences in 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: The API endpoint and core data structure are identical. You'll primarily be changing parameter values within the existing request. No new logic is required.
- Low to Very low effort: The API endpoint and overall data structure remain nearly identical. You will mostly adjust parameter values and possibly add or remove a few fields within the existing request.
- Low effort: 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.
- Medium effort: Requires implementing a new API endpoint or a completely new logical flow. You'll need to write a new block of code to handle this flow.
The API endpoint and overall data structure remain nearly identical. You will mostly adjust parameter values and possibly add or remove a few fields within the existing request.
- This score represents an average. While the core logic for managing subscriptions is highly reusable, the initial enrollment for some methods may have unique rules (e.g., Pix Automático vs. a digital wallet).
- Once a payment method is enrolled, the process for handling one-click payments and recurring charges follows a consistent, straightforward pattern across the bundle.
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.