Payment Feeds
+£45/moper month, per providerStripe, GoCardless, PayPal or your bank feed — receipts auto-allocated, payouts and refunds reconciled, payment runs pushed back out.
Card, direct-debit and bank payments land in Sage against the right invoices automatically — no month-end import spreadsheets, no unreconciled clearing accounts swelling every week. Processors push events by webhook; high-street banks come in through polled Open Banking feeds. And it's two-way: payment links, statements and remittances go out to customers, while BACS payment runs and AUDDIS mandate instructions submit straight to the bank.
Try It
Stripe
Payment succeeded
pi_3f2a
Acme Supplies Ltd · INV-2214
£842.00
Sage Connector API
sage.yourcompany.com
POST /api/payments/allocateSage 50 Accounts
Payment allocated · invoice marked paid
Written to Sage · 3.8s after Stripe event
What syncs
Two-way: payments land in Sage auto-allocated; payment links and remittances push back out.
Activity — Stripe ⇄ Sage
How It Works
- 1
Events stream in
Processors (Stripe, GoCardless, PayPal, Starling) fire webhooks; banks like Barclays and Lloyds feed via polled Open Banking or host-to-host channels — the connector normalises both into payment events.
- 2
Posted correctly, every time
Successful payments allocate to invoices; failed payments flag for dunning without posting; refunds allocate to credit notes; payouts post net of fees so the bank rec still works.
- 3
Feeds stay scoped
Allocations, refunds, fees & payouts, bank feeds, mandates and remittances are independently toggleable per connection — sync only what you want.
- 4
Sage pushes back out
Payment links, reminders, statements and remittance advice go out to customers. On bank connections, approved supplier payment runs submit as BACS files and new DD mandates go out as AUDDIS instructions.
What's Included
- One payment provider or bank feed connected
- Automatic receipt allocation against matched invoices
- Fee separation and payout-to-bank reconciliation
- Refund, failed-payment and dispute handling
- Outbound: payment links, reminders, statements, remittances
- Bank connections: BACS payment runs and AUDDIS mandate submission
- Unmatched-payment queue surfaced in the portal
Who It's For
Businesses taking card, direct-debit or bank payments whose bookkeeping team currently posts receipts manually, reconciles from processor payout reports, or hand-builds BACS files for supplier runs.
FAQ
Which providers?
Stripe, GoCardless and PayPal via webhooks; Starling via its feed-item webhooks; high-street banks (Barclays, Lloyds and others) via polled Open Banking feeds — same outcome, different plumbing. Opayo and other processors on request.
What if a payment can't be matched?
It lands in an unmatched queue in the portal — staff assign it to an invoice in two clicks, it never silently disappears.
Do bank feeds need re-authorising?
Open Banking consent renews every 90 days — the portal prompts before expiry, and the feed keeps catching anything it missed on reconnect.
You can actually submit payments to the bank?
Yes — approved supplier payment runs submit as BACS files and DD mandate changes go out as AUDDIS instructions, via your Bacs bureau or host-to-host channel. Execution still needs your bank-side approval, so nothing pays out without a human release.
Add Payment Feeds to Your Package
Pick a tier, tick this add-on and get a fixed quote.