Payment Fraud Screening & 3DS2 for Business Central

Recursos Principais

Rules-based fraud scoring evaluating AVS match, CVV result, transaction amount, geo/IP signals and ship-to mismatch, with per-rule weights stored in a configurable Fraud Rule table extension

Velocity rules that count transactions and value over rolling windows keyed by card hash, email, IP address and ship-to address to catch carding and rapid-fire attempts

3-D Secure 2 / SCA challenge orchestration against your acquirer or PSP, recording the authentication outcome, ECI and liability-shift status on the sales/payment document

Manual Risk Review Queue — an AL list page where held orders are approved, rejected or escalated, with reviewer, timestamp and reason captured in an audit log table

Blocklist and allowlist management (card BIN, email domain, IP range, country) enforced via event subscribers before the order is released or the payment is posted

Configurable risk thresholds that route each transaction to approve / review / block, adjustable per company without code changes

Chargeback and dispute tracking table linking each dispute to the originating transaction, its fraud score and the approving rule for post-mortem analysis

Event subscribers on Sales Order Release and payment posting codeunits so screening runs in the standard BC flow with no parallel process to maintain

Dedicated permission set (read/score vs. review/override) so finance and fraud-ops roles are separated under BC's standard permission model

Job Queue entry for batch re-scoring and for auto-expiring stale held orders so the review queue never silently grows

BC REST/OData API pages exposing scores, queue items and disputes for external SIEM, Power BI or a PSP reconciliation feed

Optional Dataverse / Power Platform surfacing so a fraud-ops dashboard or Power Automate alert can sit on top of the same data

Telemetry to Application Insights (when enabled) for score distribution, block rate and challenge success rate

Localization-aware: respects your country extension and currency, and SCA enforcement is scoped to in-region/in-scope transactions you define

Feito sob encomenda, pronto para você

Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.

Você faz o pedido

Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.

Nós criamos e instalamos

A ECOSIRE cria, configura e instala no seu Dynamics 365 Business Central.

No ar + suporte

Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.

Sobre este Produto

Card-not-present fraud and strong customer authentication (SCA) mandates put two pressures on Business Central merchants at once: stop fraudulent orders before they ship, and prove that in-scope transactions were authenticated under PSD2/3-D Secure 2. Business Central core has no fraud engine and no 3DS2 orchestration — it records the payment your gateway returns and nothing more.

Payment Fraud Screening & 3DS2 for Business Central is a per-tenant AL extension that ECOSIRE builds, installs and supports on your environment (SaaS or on-prem). It is not an instant AppSource download — we scope it to your gateway, your risk appetite and your localization, then deploy it as a versioned extension into your tenant.

The extension subscribes to the payment-posting and sales-order release events, scores each card-not-present transaction against configurable rules (AVS match, CVV result, velocity by card/email/IP/ship-to, amount and geo signals), and either approves, holds for manual review, or blocks. For in-scope payments it orchestrates a 3DS2 / SCA challenge against your acquirer or PSP and records the authentication outcome and liability-shift status on the document. A Risk Review Queue page lets your team release, reject or whitelist held orders with a full audit trail, and a Chargeback/Dispute log links disputes back to the original transaction and the score that approved it.

Everything ships as AL table, page and codeunit extensions with a dedicated permission set, configurable rule tables, and optional Power Platform / Dataverse surfacing for fraud dashboards. You own the source and the tenant; we handle the build, the install and ongoing support.

O que você ganha

A per-tenant Business Central extension (.app) built in AL, version-controlled, installed into your sandbox then production environment by ECOSIRE

Source code for the AL project (table/page/codeunit extensions, event subscribers, permission set) handed to you under the agreed license

Configured fraud rule set, velocity windows and risk thresholds matched to your gateway/PSP and risk appetite during onboarding

3DS2 / SCA integration wired to your specific acquirer or payment service provider, including outcome and liability-shift capture

Permission sets and a short admin guide covering the Risk Review Queue, blocklist/allowlist and threshold configuration

OData/REST API endpoints (and optional Dataverse mapping) documented for your BI, SIEM or Power Platform consumers

Deployment notes, an upgrade/compatibility plan against Microsoft's BC release cadence, and a post-go-live support handover

Para quem é isso

E-commerce / card-not-present merchant on BC

Sells online or over the phone through Business Central and is seeing rising chargebacks. Wants automated screening and a review queue so fraud-ops can act before orders ship, without bolting on a separate system.

Finance / compliance lead facing SCA mandates

Needs to demonstrate that in-scope card payments are authenticated under PSD2 / 3-D Secure 2 and that liability shift is recorded. Wants enforcement and an audit trail living inside BC, not in a spreadsheet.

BC administrator or implementation partner

Owns the tenant and wants a clean, supportable per-tenant extension using standard AL patterns, dedicated permission sets and event subscribers — not unmaintainable customizations or risky base-app changes.

Como Payment Fraud Screening & 3DS2 for Business Central se compara

Critério	ECOSIRE	Construção personalizada	Concorrente
Rules-based fraud scoring (AVS/CVV/velocity) inside BC	Incluído	Suporte parcial	Suporte parcial
3-D Secure 2 / SCA challenge orchestration wired to your PSP	Incluído	Suporte parcial	Suporte parcial
Manual review queue with audit trail and role separation	Incluído	Suporte parcial	Suporte parcial
Chargeback/dispute tracking linked to the approving score	Incluído	Suporte parcial	Não incluído
Built, installed per-tenant and supported on your environment	Incluído	Suporte parcial	Não incluído
Tuned to your gateway, risk appetite and localization	Incluído	Incluído	Não incluído
You own the source and the extension	Incluído	Incluído	Não incluído
Available as instant self-service download	Não incluído	Não incluído	Incluído

Perguntas frequentes sobre Payment Fraud Screening & 3DS2 for Business Central

How long does delivery take, and how is it installed?

Typical build-to-order delivery is about 2–4 weeks from scoping sign-off, depending on your gateway/PSP and how many fraud and velocity rules you need. We build the extension, validate it in your sandbox tenant, then install it as a versioned per-tenant AL extension into production. There is no AppSource download — ECOSIRE handles the build and the install on your environment.

Do you provide ongoing support and updates after go-live?

Yes. We provide a support handover at go-live and offer ongoing maintenance covering rule tuning, bug fixes, and compatibility upgrades against Microsoft's Business Central release cadence (major updates roughly twice a year). Because you hold the source and own the tenant, you can also self-maintain or move support in-house at any time.

Which gateways and 3DS2 providers do you support?

The extension is built to your specific acquirer or payment service provider. The 3DS2 / SCA orchestration and fraud-signal mapping (AVS/CVV results, ECI, liability shift) are wired to that provider during the build, since signal formats differ between PSPs. Tell us your gateway during scoping and we confirm fit before any work starts.

Will this modify the base application or affect upgrades?

No base-app changes. It ships as table, page and codeunit extensions with event subscribers, which is the supported AL pattern for both BC SaaS and on-prem. That keeps your tenant upgradeable; we include an upgrade/compatibility plan and re-test the extension against new BC releases as part of support.

Can the fraud scores and review queue feed external tools like Power BI or a SIEM?

Yes. We expose scores, review-queue items and disputes through BC's REST/OData API pages, and can optionally surface the same data into Dataverse for Power BI dashboards, Power Automate alerts, or a feed into your SIEM and PSP reconciliation process.