VILLACRUSIS LABS.

Case study · LEAD FRONTEND ENGINEER

US Finance SaaS: Invoicing and Stripe

Lead frontend on a US events-industry finance platform: full invoicing lifecycle, OTP-secured public views, Stripe card, ACH and debit with state fee rules.

Next.jsTypeScriptStripeACHSubscription billingMicrosoft login

The business and the problem

A US software company serves the events industry — venues, planners and vendors who invoice each other for deposits, balances and add-ons, often across state lines. Getting paid meant chasing PDFs and bank details by email. The company needed a full invoicing product: create, send, track, collect and reconcile, with payment methods that Americans actually use and fee rules that differ from state to state.

What was built

The invoicing lifecycle

Drafting, sending, reminders, partial payments, refunds and reconciliation, with a clear status at every step for both the sender and the payer.

Public invoice views without passwords

A payer receives a link, not a login. The page is protected by a one-time code sent to their email, so a forwarded link cannot be used by someone else, and the payer never has to create an account to pay.

Card, ACH and debit payments with state-specific fee rules

Stripe payments for cards, bank transfers (ACH) and debit. Some US states restrict how card surcharges may be passed on to the payer; the checkout applies the correct rule for the payer's state automatically and shows the fee before payment, so the business stays compliant without its staff needing to know the law.

Subscription billing with automatic enforcement

Customers pay for the software itself on a subscription. Plan limits and overdue states are enforced in the product automatically, so nobody has to switch a delinquent account off by hand.

Enterprise sign-in

Microsoft account sign-in for companies that require it.

What changed

Businesses that used to email PDFs and wait now send a link and get paid by card or bank transfer with the fee rules handled for them. The company's own subscription revenue is collected and enforced without manual work.

What this means for an SME project

If your business needs to collect payments online in the Philippines — deposits, balances, subscriptions — the same discipline applies: the payer should never need an account, the fee should be visible before the click, and GCash, Maya and cards should all work. This platform did that under stricter rules than a Philippine SME will face. Online payments are an add-on to a business website or part of a custom CRM or web app; NudgeNow runs GCash and Maya payments through PayMongo on exactly this pattern.

Stack

Next.js and TypeScript, Stripe for payments and subscriptions, Microsoft identity for enterprise sign-in.

Building something similar? Tell me about it.

Most SME projects are a fraction of this size, which is why they ship in weeks. The same care goes into a landing page as into a fintech platform.