Skip to content
All work
White labelFinancial services

Payment aggregator

One integration for every way a customer wants to pay

Online payments in Southeast Asia are fragmented across cards, local wallets, instant bank rails, and QR. Symph built a payment gateway so a merchant integrates once, or not at all, and still accepts all of them.

This is a Symph product. We built it and we run it.

01

At a glance

A payment gateway with hosted checkout, payment links, merchant and branch management, transaction reporting, and settlement controls

Client
Symph product, serving merchants from single-location businesses to multi-branch operations
Industry
Payments infrastructure
Status
Live and operating, under continuous security maintenance
Engagement
Symph-owned product: build, operate, and secure
02

The challenge

A merchant wanting to accept every popular payment method is looking at a development project, not a signup.

  1. The market is fragmented

    Customers expect cards, local wallets, instant bank transfer, QR, and regional wallets, each with its own integration.

  2. Merchants do not have engineering teams

    The people who need this most are least equipped to build it.

  3. Multi-branch merchants need structure

    One account has to cover many locations without mixing up their transactions.

  4. Finance teams need records, not dashboards

    Exportable transaction data and settlement controls matter more than charts.

  5. Payment software is never finished

    Handling other people’s money means a permanent security obligation, and payment-critical paths can never regress while that work happens.

03

How we built it

Symph built the product in three layers, each removing more work from the merchant.

  1. One integration, many methods

    A single integration point gives the merchant cards plus the major local and regional digital wallets and instant payment rails, instead of one integration per method.

  2. Or no integration at all

    Payment links let a merchant send a customer to a hosted payment page without touching code, which is the difference between a product a small merchant can use and one it cannot.

  3. Operate it like payment infrastructure

    Dependencies and platform components are reviewed and updated continuously, with automated behaviour tests guarding payment-critical paths on every release.

04

Modules

  1. 01

    Hosted checkout

    A payment page covering cards, local and regional wallets, instant bank transfer, and QR.

  2. 02

    Payment links

    Shareable links to a hosted payment page, usable without any integration work.

  3. 03

    Merchant and branch management

    One merchant account across multiple branches, with transactions attributed per branch.

  4. 04

    Transactions and exports

    Searchable transaction records with exports for finance and reconciliation.

  5. 05

    Settlement holdouts

    Controls over amounts held back from settlement.

  6. 06

    Reporting

    Operational reporting across merchants, branches, and payment methods.

05

Delivery model

  1. 01

    Symph-owned product

    Symph builds, hosts, operates, and secures the gateway rather than handing it over.

  2. 02

    Continuous security maintenance

    Dependencies and platform components are reviewed and updated as an ongoing discipline, not a periodic project.

  3. 03

    Automated behaviour tests on payment paths

    Every change to a payment-critical path is tested before release.

06

How it’s built

Proven architecture

The gateway runs on Google Cloud with a managed datastore, cached sessions, and automated build and deployment, built for reliability under transaction load.

Secure by default

Encryption, strict access controls, managed secrets, continuous dependency maintenance, and automated regression testing on payment paths protect merchant and cardholder data. Symph follows OWASP-aligned practices and the Philippine Data Privacy Act.

AI-native delivery

Symph’s engineers build and review with AI coding tools like Claude Code and OpenAI Codex, which is a big reason security maintenance keeps pace without stalling product work.

Application
Node.jsExpressTypeScriptRedis
Google Cloud
Google Cloud
AI-native development
Claude CodeOpenAI Codex
07

The result

A merchant integrates once, or sends a link, and accepts cards and every major wallet its customers use.

  • 1integration point for cards, wallets, bank rails and QR
  • 0integration work needed with payment links
  1. Live and operating

    The gateway is a working Symph payment product, not a prototype.

  2. Many methods, one integration

    Cards, local wallets, instant bank rails, QR, and regional wallets are reachable through the same checkout.

  3. Usable without engineers

    Payment links let a merchant collect online payments with no integration work at all.

  4. Built for multi-branch merchants

    Branch-level attribution, transaction exports, and settlement holdouts support real finance operations.

  5. Maintained like payment infrastructure

    Symph runs full security remediation cycles and automated behaviour tests on payment-critical paths rather than deferring them.

More work