Payment Gateway Hub

The problem

Dynamics 365 Finance & Operations ships with a payment services framework, but in practice every processor you actually need is a separate build. A call centre order needs an authorisation against a stored card token. An e-commerce channel posts a capture that has to land as a customer payment journal line. A regional processor in the Gulf, South Asia or Latin America wants a signed hash, a redirect page and an asynchronous callback that F&O has no listener for. Finance then reconciles the processor's settlement file against CustTrans by hand, because nothing in the box maps a gateway payout to the individual invoices it settled.

The result is familiar: authorisations captured in a portal but never posted, payments applied to the wrong legal entity, refunds issued in the gateway that AR never sees, and a month-end where the clearing account never clears. Each new processor repeats the same X++ work from scratch.

What ECOSIRE builds

We build a single gateway abstraction inside F&O — one contract, many processors — as X++ extensions with no overlayering. Adding your next processor becomes a configuration and a small adapter class, not another integration project.

Gateway abstraction layer

A processor-agnostic interface handles authorise, capture, void, refund and tokenise. Each processor you name in scoping gets its own adapter class implementing that interface, registered through an extensible enum and a factory so the calling code never branches on processor. Endpoint URLs, merchant identifiers, currency support and per-entity credentials live in a parameters table keyed by legal entity and payment method, so a group running several DataArea values can route each entity to its own merchant account.

Secure credential and token handling

Secrets are held outside the transactional tables — Azure Key Vault references resolved at runtime, or the platform's encrypted storage where Key Vault is not available in your environment. Card data is never persisted in F&O: the app stores processor tokens only, linked to the customer record so call centre and recurring billing can re-use them without re-entering a PAN.

AR settlement that actually closes

A captured payment creates a customer payment journal line and settles it against the target invoice or sales order through the standard settlement engine, honouring LedgerDimension defaulting, cash discount rules and the posting profile you configure. Gateway fees post to a separate ledger account with their own financial dimensions. Refunds reverse through the same path so credit notes and processor refunds stay in step.

Callbacks and asynchronous notifications

Most processors confirm asynchronously. We expose a custom service endpoint (SOAP or REST over the standard service framework) that receives webhooks, verifies the processor signature, writes to a staging table and hands processing to a batch job. Nothing posts on the inbound HTTP thread, so a slow ledger posting can never time out a webhook and cause the processor to retry into a duplicate payment. Duplicate callbacks are idempotent on the processor reference.

Batch processing and retries

A SysOperation-based batch job polls pending authorisations, retries transient failures with backoff, expires stale authorisations before the processor does, and imports settlement or payout files. Batch jobs are recurrence-configurable per legal entity and log every attempt.

Reconciliation workbench

A form matches processor settlement lines against F&O payment transactions on processor reference, amount and date, flags unmatched rows, and lets a clerk post the difference to a configured variance account with a reason code. Everything is exposed as data entities so the same matching can be driven from the Data management framework or an external tool over OData.

Integration points

Authorisation is available from the sales order, the call centre order entry form, the free text invoice and the customer payment journal. Where you use Dual-write or Power Platform, the payment status and token references are surfaced as entities so a Power App or portal can display them without a second integration.

Who it is for

Organisations already live on or implementing Dynamics 365 Finance and Supply Chain Management that take card, wallet or local processor payments and want them settled in AR rather than reconciled in a spreadsheet. It suits multi-entity groups with different merchant accounts per country, call centre and B2C operations, and finance teams carrying a large unreconciled clearing balance.

How delivery works

Everything ECOSIRE ships is built to order. Nothing here is a shelf product you download and install today.

1. Scoping call. We go through your processors, the API documentation for each, your legal entity and merchant account structure, the posting profiles and dimensions you want used, and your F&O version and update cadence. 2. Fixed quote. You receive a written scope with the exact processors, forms, entities, batch jobs and posting behaviour included, a fixed price and a delivery date. The listed price is the baseline for a typical two-processor build; the quote reflects your actual scope. 3. Build. Development runs in our environment against your target platform update, as X++ extensions in a dedicated model with no overlayering. You get progress checkpoints, not a black box. 4. Install in test. We deliver a deployable package for your LCS/sandbox pipeline and support the install in your UAT or test environment. We walk your team through configuration and run the processor sandbox credentials end to end with you. 5. Production. Once you sign off UAT, the same package goes through your normal release pipeline to production. We are on the call for the first live transactions. 6. Support. A defined support window covers defect fixes and assistance with the platform update that follows go-live.

What we do not claim

We are not a payment processor and we do not hold your funds. PCI scope reduction depends on using hosted fields or a redirect flow at your processor — we will tell you plainly which of your chosen processors allow that and which do not. We are not affiliated with, endorsed by, or certified by Microsoft or any payment processor.