Limitations

• GCash billing info updates not supported — If a customer needs to update their wallet funding source, they must do so in the app itself.
• No ad-hoc or one-time purchases using stored billing info — Customer-initiated one-time purchases using stored billing info and merchant-initiated force collections are not supported.
• Chargebacks not reflected — Chargebacks are not currently supported or reflected in Recurly.
• GCash one-time payments don't store billing info by design — Customers must reauthenticate via Recurly.js every time.
• Free trials — Free trials are not yet supported with this wallet.

Definition

dLocal is a full-service payment management platform built for emerging markets in APAC, specifically the Philippines. It supports subscription enrollment, recurring transactions, one-time payments, and refunds for GCash. You'll need an existing dLocal relationship and a valid Integration Key to connect dLocal with Recurly.

Key details

Feature	Details
Services that work with Recurly	Payment processing, subscriptions, one-time / ecommerce payments with GCash
Supported operations	Subscription signups, recurring transactions, refunds, one-time purchases
Supported payment types	GCash
Supported card brands	N/A
Gateway-specific 3DS2 supported	No
Card on file supported	No
Regions	GCash: Philippines
Currencies	PHP only
Gateway features	None

Setup

1

Obtain dLocal credentials

Log in to your dLocal account to retrieve the credentials you'll need to connect it with Recurly.

1. Log in to your dLocal account. Engage with dLocal to address any applicable contracts and fees before proceeding. Access your dLocal Production account for production keys, or Sandbox account for sandbox keys.
2. Within your dLocal merchant dashboard, select Settings, then choose the Integration option.
3. Copy the X-Login, X-Trans-Key, and the Secret Key. You don't need the smartfields API key. Save these for the next step.
2

Enter credentials in Recurly

Add your dLocal credentials to a new payment gateway in Recurly.

1. In Recurly, navigate to Configuration → Payment Gateways, select Add a New Gateway, then choose dLocal.
2. Paste your X-Login, X-Trans-Key, and Secret Key into the applicable fields, shown below.

3

Set your payment methods

Under Alternative Payment Methods, enable GCash — it's the only option. No card options appear under Accepted Card Types, since Recurly doesn't currently support card processing with dLocal.

4

Save and enable the gateway

Select Add Payment Gateway. dLocal appears in your Production Gateways list in Recurly with a status of Enabled.

5

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.

6

Go live

Confirm your Recurly site has production dLocal credentials entered, and that your dLocal account is in Production mode.

TipKeep your dLocal credentials secure and limit access to authorized personnel. Consult your dLocal representative to confirm your account is in good standing and compliant with all relevant regulations.

Integration guides

Refer to the individual payment method guides for implementation details:

• GCash integration guide
• One-time payments / ecommerce integration guide

Payment method specifics

GCash Wallet

dLocal and the GCash method require specific fields to authorize a payment successfully.

• Customer first and last name
• Customer email address
• Customer billing address (street address, city, region/state, country, postal/PIN code)
  • Street address — House/street name and number
  • City — Locality and city
  • State — Province
  • Postal code — Postal / zip code (4 digit)
  • Country — Country code (e.g., PH)
• Customer phone number

FAQs

I am using the billing info ID for one-time purchases, and it's failing. What can I do?

Recurly's integration with dLocal includes GCash only, which doesn't allow CIT one-time purchases using on-file tokens. You must offer the customer the option of using GCash and use Recurly.js to allow them to authenticate their account for one-time / line item purchases. If there is a stored payment method, its specific use is for active subscriptions only.

I'm setting the store_billing_info API field to 'true' on a line item purchase, but I'm getting an error. What gives?

One-time, or more specifically, ecommerce transactions using GCash do not produce a storable token for future purchases. Customers must re-authenticate with their app for every purchase. You'll need to set the store_billing_info API parameter to false and set up your checkout flow to always prompt the user to select the payment method during checkout, rather than using a stored method.