Questions about a step? Contact support.
This guide shows you how to set up and navigate the ePay extension — Dynamics eShop’s all-in-one payment solution for Dynamics 365 Business Central. ePay provides PCI-compliant payment processing integrated with the CardConnect and Authorize.net payment gateways.
ePay can be used to manually authorize or charge funds for orders, and to automate customer payment at different stages of the ordering process. From inside Business Central you can manage customer payment profiles, decide when and how incoming orders are charged, and keep accurate cash receipt journals for every transaction. If ePay was purchased alongside Dynamics eShop’s B2B/B2C ecommerce solutions, ePay and its sub-products — eShop Pay, Bill Pay and Email Pay — can take much of the payment processing burden off Sales and Accounts Receivable.
📋 How to use this guide
Dynamics eShop operates a licensing system across all its products, including ePay. If your license is found to be invalid or expired you may lose access to the ePay extension and its functionality inside Business Central and on any connected ecommerce sites.
Follow these steps to gather the information Dynamics eShop needs in order to activate your ePay license.
1) In Business Central, select the ? help icon. In the Help pane on the right, choose Help & Support, then select Inspect pages and data from the Help & Support menu.
2) When the Page Inspection pane loads on the right, select the search icon, then find and open Companies. Highlight the Business Central company you will be using ePay in, and copy the full Id from the Page Inspection pane.
3) Send the details for your deployment type to support@dynamicseshop.com or your Dynamics eShop project manager:
| Deployment | What to send |
|---|---|
| Cloud Business Central | Your organization’s Microsoft Azure tenant ID, the Business Central environment name, and the Business Central company Id. |
| On-premises Business Central | The Business Central server address and the Business Central company name/Id where ePay will be used. |
⚠️ Wait for confirmation
Dynamics eShop support or your project manager will respond once your subscription has been activated. Continue to the next section only after that confirmation.
⚠️ Permissions required
To install an extension, the user must be a member of the D365 Extension MGT user group or hold the EXTEND. MGT. – ADMIN permission set.
1) At the top of Business Central, select the search icon, then find and open Extension Marketplace.
2) Use the search bar to find the ePay Credit Card & ACH Payments extension published by Dynamics eShop Inc. Select Free trial on the AppSource page, then again in the pop-up.
⚠️ This step interrupts other users
Installing the extension forces Business Central users to close the pages and reports they are working on and redirects them to the home page. Schedule it accordingly.
3) Select Install to begin. When installation finishes you receive a confirmation message and a prompt to refresh Business Central.
4) Select the search bar and type “ePay License” until you can choose ePay License Registry.
5) On the ePay License Registry screen, select Get Active Licenses.
📝 Expired license?
If your license has expired, contact support@dynamicseshop.com or your Dynamics eShop project manager.
Once ePay is installed and licensed, permission sets control how Business Central users interact with it. The three sets are listed below from highest to lowest privilege:
| Permission set | What it allows |
|---|---|
| ESHOP-EPAY PS | Can edit the ePay Setup card and perform every other ePay process. |
| ESHOP-EPAY EDIT PS | Can manage ePay profiles, authorize, charge and void. Cannot edit the ePay setup. |
| ESHOP-EPAY READ PS | Read-only access to ePay tables such as profiles and transactions. |
📝 Administrator task
The steps below should be completed by a Business Central administrator.
1) Search for Users and select a user name to open the User Card.
2) Scroll to the User Permission Sets table and add the relevant ePay permission set.
3) Specify the Business Central company the permission applies to, or leave it blank to apply it across the entire environment.
The following Business Central roles can view the ePay Dashboard, which gives a quick reference for ePay profiles and credit card authorizations that are expiring or expired:
| Role | Role | Role |
|---|---|---|
| Accountant | Accounting Manager | Accounts Payable Coordinator |
| Accounts Receivable Administrator | Outsourced Accounting Manager | Sales Order Processor |
| Sales and Relationship Manager | Sales Manager | Finance (FIN) |
| IT Manager | System Admin | Inventory Manager |
| Warehouse | Warehouse Worker | Shipping & Receiving |
Two ePay Dashboard tiles are updated by a job queue that polls the connected payment gateway:
| Tile | What it shows |
|---|---|
| Expired Credit Cards | Selecting the tile opens a filtered view of expired ePay profiles. |
| Expired Authorizations | Selecting the tile opens the authorizations that have expired. |
Contact accounting@dynamicseshop.com about obtaining the merchant application for your new payment gateway. In your email, include your company name and the email address of the person who will sign the application.
Once the merchant process has started, work with the gateway and Dynamics eShop to complete the application and get the account live.
With the merchant account live, generate the integration credentials that connect the payment gateway to Business Central.
| Value | Where it is used in ePay |
|---|---|
| MID | Identifies the merchant account. |
| Username | Entered as the API Token on the ePay Setup card. |
| Password | Entered as the API Key on the ePay Setup card. |
| URL | https://fts.cardconnect.com |
⚠️ Keep these credentials secure
This information populates the ePay Setup card in the next section. Treat it as sensitive and store it securely.
| Value | Where it is used in ePay |
|---|---|
| API Login ID | Entered as the Identifier ID and the API Token. |
| Transaction Key | Entered as the API Key. |
| URL | https://api.authorize.net/xml/v1/request.api |
In Business Central, search for “ePay” and confirm that ePay Setup appears, then open it.
These fields establish the connection between the ePay extension in Business Central and your payment gateway. Dynamics eShop can provide test credentials until your merchant application has been processed successfully.
⚠️ Switching from test to live
Once merchant onboarding is complete, confirm the correct gateway is selected — transaction reference numbers and token IDs are generated differently in CardConnect/CardPointe than in Authorize.net. The URL, API Token and API Key fields also change to your live credentials rather than the generic testing values. Retrieve the live values from your merchant portal as described in section 5.3 or 5.4, and contact support@dynamicseshop.com if you are unsure.
| Field Name | Functionality |
|---|---|
| General > GateWay | Selects the corresponding merchant provider. |
| Identifier ID | Unique ID identifying you to the gateway. |
| URL | The URL needed to connect to the gateway. |
| API Token | The token for the API integration. |
| API Key | The key for the API integration. |
Credit card fields
ACH fields
With the fields configured, select Test Connection in the top bar and choose Credit Card or ACH depending on what your business uses.
📝 Expected result
You should see a Success response from the payment gateway. If the test connection fails, contact your IT department or the ePay team.
| Field Name | Functionality |
|---|---|
| Convenience/Additional Processing Fee | Sets whether a convenience fee applies. Credit card only. Can be a percentage or a flat amount, depending on the adjacent Is Percentage toggle. |
| Payment Journal Batch, Sales Journal Template, Sales Journal Batch for CC/ACH | Required for automations such as automatic posting to cash receipt journals and general ledgering of payment information. Your accounting team or Business Central partner will typically set these up so they fit your existing sales and accounting workflows. |
Credit card functional settings
ACH functional settings
Below the General, Credit Card and ACH settings you will find the Automation section. These settings determine at what point in an order ePay attempts to authorize or charge funds, and whether customers receive an email receipt.
Because different business models call for different transaction timing, enable only the automations that match your sales and accounting workflow.
📋 Payment profile hierarchy
These automations require an ePay-enabled Payment Method Code on the order, and use the following hierarchy of payment profiles when attempting to authorize or charge funds:
📝 Missing prerequisites
If the Payment Method Code is invalid or missing, or none of the payment profile options can be satisfied, ePay displays a detailed error message identifying which fields need input before the enabled automations can proceed.
| Field Name | Functionality |
|---|---|
| Auto Authorize while Release | Automatically authorizes sales orders with ePay on release. See section 9.2. |
| Auto Capture while Posting | Automatically captures funds when a sales order or invoice is posted with ePay. See section 10.2. |
| Auto Close Invoice with Email Pay | Automatically closes an invoice in Email Pay — a paid add-on to the standard ePay product. Contact sales@dynamicseshop.com for details. |
| Retrieve Transaction while Release Only | Retrieves the transaction into Business Central while the order is being released. If cleared, the transaction is retrieved while validating the Your Ref Number instead. Recommended off. |
| Enable E-Mail Receipts | Should be off during initial implementation and testing. Automatically emails receipts to customers when funds are captured. Requires an email account to be set up in Business Central. |
| Cash Receipts Enabled | Automatically creates cash receipts in the cash receipts journal when funds are captured. Pairs with Post Cash Rcpts While Capture. |
| Post Cash Rcpts While Capture | Automatically posts cash receipt journal lines while funds are being captured. Pairs with Cash Receipts Enabled. |
| Re-Auth & Capture While Shipping Partially | Allows orders to be partially shipped and paid for with ePay. Orders are re-authorized and captured for the partial amount when they ship. |
These fields are specific to Email Pay, a paid add-on to the standard ePay extension. To add an Email Pay license to your current ePay solution, contact sales@dynamicseshop.com. See the separate Email Pay user guide for details of how ePay can be extended to send automated payment request emails and accept payment through a secure link.
| Field Name | Functionality |
|---|---|
| E-Mail Pay URL | The URL provided by eShop to connect to the Email Pay service. |
| Invoice Email Pay Request Template | Selects a different template for posted sales invoices that have not passed their due date. |
| Order Email Pay Template | Selects a different template for sales orders. |
| Invoice Email Pay Attachment Template | Selects a different report layout to attach to payment requests sent on posted sales invoices. |
| Overdue Email Pay Template | Selects a different template for posted sales invoices past their due date. |
| Order Email Pay Attachment Template | Selects a different report layout to attach to payment requests sent on sales orders. |
| Duration For Payment Reminders | The time in days that must elapse before another payment request is sent. |
| Default Send-to-Email | Selects whether a payment request goes to the Bill-To email on the customer card or the email on the posted sales invoice. |
| First Payment Request based on Due Date | The number of days before or after the invoice due date that the first payment request is sent. |
Marking a payment method as ePay Payment Method enabled allows ePay functionality to work on sales orders using that payment method’s code.
⚠️ Orders without an ePay payment method
Any sales order with a payment method code that is not ePay-enabled has no access to ePay functionality. This restriction does not apply to posted sales invoices — an invoice works with ePay regardless of payment method code, relying instead on whether the customer has a valid ePay profile.
📝 Recommendation
Use an ePay-enabled payment method on customer accounts that are not on terms, so the automation can confirm you have a card on file when processing a sales order.
ePay payment methods also have optional automations that stack on top of the setup card automations covered in section 6.3, further ensuring orders are authorized or paid before each fulfilment milestone.
1) In Business Central, search for “Payment Method” and select Payment Methods.
2) Select the ePay Payment Method box for every payment method that will be used with ePay, and confirm the changes were saved in the top right.
3) For payments that require authorization before release, enable ePay Requires Auth Before Release. See the example in section 9.5.
4) To ensure funds are fully captured when items leave your warehouse, enable ePay Auto Captures while Shipping for the payment method used on the order. You can also enable ePay Requires Capture to Post Shipment to verify funds are captured before a warehouse shipment can be posted. See the example in section 9.4.
| Field Name | Functionality |
|---|---|
| ePay Payment Method | Makes the payment method ePay-applicable. When enabled, all ePay functionality is available for orders using this payment method code. |
| ePay Requires Authorization before Release | Requires funds to be authorized before any shipment of product is released. Requires ePay Payment Method first. |
| ePay Auto Captures while Shipping | Automatically captures funds (authorizing first if necessary) when a warehouse shipment is posted for a sales order. ePay follows the payment profile hierarchy described in section 6.3, and displays an error if none of those options can be used. Requires ePay Payment Method first. |
| ePay Requires Capture to Post Shipment | Checks that funds were captured successfully before the warehouse shipment can be posted — a safeguard against shipping unpaid items. Requires ePay Auto Captures while Shipping first. |
📝 Gateway differences
The example below is for CardPointe. Other merchant gateways may look different.
For credit cards: complete the required information and save.
For ACH: enable the ACH button, complete the required information and save.
📝 Default profiles
If Default was enabled, that payment profile becomes the default for payments on that customer.
ePay Profile List fields
| Field Name | Functionality |
|---|---|
| Default | A visual check showing which profile is set as default. |
| Profile ID | The corresponding ID from the payment gateway. |
| Identifier ID | The merchant code from the payment gateway. |
| Account ID | Differentiates between multiple profiles on one customer. |
| Type | The payment type — credit card or ACH. |
| Account No | Stores only the last four digits of the card. |
| Token | The unique token associated with the card details stored in the payment gateway. |
Profile card actions
| Action | Functionality |
|---|---|
| New | Creates a new ePay customer profile with the information entered. |
| Update Profile | Updates the customer profile card. |
| Transactions | Shows the transactions associated with that profile card. |
| Make Default | Makes the profile card the default. |
| Remove Default | Removes the profile card as the default. |
| Delete Profile | Deletes the ePay profile. |
1) Navigate to the customer’s ePay profiles.
2) Select the profile you want as the default and choose Make Default. Verify that the profile now has a checked default box.
3) To remove a profile as the default, select it and choose Remove Default. Verify that the default box is no longer checked.
Besides the default profile, you can have a specific customer profile used by automations on a single order by setting an ePay Account Reference on that sales order. That profile is then used for the remainder of the process.
⚠️ Credit card only
ACH does not allow authorization at the sales order level. ACH funds can only be captured at the posted sales invoice level.
📝 Convenience fee
The convenience fee configured on the ePay Setup card is applied and added to the total amount. The fee remains editable for flexibility.
Payment card fields
| Field Name | Functionality |
|---|---|
| Total Amount | The sales order total plus the convenience fee. |
| Convenience/Additional | The convenience fee from the ePay Setup card, applied to the sales order total. |
| Select Existing Profile | Selects a saved customer payment profile — see section 8.1. |
| New Card/ACH Details | Details for a new card or ACH account. Selecting Save Profile stores them as a new customer payment profile. |
⚠️ Credit card only
As with manual authorization, ACH cannot be authorized at the sales order level.
1) Search for ePay and select ePay Setup.
2) Under Automation, enable Auto Authorize while Release.
📝 Interaction with payment method settings
If ePay Requires Auth before Release is enabled on the payment method, authorization is still required before any release. That authorization can happen automatically when Auto Authorize while Release is on and the customer has a default profile.
3) Release an order to have it authorize automatically. Make sure the customer has a default profile for the authorization to use.
📝 Warehousing varies
Step 3 may differ depending on your organization’s Business Central warehousing process. The instructions above follow the standard process; what matters is that the result is a posted sales shipment.
⚠️ Void before reauthorizing
You must have completed an authorization first (section 9.1 or 9.2). Selecting Authorize without voiding the existing authorization produces a warning message.
📋 Automatic reauthorization
If ePay Requires Authorization Before Release is enabled on the payment method used for the order, ePay attempts to reauthorize automatically using this hierarchy:
📝 Voiding
To void an authorized transaction, see section 14.1.
If ePay returns any response code other than successful, the details the payment gateway provides about the card issue are saved to the ePay Transaction List.
The unfiltered ePay Transaction List can be opened from the search button anywhere in Business Central. While you are on a sales order or posted sales invoice, the transactions for that specific document are available under ePay → Transactions in the action bar.
Sales orders may or may not have been authorized already — funds can be captured either way. To check whether an order was authorized before it is invoiced, open the ePay Transactions list, which shows whether the order has been authorized and captured.
⚠️ Authorization may be required first
If ePay Requires Authorization before Release is enabled for the payment method and no authorization exists, an error appears stating that authorization is needed. Authorize the sales order to proceed.
📝 Result
The posted sales invoice is now processed, and closed if Cash Receipts Enabled and Post Cash Rcpts While Capture are on. Funds are authorized and captured.
This method requires Auto Capture while Posting to be enabled in the Automation section of the ePay Setup card (see section 6.3).
📝 Invoice closure
If Cash Receipts Enabled and Post Cash Rcpts While Capture are on in the ePay Setup card, the sales invoice is closed automatically.
📝 Scope
This section applies only to posted sales invoices whose funds have not already been authorized and captured.
📝 Refunds
To refund an authorized and captured transaction, see section 14.2.
📝 Automatic authorization
If Auto Authorize while Release is enabled on the ePay Setup card and a payment method code is selected, step 3 is already done. Verify by selecting ePay → Transactions.
📝 Scope
This applies only to posted service invoices whose funds have not already been authorized and captured.
📝 Verifying the result
The journal lines are posted and the customer’s account balance reflects the payment. Check the customer card — the balance should show the change, and ePay → Transactions displays the record.
⚠️ Captured funds cannot be voided
If the authorization line has already been captured, the funds can no longer be voided and must be refunded instead — see section 14.2.
📝 Reauthorizing afterwards
To reauthorize the sales order after voiding, see section 9.5.
📝 Effect on posted sales invoices
If the refund was on a posted sales invoice with Cash Receipts Enabled, an opposing cash receipt entry is posted and the invoice is left open to be captured and closed again — see section 9.3 or 11.
📝 Effect on posted sales invoices
On a posted sales invoice, an opposing refund cash receipt entry is posted against the payment and the invoice is left open to be captured and closed again — see section 9.3 or 11.
📝 Need help?
For support or questions specific to your ePay implementation, contact support@dynamicseshop.com or your Dynamics eShop project manager.