Southeast Asia Local Payment Methods: Refunds & Chargebacks

The first refund request from a customer in Manila arrives. Your team checks the payment and finds that the name of the local payment method she used can't answer three questions. It doesn't tell you whether the payment can be refunded, how the request should be handled, or when the customer gets the money back.

Back home in the US or Europe, you never had to ask. Cards answered all three the same way every time: refunds went back to the card, disputes ran through card-scheme chargebacks, and subscriptions renewed on a stored card. Local payment in Southeast Asia does not work that way. When you accept local payment methods in the Philippines, Thailand, Indonesia, and Vietnam, the answers depend on several parties. They include the wallet or bank the customer paid with, the provider that processes the payment for you, and the terms of your own contract.

If you leave those answers to chance, the cost shows up after the sale. A refund that can't go back the way it came can turn into a manual payout and an unhappy customer. A dispute without a card-scheme chargeback behind it still reaches you, through the wallet operator or straight from the customer. A subscription that can't renew on its own may lose the customer at the second billing cycle.

That is why choosing which wallets to add is only half the decision. The other half is what each wallet lets you do after a customer pays with it. This article covers that second half: refunds, disputes, and renewals, in the order you will meet them. It ends with five questions to settle with your payment provider when you sign, before any method goes live.

Key Takeaways

• Four things decide a refund on a local payment method: whether you can start it, how it is processed, how long you have, and when the money reaches the customer. Each can be set by a different party.
• Wallet and bank-transfer payments don't run on card networks, so there is no card-scheme chargeback, but disputes still reach your team.
• A wallet that supports auto-debit doesn't mean your provider, or your contracting entity, can use it.
• Settle five questions with your payment provider when you sign, before any method goes live.

Refunds: Who Controls the Process, and When Will the Money Arrive?

Start with refunds, because they are the first problem you meet after the sale. A refund on a local payment method depends on four things: whether you can start it, how it is processed, how long you have to issue it, and when the customer is credited.

Here is what the companies behind some of these methods say, starting with Maya in the Philippines:

• Maya Checkout: Refunds must first be enabled through your Maya relationship manager and are then available from the day after the payment for up to 180 days.
• GCash and QR Ph payments taken through Maya Checkout: Refunds are processed manually, and the customer's wallet or bank decides when the money arrives.
• GCash: For unrecognized charges, its help center tells customers that refunds are handled by the merchant.
• QRIS paid through DBS Indonesia's digibank app: The bank's guide says a refund goes ahead only if the merchant agrees.
• MoMo in Vietnam: Its developer documentation supports full and partial refunds through its API, within set minimum and maximum amounts.

Every company sets these rules differently, and some do not publish them at all. Before you write your refund policy, run every local payment method through the four checks below.

Methods that refund automatically can share your standard refund policy. Methods that need a manual request or a manual payout need their own support script, and someone in finance who owns the payout. Late refunds belong in that script too: Maya Checkout, for example, still takes manual refund requests between 180 days and one year. If a refund arrives late or not at all, it turns into a dispute with the customer who bought from you. That is the next risk to plan for.

No Card-Scheme Chargeback Doesn't Mean No Dispute Risk

Disputes come next. In the US and Europe, you know how this works with cards: an unhappy customer goes to their bank, and the bank's chargeback process settles the case under card-scheme rules. Payments from a wallet balance or a bank transfer do not run on card networks, so those rules do not cover them. But no card-scheme chargeback does not mean disputes disappear. It only changes the route they take to reach you.

Some wallet operators run their own dispute process, and others send the customer straight to you. Here is how the companies behind two Philippine wallets describe those routes:

• GCash acquiring: For merchants that accept payments through GCash itself, GCash runs its own chargeback process and charges fees only if a case escalates to pre-arbitration or arbitration.
• GCash QR payments: When a customer reports that a QR payment never reached the merchant, the merchant and the merchant's bank review the claim within 6 to 12 business days.
• GCash unrecognized charges: GCash can only check the transaction or unlink the account, and it tells the customer that the merchant handles the refund.
• Maya Wallet: Customers can contest a payment through Maya's purchase dispute form, including goods not received or a refund that never arrived.

So even without a bank or card scheme in the middle, every dispute ends up with your team, and your people have to resolve it.

Prepare for that on every local payment method. Ask your provider whether it can receive disputes raised through a wallet and whether it handles them. Then ask how it hands them over to you. Agree with your provider which records each side keeps for every payment, from the order and delivery to any refund. Those records are your evidence when a dispute arrives. Inside your company, give wallet complaints a dedicated owner in support, so each one is settled before it turns into a formal claim.

All of this covers one-off orders, which are only half the picture. If your product is sold by subscription, the next question is whether a local wallet lets you charge the customer again automatically.

Renewals: A Wallet That Supports Auto-Debit Doesn't Mean Your Provider Does

Renewals come last. In the US and Europe, a stored card renews on its own. Many digital wallets in Southeast Asia offer the same feature. There is a catch, though: a wallet that supports auto-debit does not mean you can use it.

Here is what two wallet operators publish about their own features:

• DANA: Its developer documentation describes a subscription product that charges a user on an agreed schedule, with an amount that is either fixed or varies by billing cycle.
• GCash: Its help center lists Google, Apple, Spotify, and Netflix among the subscriptions that are deducted automatically from GCash accounts.

Both show the feature exists. So why might you not be able to use it? Because that depends on two things: your provider and the entity you contract through. For every wallet you plan to bill on a schedule, ask your provider two questions:

1. Does it support that wallet's automatic charges, not just one-off payments?
2. Can the entity you contract through use the feature?

Ask about saved wallets and scheduled charges separately. A wallet saved for faster checkout is not automatically set up for automatic charges.

If auto-debit is not available, you will need manual renewals, and that is ongoing work for your team. For example, you may have to send every customer a payment link before each billing cycle.

What a wallet operator says a method can do is not the same as what you can actually use. Your provider decides that, which brings us to the last step: the questions to settle before you sign.

Before You Launch: Five Questions to Ask Your Payment Provider

The first refund, the first dispute, and the first failed renewal all lead back to the same place: your payment provider. So settle the answers when you sign, not after a customer complains. If you are planning to expand into Southeast Asia with local payments, take these five questions into the contract talks. Ask them for every local payment method you plan to offer.

1. Can refunds be started for this method, and do they need to be enabled first? If refunds are off by default, your first refund request will stall while someone works out who can switch them on.
2. How is a refund processed, and how long is the refund window? The answer shows which methods can follow your standard refund policy and which need a manual process and a plan for late refunds.
3. Once a refund is processed, how long until the customer has the money? Your support team needs this to tell a customer when the money will arrive, without guessing.
4. How do disputes raised through the wallet reach us, and which records does each side keep? Without a card-scheme chargeback, this is the route every dispute will take, and those records are your evidence.
5. Do you support automatic charges on this wallet, and can our contracting entity use them? If either answer is no, plan for manual renewals before you sell a subscription on that method.

Get the answers in writing, one method at a time. With them, you can build your refund policy, support scripts, and finance plan around how each method actually works, rather than around habits from card payments.

Conclusion

Learning how to expand into Southeast Asia with local payments starts with knowing what each local payment method lets you do after the sale, not just which ones to add. Check refunds, disputes, and renewals method by method, and settle the answers with your provider before you launch.

These rules are far easier to settle before launch than after the first complaint. Antom supports 300+ payment methods across 200+ countries and regions. Tell us your contracting entity and target markets, and we will confirm which methods you can switch on and the limits for each. Talk to Antom about payment methods for Southeast Asia.