Stripe Payment Connector for Business Central

Key Features

Page extension on Sales Invoice and Posted Sales Invoice to generate a Stripe Payment Link or Checkout Session per document, with the URL emailed or embedded in the BC document layout

Acceptance of cards, digital wallets (Apple Pay / Google Pay), and bank debits (ACH, SEPA, Bacs) according to what is enabled on your Stripe account

Inbound Stripe webhook handling via an AL API page (or Azure Function relay for restricted networks) with signature verification and idempotent event processing

Automatic payment registration and application to the originating Sales Invoice via the Cash Receipt / Gen. Journal posting routines — no manual receipt entry

Job Queue entry that polls the Stripe Payouts and Balance Transactions API and reconciles each payout to a Bank Account Ledger Entry

Automatic split of gross charges and Stripe processing fees into separate, configurable G/L accounts so net deposits always tie out

Refund processing initiated from the Customer Ledger Entry or Posted Sales Invoice, pushed to Stripe via API and posted back to BC

Subscription / recurring billing mirrored from Stripe into BC recurring sales documents and renewal schedules

Multi-currency aware: Stripe presentment currency mapped to BC currency codes with exchange-rate handling on settlement

API secret keys and webhook signing secrets held in Isolated Storage, surfaced only through a permission-set-gated Setup page

Dimension, number-series, and posting-group aware so payment entries match your existing financial reporting structure

Optional Dataverse / Power Platform virtual-table sync exposing payment and payout status to Power BI and model-driven apps

Dedicated Stripe Payments role with a tailored BC permission set so only authorized users can configure keys or trigger refunds

Reconciliation log page and telemetry signals (Application Insights) for every webhook, payout poll, and refund for auditability

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

The Stripe Payment Connector for Business Central is a build-to-order AL extension that closes the gap between how your customers pay (Stripe) and how your finance team books revenue (Business Central). It is not an instant AppSource download. ECOSIRE builds it to your chart of accounts, currencies, and posting rules, then installs it as a per-tenant extension on your Business Central SaaS or on-premises environment and supports it after go-live.

On the sales side, the extension adds a page extension to the Sales Invoice and Posted Sales Invoice that generates a Stripe Payment Link or Checkout Session per document. Customers pay by card, digital wallet (Apple Pay / Google Pay), or bank debit (ACH, SEPA, Bacs where enabled on your Stripe account). When the payment succeeds, a Stripe webhook is received by an AL API page (or an Azure Function relay where firewall rules require it), matched to the originating document, and the Payment is registered and applied — no manual cash-receipt entry.

On the back-office side, a Job Queue entry polls the Stripe Balance Transactions and Payouts API on a schedule you choose. Each payout is reconciled to a Bank Account Ledger line, gross charges and Stripe processing fees are split into the correct G/L accounts, and refunds initiated from the Customer Ledger Entry card are pushed to Stripe and posted back. Subscription and recurring billing schedules can be mirrored from Stripe into recurring sales documents.

Everything respects Business Central permission sets, dimensions, and number series. API keys are stored in Isolated Storage, never in plain tables. Optional Dataverse/Power Platform sync exposes payment status to Power BI and model-driven apps. You receive the source AL, a deployment runbook, and a defined support window.

What you get

A per-tenant Business Central AL extension (.app) built to your environment, version-pinned to your BC release

Full AL source code (table/page extensions, API pages, event subscribers, Job Queue codeunits) handed over in a Git repository

Deployment runbook covering extension installation, Stripe API/webhook configuration, and Job Queue scheduling

A configured Stripe Payments permission set and role, plus a Setup page for keys, accounts, and posting mappings

Sandbox installation and a joint test pass (test-mode Stripe keys) before production go-live

Administrator and end-user handover documentation plus a recorded walkthrough

A defined post-go-live support and bug-fix window with an agreed response SLA

Who this is for

SMB Finance Manager

Owns month-end close and wants Stripe payouts, fees, and refunds to land in the right G/L accounts automatically instead of being keyed from CSV exports.

E-commerce / Operations Lead

Sends invoices from Business Central and needs a one-click pay-now link so customers can settle by card or wallet without leaving an email.

Business Central Administrator / Partner

Responsible for the BC tenant and needs a clean per-tenant extension with proper permission sets, Isolated Storage for secrets, and source code they can audit and maintain.

How Stripe Payment Connector for Business Central Compares

Criterion	ECOSIRE	Custom Build	Competitor
Stripe payments fully embedded in Business Central (no external portal)	Included	Partial support	Partial support
Automatic payout & processing-fee reconciliation to the correct G/L accounts	Included	Partial support	Partial support
Built to your chart of accounts, dimensions, and posting rules	Included	Included	Not included
Full AL source code handed over for you to own and audit	Included	Included	Not included
Installed per-tenant and supported on your environment by the vendor	Included	Partial support	Partial support
Refunds and recurring/subscription billing driven from BC	Included	Partial support	Partial support
Secrets in Isolated Storage with a dedicated permission set	Included	Partial support	Partial support
Fixed one-time build cost with a defined delivery timeline	Included	Not included	Partial support

Frequently Asked Questions about Stripe Payment Connector for Business Central

Is this a download from Microsoft AppSource?

No. This is a build-to-order extension. ECOSIRE builds it against your specific Business Central version, chart of accounts, currencies, and posting rules, then installs it as a per-tenant extension on your environment. There is no instant AppSource listing to download.

What is the typical delivery lead time?

A standard build runs about 2 to 4 weeks from kickoff: requirements and Stripe account review, then development in a sandbox, a joint test pass with Stripe test keys, and production go-live. Heavily customized posting logic, recurring-billing scenarios, or Dataverse sync can extend this — we confirm the timeline in writing before starting.

How are ongoing support and updates handled?

Every build includes a defined post-go-live support window for bug fixes at the agreed response SLA. Because Business Central ships major updates twice a year, we offer ongoing maintenance to recompile and retest the extension against new BC releases and adapt to Stripe API changes. Maintenance terms are quoted separately from the one-time build.

Where are my Stripe API keys stored, and is it secure?

Secret keys and the webhook signing secret are stored in Business Central Isolated Storage, never in plain tables or in source. Access to the Setup page is gated by a dedicated permission set, webhook payloads are signature-verified, and every webhook, payout poll, and refund is logged for audit. We use Stripe test keys throughout the sandbox phase.

Can it handle multi-currency, refunds, and recurring billing?

Yes. The connector maps Stripe presentment currencies to your BC currency codes with exchange-rate handling on settlement, lets you issue refunds directly from the Customer Ledger Entry or Posted Sales Invoice (pushed to Stripe and posted back), and can mirror Stripe subscriptions into BC recurring sales documents. Available payment methods depend on what is enabled on your Stripe account.