Limitations

• UPI mandate migration not supported — Customer mandates on another platform cannot be migrated to Recurly. Customers must cancel existing mandates and resubscribe. Enrollments are tightly coupled with the acquiring partner, merchant, and consumer — when the acquiring partner changes during a migration, re-enrollment is required per RBI and NPCI rules.
• UPI transaction limit — RBI mandates limit individual transactions to 15,000 INR without a consumer two-factor flow. This 2FA is handled by the customer's bank UPI app and is not customizable. Plans, or the combined amount of plans sent in the same purchase signup request, should be at or below 15,000 INR to avoid renewal rejections. See UPI AutoPay documentation for details.
• UPI billing info updates not supported — If a customer needs to update their VPA or bank account, they must cancel their existing mandate/subscription and re-subscribe.
• No ad-hoc or one-time purchases — Customer-initiated one-time purchases and merchant-initiated force collections are not supported.
• Recurly.js not supported — UPI AutoPay and Pix Automatico require direct API integration. Recurly.js is not supported for these payment methods.
• Refunds must be full amount — Partial refunds are not supported through Ebanx.
• Chargebacks not reflected — Chargebacks are not currently supported or reflected in Recurly.
• UPI App deep links do not support free trials — Free trial subscriptions are not available when using UPI App deep links.
• See individual payment method pages for additional limitations.

Definition

Key details

Integration guides

Refer to the individual payment method guides for implementation details:

• UPI AutoPay integration guide
• Pix Automatico integration guide
• Mercado Pago integration guide

Required fields

Ebanx requires specific fields to create a mandate for a recurring subscription.

UPI AutoPay

• VPA (UPI AutoPay) via PGR array. For QR / App Intent flows, send Payment Type and Authentication Type and omit the VPA.
• Customer email address
• Customer first and last name
• Customer billing address (street address, city, region/state, country, postal/PIN code)
  • Street address — House/street name and number (e.g., HOUSE NO. 32, MG ROAD)
  • City — Locality and city (e.g., VILLAGE OF AMARPUR, NEW DELHI)
  • State — State or union territory (e.g., MAHARASHTRA)
  • Postal code — PIN code (e.g., 110019)
  • Country — Country code (e.g., IN)
• Customer phone number

Pix Automatico and Mercado Pago

• Customer name
• Customer billing address
• Customer email address
• Customer phone number
• Tax ID and Tax ID type (required for Brazil)

Mandate preferences

Ebanx payment methods use subscription-level mandate IDs assigned to a customer's subscription at signup. Customers can revoke or pause (UPI only) their mandate from their banking app, which affects the subscription in Recurly.

• Customers cancelling or pausing mandates in their banking app are handled automatically.
• Pausing and resuming subscriptions via a banking app is currently supported with UPI only.

Configuring Ebanx in Recurly

Step 1: Obtain Ebanx credentials

Step 2: Enter credentials in Recurly

Step 3: Set your payment methods

Under Alternative Payment Methods, enable UPI AutoPay, Pix Automatico, and/or Mercado Pago as applicable. No card options appear under Accepted Card Types — Ebanx supports regional alternative payment methods only.

Step 4: Enable currencies

Enable the correct currencies for each payment method:

• UPI AutoPay — INR only
• Pix Automatico — BRL only
• Mercado Pago — BRL, ARS, CLP, MXN, or UYU

Step 5: Select your settlement model

Choose your operational settlement model. Confirm this setting with Ebanx before going live — an incorrect selection will disrupt processing and cause settlement delays.

• Cross-border (default, recommended for most merchants) — Ebanx handles the regulatory last mile on your behalf. You're funded in USD.
• Local settlement (advanced, uncommon) — You handle the regulatory last mile yourself. You're funded in local currency.

Selecting Local Settlement will display a warning. If you've confirmed with Ebanx that your account uses local settlement, proceed. Otherwise, revert to Cross-Border.

Step 6: Save and enable the gateway

Click Add Payment Gateway. Ebanx will appear in your Production Gateways list in Recurly with a status of Enabled.

Step 7: Test the configuration

Run a test transaction in development mode on your Recurly sandbox site before going live. If your settlement model is set incorrectly, you'll receive an Authentication error.

Step 8: Adjust dunning settings

Step 9: Go live

Configuring webhooks in Ebanx

Set the Recurly callback endpoint

The state of your Ebanx dashboard (sandbox or production) determines which service URLs are updated. Sandbox Ebanx URLs must point to Recurly sandbox sites; production URLs must point to production Recurly sites.

https://callbacks.recurly.com/ebanx/YOUR_SUBDOMAIN

For EU-hosted Recurly sites, use:

https://callbacks.eu.recurly.com/YOUR_SUBDOMAIN

Subscription behavior

Retries and dunning

Retries are supported for UPI AutoPay, Pix Automatico, and Mercado Pago when your dunning settings are not configured to expire subscriptions immediately. See the Static Retries documentation and each individual payment method's page for method-specific retry behavior.

Transaction, invoice, and subscription status

For UPI AutoPay and Pix Automatico, subscriptions become active immediately, but transactions and invoices remain in a scheduled/processing state until the pre-renewal notification is received and payment is triggered. If a customer doesn't authorize enrollment or payment via their banking app, the transaction will fail and the subscription will be expired upon rejection.

Supported subscription types

• Trial subscriptions with payment data on file
• Non-trial subscriptions
• Renewals

Features not supported with Ebanx

The following are not supported across all Ebanx payment methods:

• Authorize and Capture and Void transaction types — Ebanx transactions must be refunded, not voided
• Subscription upgrades — mandate amounts and frequency are controlled by the customer's banking app; changes in Recurly can cause declines
• Trials without payment data on file
• Trials using App deep links / intents
• Non-Net-0 terms — Ebanx APMs must be charged on the specific day noted in the mandate; terms above Net-0 can cause failures
• One-time transactions — Ebanx payment methods support renewals only
• Account hierarchy — mandates associated with a parent or child account won't apply to recurring subscriptions
• Aggregated or calendar invoicing — combining existing subscriptions is against mandate regulations in India and LATAM banking institutions
• Bundling subscriptions — same restriction as calendar aggregation
• Multiple subscriptions on a single account — each subscription uses one mandate ID; only one mandate ID is permitted per account
• Merchant admin-created subscriptions — MIT subscription enrollments are not permitted per NPCI regulations (India) and LATAM banking institutions, due to pre-debit notification and consumer authentication requirements

UPI / APAC specific:

• Billing info updates must be made by customers directly in the UPI app

FAQs