

Local Payout Funding
On-Platform Transfers
Local Currency Payouts
The company is a Singapore-headquartered online travel platform where customers book hotels, flights, tours, and car rentals. Its inventory spans more than 230 countries and territories and 600+ airlines integrated into its booking service. On the customer side, it already accepts both traditional and stablecoin payments, and it pays a wide base of travel suppliers and vendors as well as its own staff.
To support that, the platform needed a partner that could fund its payouts from a single balance, move money between its two entities, and pay vendors and disburse employee salaries in local currency, all through one integration. It turned to Tazapay for that infrastructure.
That balance is funded through fiat top-ups, with a dedicated USDT wallet also enabled, giving the platform more than one way to bring funds in as it scales, consistent with how it already handles payments on the customer-facing side of its business.
As the platform built out its payout model, several gaps shaped the partner it needed.
The platform wanted to pre-fund its outbound payments rather than raise a bank transfer every time a payout run was due, so that funds were already in place when vendor and salary disbursements needed to go out.
The platform needed funds to move cleanly between its two entities, without a manual bank instruction for each movement.
The platform pays travel suppliers and vendors and disburses employee salaries, and needs these to land in local currency through local rails rather than correspondent banking, where cost and settlement time are both less predictable.
The platform wanted more than one way to fund its payout balance, fiat and stablecoin, without maintaining separate infrastructure for each.
The platform wanted funding, transfers, and outbound payouts on a single integration rather than stitching together separate providers for each leg.
Tazapay gave the platform a funding and payout stack built around local currency disbursement, on one integration.
Virtual Account for Fiat Funding.
Tazapay provides a virtual account into which the platform tops up fiat. Balances sit ready to be deployed, so a payout run is never waiting on an inbound transfer to clear.
Stablecoin Funding Option.
Tazapay enabled a dedicated USDT wallet on one of the platform's entities. Stablecoin held in that wallet is converted into fiat ahead of settlement and pooled into the shared virtual account, giving the platform an additional route into its payout balance alongside fiat top-ups.
Account-to-Account Transfers.
The merchant moves funds between it's two entities, keeping movement simple and on-platform rather than manual.
Local Currency Vendor Payouts.
Platform's travel suppliers and vendors are paid in local currency through local payout rails.
Employee Salary Disbursements.
The same payout rails handle the platform's payroll, disbursing employee salaries in local currency alongside its commercial payments.
Single Integration.
Fiat funding, stablecoin funding, transfers, vendor payouts, and salary disbursements all run through one Tazapay integration.
Step 1. Fiat is deposited into a named virtual account held in the company’s name. Stablecoins such as USDC or USDT are deposited into a separate stablecoin wallet on Tazapay and converted into fiat before settlement.
Step 2. Funds are held as a balance in the virtual account, ready to fund outbound payments, regardless of whether they originated in fiat or stablecoins.
Step 3. When required, the company can transfer funds between its own entities.
Step 4. The platform pays vendors and travel suppliers in local currency through local payout rails.
Step 5. The same payout rails are used to disburse employee salaries in local currency directly to their bank accounts.

The platform runs its payouts, funding, and internal transfers on Tazapay today, with both fiat and stablecoin as options for getting funds into its payout balance. Tazapay's modular infrastructure means additional payout corridors and funding rails can be enabled without rebuilding the integration as the platform's needs grow.