GCash for Business

Merchant copilot: tester's guide

This demo onboards a merchant end to end through a chat conversation, saves progress by email, verifies registrations against mocked DTI and SEC registries, collects documents, and gives reviewers an admin panel with decisions and applicant emails. Everything below can be tested in a browser with no setup.

Open the chatAdmin panelEmail outbox

Two-minute happy path

  1. Open the chat and give any first name and an email you can retype later.
  2. Pick Sole proprietor, then a volume of PHP 250,000 to 1,000,000.
  3. Enter DTI registration number 2034567. It verifies and skips the questions the registry already answered.
  4. Answer the remaining check, then upload any image for each document (or downgrade to Tier 1 to skip most).
  5. Press Confirm to e-sign. Then open the admin panel, click your application, and approve it.
  6. Open the outbox to read the confirmation and decision emails that were generated.

Registry test numbers

DTI covers sole proprietors, SEC covers partnerships and corporations. Micro sellers and professionals skip the registry entirely. A registration number is an opaque identifier: it encodes nothing about the owner, industry, or risk. The flow only checks the format, then queries the registry for those facts. This demo uses a mocked registry, and the numbers below are test inputs wired to return each outcome.

InputFormat checkWhat the demo registry returns
2034567Valid DTI formatRegistry query verifies the business name and owner, proceeds to checks
2034500Valid DTI formatRegistry query returns a different registered owner, flagged for manual review
2034513Valid DTI formatRegistry query returns a high-risk business activity (lending), flagged for additional review
1234Invalid DTI formatRejected before any query, asks the applicant to re-enter the number
CS201512345Valid SEC formatRegistry query verifies the company registration
CS12Invalid SEC formatRejected before any query, asks the applicant to re-enter the number

Capabilities and how to test them

Guided application

The whole application is a conversation: name, email, business type, monthly volume, registry check, eligibility, documents, e-sign.

Try it: Open the chat and follow the chips. Pick Sole proprietor, the lowest volume, registry number 2034567, answer the checks, then press Confirm and submit.

Save and resume by email

Progress is saved server-side under the applicant's email after every step.

Try it: Complete a few steps, reload the page (or open it on another device) and enter the same email. The transcript and step come back with a welcome-back message.

Corrections in plain chat

Applicants can fix their details without restarting.

Try it: Type "change my email to new@x.ph" or "call me Carla" into the message box at any point after the email step.

Free-form questions

Anything typed that is not an answer to the current step is answered from the requirements knowledge base, powered by Claude with a curated fallback.

Try it: Ask "what does a corporation need?", "who is the authorized signatory?", "what should the selfie show?" or something oblique like "my brother owns the store, can I sign up?"

Five business types, three tiers

Micro seller, sole proprietor, partnership, corporation, and licensed professional (PRC), each mapped to Starter, Premium, or Pro by monthly volume. Documents follow the tier first: Tier 1 Starter needs only a government ID and a selfie, on any structure.

Try it: Run the flow once as a corporation above PHP 5M (long document list) and once as a micro seller (ID and selfie only). Try "Licensed professional" to see the PRC ID and PTR requirements.

Registry verification instead of certificate uploads

DTI and SEC certificates are never uploaded. The applicant types a registration number, the format is validated, and a mocked registry integration confirms the record, the owner, and the industry risk. Questions the registry can answer are never asked.

Try it: Use the registry numbers in the table above. Note that a verified sole proprietor is never asked the signatory question, since the registration is under their own name.

Tier downgrade mid-flow

Applicants who do not want to gather documents can drop to Tier 1 Starter and keep only the ID and selfie checklist.

Try it: Start as Tier 2 or 3, and when the document checklist appears, use the downgrade chip (or say you do not want to upload documents).

Real document uploads

Images and PDFs up to 10MB are stored and shown to reviewers.

Try it: Upload any image or PDF when asked. Then find your application in the admin panel and click the thumbnail: it zooms to a lightbox, Escape closes it.

E-signature by confirmation

The final Confirm button is the electronic signature. No drawn signature is collected.

Try it: Finish the flow and press Confirm. The summary card records the signed time and a confirmation email is sent.

Email notifications

Confirmation email on signing, an automatic reminder 15 minutes after an application stalls, decision emails on approve or deny, and manual emails from the admin. Every email carries a button that reopens the application, and opens are tracked with a pixel.

Try it: Sign an application and check the outbox. Leave one unfinished for 15 minutes and the reminder appears on its own. Note: this demo can only deliver real email to the account owner's inbox; every other address is recorded in the outbox instead, which is the intended place to verify content.

Admin panel

Roster of every application with status, tier, document progress, and registry result. Each row opens a detail page with the application, registry record, document previews, eligibility checks, and full email history with open status.

Try it: Open /admin, click your applicant, review the cards, then approve or deny. The decision emails the applicant, and the chat announces the decision the next time they resume.

Manual admin emails with compliance templates

Reviewers can email an applicant directly. Four premade templates (clearer document, missing documents, signatory confirmation, details mismatch) prefill the composer and stay editable.

Try it: On an applicant's detail page, click a template chip, adjust the wording, send, and see it appear in the email history. Check the outbox to read it as the applicant would.

Full-screen portal mode

A hidden second presentation of the same flow, one question per screen.

Try it: Answer the very first question (your first name) with the word "full" and watch the transition.

Known demo limits

Questions or bugs: note the applicant email you used and what you expected, then send them to the team.