Say you run a 15-person online retailer split between Jakarta and Cebu, and you route payments through Xendit, PayMongo, and Midtrans depending on the market. This cycle, all three vendors moved, but only one of them shows up as a bigger number on your next invoice. Xendit added a new fee schedule with a hard effective date. PayMongo shipped a card product. Midtrans pushed out a batch of smaller features. Only Xendit touched pricing, and the way it's structured, a merchant who ignores it could end up paying for the same oversight three separate ways.
Xendit
Xendit is introducing a new "Xendit Processing Fee" stacked on top of existing payment-method fees, effective October 1, 2026 across most markets it serves. If your business is contracted to Xendit Philippines Inc., the change lands a month earlier, on September 1, 2026 — worth putting on a calendar now, not discovering in September.
The fee hits every transaction attempt, not just the ones that succeed. Payouts, refunds, and failed charges all count. For Indonesia specifically, the published per-method rates are QRIS at 0.7%, GoPay and OVO e-wallet acceptance at 1.5%, an Indonesian-issued credit card at 2.4%, and QR Indonesia at 0.7% plus $0.20 per transaction.
Three flat fees ship alongside it. A Monthly Minimum Fee of $50 — roughly Rp 790,000 or ₱2,850 at current rates — lands on dormant accounts. A Monthly Maintenance Fee of $250, about Rp 3.95 million or ₱14,200, applies to any account still running Xendit's legacy payments API. A Chargeback Dispute Fee of $25 hits per card dispute.
That legacy-API fee is really a migration deadline dressed up as a maintenance charge. I'd bet most of the merchants still on the old API haven't noticed yet. Xendit's notice sets October 1, 2026 as the cutover date to its current Payments and Payouts API.
This is what actually hits your bill. A merchant on the legacy API who lets one account go dormant now pays three new line items instead of one. Migrate off the legacy API and keep every account active, and you only absorb the new per-transaction Processing Fee — annoying, but a single number instead of a stack.
Source: Xendit Pricing Policy, Xendit Help Center.
PayMongo
PayMongo teamed up with Mastercard and card-issuing processor Paymentology to launch a virtual prepaid business card on June 9, 2026. Paymentology and Mastercard license the issuing infrastructure to PayMongo, so PayMongo can issue pre-funded cards to its merchants without holding a banking license of its own.
The card is pre-funded, not credit-based. A merchant loads it, then spends against that balance for supplier payments or team expenses. The target segment is Philippine SMEs that don't qualify for a business credit card or a corporate card program through a bank, and that's a real gap. Plenty of profitable five- and ten-person shops in Manila get turned down by banks purely on paperwork, not revenue.
This follows PayMongo's site rebuild on March 2, 2026, and its April 2026 payments-infrastructure work — the legacy API and endpoint decommission on April 5, and BIR Digital Tax Withholding on payouts effective April 1. No PayMongo transaction-fee rates changed alongside the card launch. The standard rate is still 3.5% plus ₱15 per card transaction and 3% for e-wallets. On a ₱2,500 sale, that's roughly ₱103 gone before the deposit even clears.
Source: BusinessWorld Online (June 9, 2026), PayMongo product changelog.
Midtrans
Midtrans shipped three product changes in July 2026, though it hasn't published the exact release day. Payment Link now supports a QR-code format for the link itself, alongside the existing copyable-text template, so a merchant can display a scannable code instead of texting a URL that might get flagged as spam. Promo Management added voucher-code-based campaigns as a mechanic distinct from Midtrans's existing percentage and fixed-discount promo types. That's useful if you're running a campaign through an influencer in Jakarta and want a code you can trace back to that one person.
On the reporting side, Midtrans added a Column Transaction Split view inside its Consolidated Cross Border and Non-Cross-Border reports, plus a Single Auto Withdrawal Report for merchants subscribed to the Transaction Split feature. Separately, Midtrans confirmed its Mobile SDK is being deprecated: no new feature development, no new integration support, and that includes the SDK Demo. If your app still depends on it, start looking at Midtrans's newer integration paths now rather than after something breaks in production.
No Midtrans transaction-fee changes were published alongside these releases. Pricing stays per-successful-transaction, with no separate implementation or maintenance fee — the one vendor in this batch that didn't touch money at all this cycle.
Source: Midtrans documentation and release notes (docs.midtrans.com).
Coverage note
Only Xendit changed price this cycle, and it's an addition to the fee schedule rather than a tier change. That's a new per-transaction Processing Fee plus three flat fees covering dormant accounts, legacy-API maintenance, and chargeback disputes, effective October 1, 2026 (September 1 for Xendit Philippines Inc. merchants). Anyone still on Xendit's legacy API has until that date to migrate before the $250-a-month maintenance fee kicks in — call it about Rp 3.95 million or ₱14,200 a month for doing nothing. PayMongo's card launch and Midtrans's July releases are feature ships with no attached price change, which is the more common outcome most cycles. Most weeks in SEA payments infrastructure, somebody ships a feature and pricing just doesn't move.