SYS-PAYOnDraft

Service 07

Pay Now on a page you own,

then Xero is told once.

Xero can send the customer to a payment URL you control. OnDraft drafts that page, takes the card payment, and records it on the invoice — duplicate-safe, with a run you can query.

Problem

Pay Now on a Xero invoice opens a processor page the customer does not recognise. Finance then types the card settlement back into Xero, or waits for a bank feed, while operations still does not know it is paid.

System

Xero Payment Services send the customer to an OnDraft page with invoice placeholders. Stripe collects the card. OnDraft posts the payment to the Xero invoice with a stable external id so retries do not double-apply. Process runs are recorded.

Outcome

The invoice is paid in Xero from the page the customer used. Brand stays with the business. The existing Xero → Logistaas path can fire from the same cash fact.

A Xero invoice is yours. The Pay Now button often is not — it dumps the customer onto Stripe, GoCardless or PayPal chrome that does not look like the business that just billed them.

Xero Payment Services let you register a custom URL. Placeholders carry invoice number, amount and currency. The customer lands on a page drafted for the organisation: who is being paid, what the invoice is, what happens next.

Collection is the other half of the payment story OnDraft already ships the operations way. Once Xero has the receipt, the existing enrich → duplicate-check → write pattern can tell Logistaas (or the next operational system) without a person typing it.

How the page runs

  1. 1

    Pay Now in Xero

    The invoice carries a custom payment service. The customer clicks Pay Now and lands on your URL with invoice, amount and currency.

  2. 2

    Branded payment page

    The page shows who is being paid and what is owed. Card details go to Stripe — not to Xero, and not to a second set of books.

  3. 3

    Write back to Xero

    OnDraft posts the payment onto the invoice. If the invoice is already paid, that is treated as success — the same idempotent stance as our Logistaas serials.

  4. 4

    Operations can follow

    Xero now holds cash truth. The shipped payment.received path can enrich, duplicate-check and notify Logistaas when that destination is in scope.

Try the Flow Designer

Demo mode. The sample is Xero payment received → Logistaas create payment → finish. Add nodes, connect them, oropen the full designer. Nothing here talks to your Xero organisation.

Loading the Flow Designer…

Drag nodes, connect a payment path, then talk to us. Demo mode only.

What this system includes

  • Custom Pay Now URL registered against the Xero organisation via Payment Services
  • Branded hosted page: invoice, amount, currency, and who is being paid
  • Card collection through Stripe — not a second ledger
  • Duplicate-safe payment write back to the Xero invoice
  • Recorded process run; optional hand-off into the shipped Xero → Logistaas path

Collect

Customers pay on a page that looks like the business that invoiced them — not a generic processor splash screen.

Close

The Xero invoice moves to paid from the payment event. Nobody retypes a receipt into the ledger.

Continue

Once cash is in Xero, operational systems can consume the same payment through the flow we already run.

Supporting detail

Related systems

Questions about this system

Is this a Xero App Store product?

No. This site does not claim a marketplace listing or Xero partner badge. We register a Payment Service on your Xero organisation and build the page around that tenant.

Do you replace Stripe or GoCardless?

Card collection uses Stripe. Xero remains the invoice and payment authority. We are not asking you to move the ledger.

How does this relate to Xero → Logistaas?

Payment pages collect cash into Xero. The Logistaas flow starts after Xero already has the payment. They are two sides of the same event: collect, then tell operations.

Is this already a one-click connector?

No. We scope the Xero organisation, the Stripe account, the page, and which invoices should offer Pay Now. The engineering pattern — placeholders in, duplicate-safe write, recorded run — is the same class of work we already ship.

Is the first custom integration free?

Yes — one scoped join, agreed on a discovery call. Typical shape: Xero payment received into an operations write. It is not a rewrite of the whole estate. Open the Flow Designer demo, then talk to us.

Do you publish prices?

Not a public rate card. The first scoped custom integration is free; everything else is scoped on a call.

We build systems that power growth.

AI agents, integrations and operational software—built around your business.