PitchStation Invoices — The invoice that chases itself

Everything after "send"

Most tools make an invoice. This one finishes the job.

An invoice here isn't a PDF you email into the void — it's a live, tracked document with a lifecycle, a chase engine, and a paper trail.

Create four ways manual · description · contract · chat

Type it, describe it ("invoice Northbrook HK$12,000, NET 14"), upload the contract and bill a milestone, or chat it into shape. Zero-fabrication rule: AI never invents an amount.

Delivery that gates itself

Clients with an account get a sign-in link; everyone else gets link + password in the same email, rotating on every resend. You never manage invoice passwords.

You see "viewed"

The moment your client opens it, you know. No more "did you get my invoice?" — the open log answers it, with a 9-language viewer for global clients.

Reminders you never write

Due−3 · due day · +7 · +14 — polite, automatic, deduped, and they stop the second money arrives. Opt out per invoice; nudge manually anytime.

Numbers an auditor trusts

Gap-free registers assigned at send (INV-2026-0042). Drafts carry a DRAFT stamp; every send freezes a sha256 compliance snapshot of exactly what was issued.

Many identities, one account

Bill as multiple entities — each issuer has its own legal block, logo, and its own register (HK-…-0001 beside SG-…-0001). Built for platforms and groups.

Clients answer back

"I've paid ✓" claims (you confirm before they count), questions that land in your inbox with context, and receipts that close the thread professionally.

Corrections done right

Edits revise the same link; paid invoices lock; credit notes correct the record — and can refund the card payment in the same step.

Runs from your phone

Install /m/invoices — the badge counts what needs you now; a push lands the moment a client reports payment.

Getting paid

Card payment on the invoice — reconciled with no human touch

With collection enabled, a Pay now button appears on every payable invoice. Your client pays on a Stripe-hosted page; a cryptographically verified settlement flips the invoice to PAID, sends the receipt, and fires your webhook.

Exactly-once settlement — a replayed event can never double-record

Amount cross-checked — mismatches are held for review, never auto-booked

No card data ever touches PitchStation

Prefer your own rails? Bank / FPS 轉數快 / PayNow / QR / payment links render in "How to pay" — clients tap "I've paid", you confirm

Refunds ride credit notes — the paper and the money move together

Automatic reminders pulsing along a timeline until a milestone turns paid

Two platforms exchanging invoice documents over glowing data streams

For platforms & developers

The whole integration is one call

Idempotent by your order id, atomic (failure creates nothing), test-mode safe against production, with signed webhooks back so you never poll. Already collected the money elsewhere? Receipt mode issues the numbered PAID document in the same call.

# one secret · one call · delivered & being chased
curl -X POST https://www.pitchstation.ai/api/invoices \
  -H "Authorization: Bearer $PAT" \
  -d '{ "external_ref": "order-417", "send": true,
        "client_email": "ap@acme.com", "currency": "USD",
        "items": [{ "description": "Machines x3", "unit_cents": 250000, "qty": 3 }] }'
→ 201 { "number": "INV-2026-0031", "url": "https://…/s/…", "password": "…" }

Quickstart & error catalog OpenAPI 3 spec

Why it's safe to run your billing here

The paper trail is the feature

Provenance foreverEvery payment records who vouched: you, your client, or a signature-verified gateway. Auditors can always tell.

Frozen at sendIdentity + content snapshot (sha256) per send — renaming your company never rewrites an issued invoice.

Abuse-boundedDaily send caps and burst detection — a leaked API token can't become a phishing engine.

Test mode for realTEST-series invoices: no emails, permanent stamp, self-purging. Your CI hits production safely.

The invoice that delivers itself, chases itself, and proves itself