DESIGN PROTOTYPE · Concept only; no financial service, payment processing, or online forms are operational.
For Philippine businesses

Payment experiences shaped around your business.

Your operating model should shape how your payments work. Start with the use case, then design the right collection, reporting, and disbursement flows.

Who we’re designing for

Start where your business starts.

Suggested audience architecture inspired by PayMongo’s clear use-case navigation, but tailored to Vertex’s narrower merchant-payments scope.

Online commerce

Help online sellers connect customer collections to order-level tracking and reconciliation.

Online use cases

Retail & services

Support merchant teams that need straightforward digital collections and practical daily reporting.

Retail use cases

Platforms & enterprises

Evaluate integration and control needs for higher-volume or more complex merchant workflows.

Platform use cases
Online commerce

From customer checkout to merchant reporting.

For businesses selling through websites, messaging channels, or apps, the focus is customer payment options and clear reference-based status reporting.

  • Payment collection via eligible channels
  • Order or invoice reference association
  • Payment status review and reporting
  • Settlement visibility for finance teams
Explore collections
Customer order · conceptDemo
Orders & paymentsMerchant #ONLINE-1042
₱3,400

Collection reference linked to transaction status.

Sample operational recordPayment matchedNo actual payment processed
In-person collection · conceptNot scannable
₱1,690.00

Sample checkout counter payment

Retail & service businesses

Help every counter team close the loop.

Where payments happen in person, simplicity matters. Explore QR-based collection concepts and daily monitoring workflows.

  • Discuss supported QR Ph merchant collection flows
  • Identify paid transactions using references
  • Summarize daily collection activity
  • Escalate unmatched transactions
Discuss retail payments
Platforms & enterprises

When payments touch multiple teams, make the rules explicit.

For larger workflows, focus on how funds move, who owns each step, how records reconcile, and which integration or approval controls are needed.

  • Merchant- and partner-level process mapping
  • Structured transaction and payout references
  • Reporting aligned with finance operations
  • Eligibility and channel availability assessment
Review integration concept
Multi-team operationsIllustrative
Business operation

Payment request and merchant reference

↓
Collection & status workflow

Eligible partner route and transaction outcome

↓
Merchant visibility

Reporting, exception handling, and reconciliation

Every use case starts with a question

How does your business get paid?

Share your use case and the team can assess possible solutions and readiness.