Os detalhes do produto são exibidos em inglês. Traduções em breve.
Fatos rápidos
- Preço
- $299.00 USD
- Versões dynamics_365_business_central
- —
- Tempo de configuração
- 30 min
- Licença
- Uma vez perpétua
- Idiomas
- 11 idiomas
Compra Única
Stored Cards & PCI Token Vault for Business Central
A gateway-agnostic tokenization layer that stores customer cards on file in Business Central with zero PAN data, reducing PCI scope to SAQ-A and enabling one-click rebill on recurring orders.
$299.00USD
Sem pagamento agora. Isto envia um pedido de orçamento à nossa equipe — responderemos por e-mail com preços e próximos passos.
Recursos Principais
Multi-gateway tokenized card-on-file — captures cards via the gateway's hosted fields/iframe so the PAN goes browser-to-gateway and only an opaque token is stored in BC
New `Customer Card Token` table + Customer Card page extension storing token, brand, last-four, and expiry only — never the full card number or CVV
SAQ-A PCI scope reduction: no cardholder data transits or persists in Business Central, SQL, or the BC filestore
Account Updater integration — subscribes to the gateway's updater API/webhook to refresh tokens for expired and reissued cards automatically
Default payment method per customer, surfaced on the Customer Card and consumed by Sales Order processing
One-click rebill on recurring orders — charge the stored token directly from a posted/recurring Sales Order action
Job Queue entry for unattended subscription/recurring billing runs against stored tokens
Gateway-connector interface implemented via AL interfaces + event subscribers so a second processor can be added without rearchitecting
Dedicated permission sets restricting who can charge, vault, or delete a stored card; tokenization actions written to the BC Change Log
BC REST/OData API exposure of the tokenized payment-method endpoints for your webshop, portal, or Power Platform flows
Optional Dataverse / Power Automate integration to trigger rebills and surface card-on-file status in Power Apps
Webhook handler (AL HTTP endpoint or Azure Function relay) for asynchronous gateway events: settlement, decline, chargeback, updater notices
Idempotent charge handling so a retried Job Queue run never double-bills a stored card
Telemetry to Application Insights for charge success/decline rates and updater coverage
Sobre este Produto
Storing customer cards on file inside Dynamics 365 Business Central is the difference between a smooth repeat-order flow and a customer who re-keys their card every time. The wrong way to do it drags your entire BC tenant — and every user who touches a Sales Order — into PCI DSS scope. This extension does it the right way: no Primary Account Number (PAN) ever touches Business Central or its SQL storage.
Por Que Escolher Stored Cards & PCI Token Vault for Business Central
Multi-gateway tokenized card-on-file — captures cards via the gateway's hosted fields/iframe so the PAN goes browser-to-gateway and only an opaque token is stored in BC
New `Customer Card Token` table + Customer Card page extension storing token, brand, last-four, and expiry only — never the full card number or CVV
SAQ-A PCI scope reduction: no cardholder data transits or persists in Business Central, SQL, or the BC filestore
Account Updater integration — subscribes to the gateway's updater API/webhook to refresh tokens for expired and reissued cards automatically
Default payment method per customer, surfaced on the Customer Card and consumed by Sales Order processing
One-click rebill on recurring orders — charge the stored token directly from a posted/recurring Sales Order action
ECOSIRE builds this as a per-tenant AL extension installed directly on your Business Central environment (cloud SaaS or on-prem). The card is captured client-side via your payment gateway's hosted fields / iframe, the gateway returns a token, and only that opaque token, the card brand, last-four, and expiry are persisted in a new Customer Card Token table linked to the Customer. Because the cardholder data flows browser-to-gateway and never transits your servers, your card-on-file process can qualify for the lightest PCI self-assessment, SAQ-A.
The extension is gateway-agnostic by design. We implement a thin gateway-connector interface (event-subscriber based) and wire it to the processor you already use — Stripe, Authorize.Net, Adyen, Braintree, Cybersource, or a regional acquirer — using their tokenization and Account Updater APIs. A default payment method per customer drives one-click rebill from recurring Sales Orders and from a Job Queue entry for subscription billing.
This is build-to-order, not an instant AppSource download. We scope your gateway, your customer/order flow and your compliance posture, then build, install, and support the extension on your tenant. Lead time is honest and stated below. After go-live, ECOSIRE owns updates, BC version compatibility, and gateway API changes under a support agreement — so Account Updater keeps working when cards expire and reissue.
O que você ganha
- A per-tenant AL extension (.app) built for your Business Central version, installed on your sandbox then production environment
- Gateway connector wired to your chosen processor (Stripe / Authorize.Net / Adyen / Braintree / Cybersource / regional acquirer) using its tokenization + Account Updater APIs
- `Customer Card Token` table, Customer Card page extension, and the default-payment-method UI
- Permission sets for vault/charge/delete actions plus Change Log configuration for the tokenization audit trail
- Job Queue setup for recurring/subscription rebilling and the Account Updater refresh run
- BC REST/OData endpoints (and optional Dataverse flow) for headless or Power Platform consumption
- Source code, AL project, and a compatibility note documenting which BC version the extension targets
- Admin + end-user documentation covering the card-on-file flow, PCI SAQ-A posture, and rebill operations
Para quem é isso
Subscription & recurring-revenue merchant
Sells repeat or subscription products and wants to rebill stored cards automatically each cycle from a Job Queue instead of chasing customers for payment details every period.
Finance / compliance owner
Accountable for PCI DSS posture and wants card-on-file without pulling the whole BC tenant into scope — the no-PAN, SAQ-A architecture is the deciding factor.
Operations / customer-service lead
Processes repeat orders manually in BC and wants a one-click charge against the customer's default stored card to cut order-entry time and re-keyed-card errors.
Visão geral da instalação
Baixe do ECOSIRE
Compre a licença em ecosire.com e baixe o ZIP do módulo Stored Cards & PCI Token Vault for Business Central no painel da sua conta.
Carregar para Odoo
Extraia o ZIP em sua pasta de complementos personalizados do Odoo no servidor (ou faça upload via Aplicativos > Instalar do arquivo em Odoo.sh/runbot).
Instale o módulo
Ative o modo de desenvolvedor, abra Aplicativos, clique em Atualizar lista de aplicativos, procure por Stored Cards & PCI Token Vault for Business Central e pressione Instalar.
Definir configurações
Abra o novo menu, cole sua chave de licença ECOSIRE, conecte quaisquer credenciais externas (Shopify, Amazon, Stripe, etc.) e salve.
Verifique e entre no ar
Execute o teste de conexão integrado, sincronize seus primeiros 10 registros e agende o cron recorrente. Entre em contato com o suporte se algo falhar.
Como Stored Cards & PCI Token Vault for Business Central se compara
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| No PAN stored in Business Central (SAQ-A scope reduction) | ||||
| Gateway-agnostic connector (swap/add processors without rearchitecting) | ||||
| Account Updater for expired/reissued cards | ||||
| One-click rebill + Job Queue recurring billing on stored tokens | ||||
| Built, installed and supported on your tenant (BC version-compat updates owned) | ||||
| Permission sets + Change Log audit trail for vault/charge/delete actions | ||||
| Tailored to your exact customer/order flow and compliance posture |
Perguntas frequentes sobre Stored Cards & PCI Token Vault for Business Central
+How long does delivery take, and what is the process?
This is build-to-order, not an instant AppSource install. After a short scoping call we confirm your gateway, customer/order flow, and compliance posture, then build the extension. Typical lead time is 2–4 weeks depending on gateway complexity and whether Account Updater and recurring Job Queue billing are in scope. We install on your Business Central sandbox first for UAT and sign-off, then deploy the per-tenant extension to production with a supported go-live.
+What ongoing support and updates do I get after go-live?
ECOSIRE owns the extension after launch under a support agreement. That covers Business Central version-compatibility updates (so the .app keeps installing through BC's continuous release cadence), changes to your gateway's tokenization or Account Updater API, bug fixes, and reasonable enhancements. Because cards expire and reissue constantly, keeping Account Updater working is part of support rather than a one-off.
+Does any actual card number get stored in Business Central?
No. The card is captured client-side through the gateway's hosted fields or iframe, so the PAN goes from the customer's browser straight to the gateway and never transits your servers. Business Central stores only the gateway token, card brand, last-four, and expiry. This is what allows the card-on-file process to qualify for the lightest PCI self-assessment, SAQ-A.
+Which payment gateways are supported?
The extension is gateway-agnostic. We implement a connector interface and wire it to the processor you already use — Stripe, Authorize.Net, Adyen, Braintree, Cybersource, or a regional acquirer — provided it exposes a tokenization API. Account Updater support depends on your gateway offering that feature; we confirm this during scoping.
+Is this an AppSource app I can just download?
No. It is built and installed as a per-tenant AL extension specifically for your environment, gateway, and order flow. That is deliberate: tokenization, PCI scope, and recurring-billing logic differ per merchant, and a per-tenant extension lets us fit your exact setup rather than ship a one-size-fits-all listing. ECOSIRE installs and supports it directly on your tenant.
+How does one-click rebill on recurring orders work?
Each customer has a default payment method backed by a stored token. From a recurring or repeat Sales Order, an action charges that token directly through the gateway connector. For unattended subscription billing, a Job Queue entry runs the charges on schedule with idempotent handling so a retried run never double-bills the same order.
Por que os clientes confiam na ECOSIRE
SOC 2 alinhado
Compatível com GDPR
Pagamento Stripe Seguro
Devolução do dinheiro em 30 dias
Atualizações vitalícias
Licença LGPL-3.0
Módulos Relacionados
Solicitar orçamento
Stored Cards & PCI Token Vault for Business Central
A gateway-agnostic tokenization layer that stores customer cards on file in Business Central with zero PAN data, reducing PCI scope to SAQ-A and enabling one-click rebill on recurring orders.
- Multi-gateway tokenized card-on-file — captures cards via the gateway's hosted fields/iframe so the PAN goes browser-to-gateway and only an opaque token is stored in BC
- New `Customer Card Token` table + Customer Card page extension storing token, brand, last-four, and expiry only — never the full card number or CVV
- SAQ-A PCI scope reduction: no cardholder data transits or persists in Business Central, SQL, or the BC filestore
- Account Updater integration — subscribes to the gateway's updater API/webhook to refresh tokens for expired and reissued cards automatically