Before calling a payroll rail faster or cheaper, measure the full corridor—from payer funding to beneficiary access, reconciliation, exceptions and recourse.
Executive summary
Current reporting from Philstar and ABS-CBN describes a BPI–Meridian initiative using stablecoin settlement rails for cross-border inflows into the Philippines. The first stated rollout use case in that reporting is payroll credits or disbursements for workers including freelancers and virtual assistants.
That is a useful operating case, but it is not yet an end-to-end performance result.
A stablecoin leg may change how institutions clear or settle value while leaving other parts of payroll untouched: employer funding, foreign-exchange conversion, local-account credit, payroll reporting, failed-payment handling and beneficiary recourse. The public record reviewed for this note does not identify the exact stablecoin, chain, issuer, redemption path, pilot fee schedule, FX spread, timing SLA or refund workflow.
The practical conclusion is reviewer-first: the useful unit of analysis is the whole corridor, not one settlement event.
What current reporting establishes—and what it does not
The public reporting aligns on three bounded points:
- BPI and Meridian are reported to be testing or preparing stablecoin settlement rails for cross-border inflows into the Philippines.
- Payroll credits are the first stated use case in that reporting.
- The initiative is framed around faster or lower-cost cross-border movement and coordination with the relevant regulatory perimeter.
Those reports do not provide a direct BPI pilot release, a direct Meridian technical note or a complete pilot operating file. They do not prove that the service is in full production, that beneficiary funds arrive faster, that the total corridor costs less, or that every legal, payroll, tax and compliance question is closed.
That distinction matters because a faster settlement leg can coexist with a slow or expensive last mile.
The corridor starts before the stablecoin leg
A worker does not experience “settlement infrastructure.” The worker experiences whether the correct amount becomes available in the correct account at the expected time—and what happens when it does not.
A treasury or payroll reviewer should therefore separate at least seven stages.
1. Payer funding
How does employer or client money enter the corridor? A funding rail can introduce its own cut-off times, bank fees, returns and identity checks before any stablecoin-related step begins.
Meridian documents another Philippines-linked product that can receive funds through ACH, wire, FedNow and RTP before conversion and local transfer. That is relevant infrastructure context, not proof that the reported BPI pilot uses the same path.
2. Institutional settlement
Which institutions exchange value, and what marks the settlement leg complete? “ Stablecoin-compatible clearing ” is a vendor capability description. It is not, by itself, the identity of the token, chain, transaction or legal settlement state in this pilot.
3. Stablecoin identity and redemption dependency
The exact stablecoin, network, issuer, reserve record and redemption path were not found in the public pilot sources reviewed.
Without that identity, a reviewer cannot complete issuer-specific reserve, liquidity, redemption or smart-contract analysis. A generic reference to stablecoins should not be upgraded into an assumption that the pilot uses USDC, USDT or any particular network.
4. FX conversion
Where is the USD/PHP conversion executed? Which benchmark or rate source applies? What spread is charged, when is the rate locked, and who bears a failed or delayed conversion?
A settlement fee can be low while the total delivered-cost difference is driven by FX.
5. Local payroll or account credit
BPI separately documents an ePayroll/BizLink stack with digital onboarding, batch payroll files and daily reports. That confirms that BPI operates digital payroll infrastructure. It does not establish that ePayroll, InstaPay, PESONet or another named BPI surface is the exact last-mile rail for this pilot.
The reviewer still needs the final destination: payroll account, ordinary bank account, wallet or another form of local credit—and the point at which the beneficiary can actually use the funds.
6. Reconciliation and reporting
The evidence file should connect the payer instruction, settlement reference, FX conversion, local credit and payroll record.
One dashboard status is not enough. The reviewer needs common identifiers, timestamps, amounts, rate details, source systems and a record of any manual intervention.
7. Exceptions and recourse
Who owns a wrong beneficiary, failed conversion, delayed credit, duplicate payment, sanctions or AML hold, refund, reversal or worker complaint?
Stablecoin settlement does not remove these cases. It changes the dependency map and may change which institution has the evidence needed to resolve them.
Corridor evidence checklist
| Corridor stage | Evidence to retain | Reviewer question | Public pilot evidence status |
|---|---|---|---|
| Payer funding | Funding instruction, originating rail, amount, fees, cut-off and sender approval | When does the corridor start, and what can fail before settlement? | Not found at pilot level |
| Settlement instruction | Institutions, settlement asset, transaction reference and completion rule | What exactly settled between which parties? | Reported at a high level; technical record not found |
| Stablecoin identity | Token, network, issuer, reserve/attestation source and redemption path | Which instrument and dependency stack are actually used? | Not found |
| FX conversion | Rate source, spread, lock time, conversion party and failed-FX handling | What determines the PHP amount received? | Not found |
| Local payout | Destination account/rail, credit timestamp and availability status | When can the beneficiary use the funds? | Exact pilot rail and SLA not found |
| Payroll record | Payroll file, worker identifier, gross/net amount and reporting status | Does the payroll record match the delivered credit? | BPI payroll capability documented; pilot use not confirmed |
| Reconciliation | Common IDs, amounts, timestamps, system records and manual adjustments | Can the whole corridor be reconstructed without inference? | Pilot reconciliation file not found |
| Exceptions | Failure code, owner, escalation, retry/refund/reversal and communication record | Who resolves each failure and on what clock? | Not found |
| Recourse | Complaint route, responsible institution, evidence package and resolution status | Where does the worker go when the credit is wrong or late? | Not found |
What to measure before saying “faster” or “cheaper”
A credible comparison should use the same corridor boundaries before and after the change.
For speed, measure:
- payer release to institutional settlement;
- settlement to FX completion;
- FX completion to beneficiary credit;
- beneficiary credit to funds actually available;
- time to resolve failed or delayed cases.
For cost, measure:
- payer-side bank or funding fees;
- settlement and network fees;
- stablecoin issuance or redemption costs, where applicable;
- FX spread and conversion charges;
- local payout fees;
- exception, return and manual-reconciliation costs.
For control quality, retain:
- authorization evidence;
- stablecoin and counterparty identity;
- sanctions/AML and beneficiary checks;
- shared transaction identifiers;
- reconciliation results;
- exception ownership and ageing;
- complaint and recourse records.
A claim that one ledger event is faster does not answer these corridor-level questions.
What this case does not prove
The reported initiative does not yet prove:
- lower end-to-end cost;
- faster beneficiary access;
- a specific stablecoin, chain, reserve model or redemption route;
- that BPI ePayroll, InstaPay or PESONet is the pilot’s exact last-mile path;
- full production readiness or complete BSP clearance;
- accounting, payroll, withholding, tax or legal treatment;
- reserve assurance, security assurance or suitability;
- adoption, customer demand, WTP, traction or PMF;
- any Treasury Desk custody, execution, payment-initiation or payroll capability.
The bounded value of the case is methodological: it shows why a stablecoin payroll review file must measure the entire corridor.
Reader-facing sources
Pilot reporting — pilot-specific claims remain attributed to current reporting
- Philstar — “BPI to pilot stablecoin rails for cross-border payroll.” 26 July 2026.
- ABS-CBN News — “BPI to pilot stablecoin for cross-border payments to virtual assistants, freelancers.” 23 July 2026.
Product and operating context — not proof of the exact pilot architecture
- Meridian — current product page.
- Meridian — “Meridian Launches U.S. Accounts in the Philippines.” 15 December 2025.
- BPI — “BPI introduces ePayroll, an effortless payroll solution for businesses and employees.” 10 March 2025.
Oversight and methodology context
- Bangko Sentral ng Pilipinas — Payments and Settlements.
- Bangko Sentral ng Pilipinas — BSP Verifier. The category guide does not establish Meridian’s exact status in this pilot.
- CPMI/BIS — “Considerations for the use of stablecoin arrangements in cross-border payments.” 31 October 2023.
Locator and evidence limitations
- A direct BPI pilot press release was not located in the public sources reviewed.
- A direct Meridian technical note for the pilot was not located in the public sources reviewed.
- The public sources reviewed did not identify the exact stablecoin, network, issuer or redemption path.
- The public sources reviewed did not provide the pilot-specific fee schedule, FX spread, timing SLA or refund path.
Public caveat
This note is a public-source review framework, not a payroll audit, payment-service assessment, reserve assurance, legal or regulatory conclusion, accounting or tax treatment, or recommendation. Pilot-specific statements remain attributed to current reporting. Product pages describe broader capabilities and do not prove the exact pilot architecture.
Reviewer question: Which corridor field would you require before describing a stablecoin payroll flow as faster or cheaper? Please keep examples public or synthetic.