Apple Pay & Google Pay Wallet Checkout for Business Central

Name: Apple Pay & Google Pay Wallet Checkout for Business Central
Brand: ECOSIRE
SKU: d365bc-wallet-checkout-applepay-googlepay

主な機能

Apple Pay and Google Pay buttons rendered on Business Central hosted pay pages and the customer self-service portal

Automated Apple Pay merchant domain verification (apple-developer-merchantid-domain-association hosting) and Google Pay merchant onboarding setup

Tokenized one-tap checkout — wallet payment tokens are passed to your gateway; no raw PAN ever touches Business Central

Gateway-agnostic design via an AL processor abstraction so the same extension works across multiple payment gateways

AL table and page extensions storing wallet method, token reference, and settlement status against the Sales Invoice and Payment Registration

Event subscribers on posting and payment-registration codeunits to auto-apply wallet payments to the customer ledger entry

Job queue entry that reconciles wallet settlements and webhook callbacks back into Business Central on a schedule

BC REST/OData API endpoints to generate, dispatch, and track pay-links for email, SMS, or QR delivery

Mobile-optimized hosted pay pages with full RTL/LTR rendering for Arabic, Hebrew, and Latin-script storefronts

Least-privilege permission sets for finance and portal roles, installable per-tenant without admin over-grant

Optional Dataverse / Power Platform integration so Power BI and Power Automate can react to wallet payment events

Configurable button styling, supported networks, and per-currency enablement from a Business Central setup page

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Dynamics 365 Business Central 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

Apple Pay & Google Pay Wallet Checkout is a build-to-order Microsoft Dynamics 365 Business Central extension that brings one-tap mobile wallet payments to the pay-links and customer portal your B2C/D2C buyers already use. It is not an instant AppSource download. ECOSIRE builds it in AL, installs it as a per-tenant extension on your specific Business Central environment (cloud SaaS or on-prem), and supports it after go-live.

On a phone, a card form is friction. Apple Pay and Google Pay collapse that into a single biometric tap, and that lift is exactly where D2C carts are won or abandoned. This extension surfaces both wallet buttons on your hosted pay pages, runs the Apple Pay merchant domain verification and Google Pay merchant setup for you, and processes the resulting payment token through your existing gateway — so it works across multiple processors rather than locking you to one.

Under the hood we add table and page extensions to carry wallet and tokenization state, event subscribers on the posted/open Sales Invoice and payment-registration flow, and a job queue entry to reconcile wallet settlements back to the customer ledger. Payment links are exposed over the BC REST/OData API and the hosted pages are mobile-first with full RTL/LTR support for Arabic and Hebrew storefronts. Permission sets ship scoped to least privilege, and optional Dataverse / Power Platform sync lets Power BI or a Power Automate flow react to wallet payments.

You get a real codebase, a real install on your tenant, and a named ECOSIRE engineer for the warranty period. Scope, gateway choice, and any portal branding are confirmed before we start so the delivered build matches your environment exactly.

得られるもの

A per-tenant Business Central AL extension (.app) built to your scoped requirements, installed on your environment

Apple Pay merchant domain verification completed and Google Pay merchant profile configured against your domain

Gateway connector wired to your chosen processor with tokenized wallet payment capture

Configured BC setup page, permission sets, and job queue entry for settlement reconciliation

Hosted pay-page templates with your branding, mobile-optimized and RTL/LTR ready

Optional Dataverse table mapping and a sample Power Automate flow when Power Platform integration is in scope

Deployment to sandbox first, UAT sign-off, then production install with rollback notes

Admin and finance-team handover documentation plus a post-go-live support and warranty window

これは誰のためのものですか

D2C / B2C Merchant Owner

Runs a direct-to-consumer brand on Business Central and sees mobile carts stall at the card form. Wants Apple Pay and Google Pay to turn checkout into a single tap and recover abandoned mobile sales.

Finance / AR Manager

Owns accounts receivable and reconciliation. Needs wallet payments to auto-apply to the correct customer ledger entry and settle cleanly, without a parallel spreadsheet or manual matching after every payout.

IT / Business Central Administrator

Responsible for the tenant. Wants a clean per-tenant extension with scoped permission sets, sandbox-first deployment, and no risky AppSource app of unknown provenance touching the production environment.

Apple Pay & Google Pay Wallet Checkout for Business Central の比較方法

基準	エコシエール	カスタムビルド	競合他社
Apple Pay & Google Pay one-tap buttons on BC pay pages	付属	部分的なサポート	部分的なサポート
Apple Pay domain verification & Google Pay setup done for you	付属	含まれていない	含まれていない
Tokenized checkout — no raw PAN in Business Central	付属	部分的なサポート	付属
Works across multiple gateways (processor-agnostic)	付属	部分的なサポート	含まれていない
Installed as a per-tenant extension on your environment	付属	付属	含まれていない
Built, tested, and supported against your actual tenant	付属	部分的なサポート	含まれていない
Settlement auto-reconciled to customer ledger via job queue	付属	部分的なサポート	部分的なサポート
RTL/LTR mobile-optimized hosted pay pages	付属	部分的なサポート	部分的なサポート
Optional Dataverse / Power Platform event integration	付属	部分的なサポート	含まれていない

Apple Pay & Google Pay Wallet Checkout for Business Central に関するよくある質問

Is this an AppSource app I can install instantly?

No. This is a build-to-order extension. ECOSIRE writes it in AL for your specific environment, then installs it as a per-tenant extension on your Business Central tenant (or on-prem deployment). There is no instant marketplace download — the value is that the build, the Apple Pay domain verification, the Google Pay setup, and the gateway wiring are all done and tested against your actual environment.

What is the delivery lead time?

A standard single-gateway build is typically delivered in about 2 to 4 weeks from scope sign-off. The first week confirms scope, gateway, and pay-page branding; the build and sandbox install follow; then UAT and the production install. Multiple gateways, custom portal work, or Dataverse / Power Platform integration extend the timeline, and we confirm the exact schedule in writing before starting.

How does ongoing support and updates work after go-live?

Every build includes a post-go-live warranty window covered by a named ECOSIRE engineer for defect fixes. Beyond that, we offer an optional support retainer covering Business Central major-version compatibility (the AL extension is revalidated against each new BC release), gateway API changes, Apple Pay / Google Pay requirement updates, and enhancements. You always own the source for your build.

Will it work with my existing payment gateway?

In most cases yes. The extension uses an AL processor abstraction so the wallet token can be routed to your existing gateway rather than forcing a switch. During scoping we confirm your gateway supports Apple Pay and Google Pay tokenized transactions and build the connector accordingly. If a gateway is named in your seed scope, we target it directly.

Does Business Central store card or wallet card numbers?

No. Checkout is fully tokenized. Apple Pay and Google Pay return a payment token that is passed to your gateway for authorization — the raw card number never reaches Business Central. BC stores only a token reference and settlement status on the invoice, which keeps your PCI scope minimal.

Can wallet payments flow into Power BI or trigger automations?

Yes, when Power Platform integration is in scope. We can map wallet payment events to a Dataverse table so Power BI dashboards report on wallet-vs-card mix, and a Power Automate flow can react to each payment — for example notifying fulfillment or posting to a channel. This is optional and quoted as part of scoping.