A native AL extension that brings Stripe card, ACH and wallet payments into Business Central sales documents — pay-by-link, capture, refunds and automatic payout reconciliation, built and installed for your tenant by ECOSIRE. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $249.00 USD; request a quote for a scoped proposal.
App manifest
Built around your workflow
A native AL extension that brings Stripe card, ACH and wallet payments into Business Central sales documents — pay-by-link, capture, refunds and automatic payout reconciliation, built and installed for your tenant by ECOSIRE.
No DIY setup — a working app, built, installed and supported by ECOSIRE.
Start with a one-time build price. We scope it with you at kickoff.
ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.
You go live in about 2–4 weeks, with a post-launch support window.
Business Central has no native card or ACH acquiring. Your AR team still chases payments by email, keys card numbers into a separate Stripe Dashboard, and hand-matches payouts against open customer ledger entries at month end. The Stripe Payments Connector for Business Central closes that gap by embedding Stripe directly into the documents your finance team already lives in.
This is a build-to-order app, not a one-click AppSource download. ECOSIRE engineers the connector as a per-tenant AL extension, installs it on your Business Central Online (or on-prem) environment, configures your Stripe account and webhooks, and supports it afterward. You get code shaped to your posting setup, payment terms and chart of accounts — not a generic shrink-wrap app you have to bend your process around.
Once live, your team can authorize and capture card, ACH and Apple/Google Pay payments from a page extension on the Sales Order and Posted Sales Invoice. Posting an invoice can auto-generate a pay-by-link that emails the customer a hosted Stripe checkout. When Stripe settles a payout, a job queue entry pulls the balance transactions via the Stripe API and applies them against the matching customer ledger entries, then stages the bank reconciliation. Refunds and partial refunds initiated in BC post back as the correct detailed ledger and application entries.
Card data never touches Business Central. We store only Stripe tokens and customer/payment-method IDs in extension tables, keeping your card-handling scope at PCI-DSS SAQ-A. Permission sets, telemetry and AL event subscribers are built to Microsoft's extension guidelines so the app survives BC's automatic upgrade cycles.
Owns the cash-application and month-end close. Wants Stripe receipts applied to customer ledger entries and payouts reconciled automatically instead of hand-matching a CSV from the Stripe Dashboard.
Wants customers to self-serve card and ACH payments via a pay-by-link on every invoice, without buying a separate payment portal or exposing the business to PCI scope.
Responsible for the tenant's extensions and upgrade safety. Needs a clean per-tenant AL extension with proper permission sets, isolated-storage secrets and telemetry — not unmanaged customizations that break on the next update wave.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Native card / ACH acceptance inside BC sales documents | Included | Included | Included | |
| Automatic payout-to-ledger reconciliation via job queue | Included | Partial support | Partial support | |
| Built and tuned to your posting setup and chart of accounts | Included | Included | Not included | |
| Installed and supported for you (no self-implementation) | Included | Not included | Partial support | |
| PCI-DSS SAQ-A tokenized vault (no PAN in BC) | Included | Partial support | Included | |
| Per-tenant AL extension that survives BC update waves | Included | Partial support | Included | |
| Pay-by-link emailed automatically on posted invoices | Included | Partial support | Partial support | |
| Predictable one-time cost with no per-seat licensing | Included | Not included | Not included |
No. This is a build-to-order extension. ECOSIRE builds the AL app for your specific posting setup and chart of accounts, then installs it as a per-tenant extension on your Business Central environment. You are not buying a generic listing from Microsoft AppSource — you are buying a connector engineered, deployed and supported for your tenant.
Typical lead time is about 2 to 4 weeks from kickoff, depending on the scope of your Stripe configuration, currencies and reconciliation rules. After a short requirements call we confirm a firm date. The build includes test-mode validation against your Stripe account before we switch you to live mode.
Delivery includes a post-launch support window for fixes and questions. We also offer an optional maintenance plan that keeps the extension compatible with Microsoft's twice-yearly Business Central releases and Stripe API version changes, and covers monitoring of the reconciliation job queue and webhook handler.
No card numbers (PANs) are ever stored in BC. The connector uses Stripe's tokenized, hosted payment flows and stores only Stripe customer, payment-method and PaymentIntent identifiers in extension tables. This keeps your card-handling scope at PCI-DSS SAQ-A. API keys are held in isolated storage, not in plain fields.
Yes. Full and partial refunds initiated in BC post back as the correct detailed customer ledger and application entries. ACH (US bank debit) and Apple/Google Pay wallets are supported alongside cards through Stripe. The connector maps Stripe presentment currencies to your BC currency codes and posts realized FX correctly on multi-currency receipts.
A native AL extension that brings Stripe card, ACH and wallet payments into Business Central sales documents — pay-by-link, capture, refunds and automatic payout reconciliation, built and installed for your tenant by ECOSIRE.