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.
Service 07
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.
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.
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.
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.
The invoice carries a custom payment service. The customer clicks Pay Now and lands on your URL with invoice, amount and currency.
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.
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.
Xero now holds cash truth. The shipped payment.received path can enrich, duplicate-check and notify Logistaas when that destination is in scope.
Customers pay on a page that looks like the business that invoiced them — not a generic processor splash screen.
The Xero invoice moves to paid from the payment event. Nobody retypes a receipt into the ledger.
Once cash is in Xero, operational systems can consume the same payment through the flow we already run.
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.
Card collection uses Stripe. Xero remains the invoice and payment authority. We are not asking you to move the ledger.
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.
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.
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.
Not a public rate card. The first scoped custom integration is free; everything else is scoped on a call.
AI agents, integrations and operational software—built around your business.