Article type: How-to
Audience: Paystand merchants and their IT administrators setting up or maintaining the Microsoft Dynamics 365 Business Central integration
Last reviewed: June 18, 2026
__________________________________________________
Overview
Paystand connects to Business Central using a Microsoft Entra ID (formerly Azure AD) app registration. That registration uses a client secret so Paystand can authenticate to the Business Central API on your behalf.
This article covers:
- Creating or rotating the client secret in Microsoft Entra ID (Azure portal)
- Pasting that secret into the Client Value field in the Paystand Dashboard
Important terminology
- In Azure, copy the Value column — this is the client secret.
- Do not copy the Secret ID — that identifier is not used for authentication.
- In the Paystand Dashboard, this same value goes in the field labeled Client Value.
__________________________________________________
Before you begin
You will need:
- Azure access with permission to manage app registrations (typically Application Administrator or Global Administrator)
- An existing Paystand app registration named Paystand (created during initial Business Central setup)
- Access to the merchant Paystand Dashboard with permission to manage integrations
- The Application (client) ID from the same Azure app registration (for the Client ID field in Paystand)
If you are setting up Business Central for the first time, complete the full installation guide before this article. This article focuses only on Certificates & secrets and updating the secret in Paystand.
__________________________________________________
Part 1 — Create or rotate the client secret in Microsoft Entra ID
These steps follow current Microsoft guidance for app registration client secrets.
Step 1: Open the Paystand app registration
- Sign in to the Azure portal or Microsoft Entra admin center.
- In the top search bar, type App registrations and open it.
- Open the Paystand application registration.
If you manage multiple tenants, confirm you are in the correct Microsoft Entra tenant before continuing.
- In the left menu under Manage, select Certificates & secrets.
- Select the Client secrets tab.
__________________________________________________
Step 2: Start a new client secret
- Click + New client secret.
Microsoft notes that certificates are more secure than client secrets for production workloads. Paystand’s current Business Central integration is configured to use a client secret in the Client Value field.
__________________________________________________
Step 3: Configure the secret
In the Add a client secret pane:
| Field | Recommended value |
| Description | Paystand secret (or another name your team will recognize) |
| Expires | 730 days (24 months) or your organization’s preferred rotation period |
Microsoft currently offers expiration options such as 180 days, 365 days, 730 days (24 months), or a custom date.
- Click Add.
__________________________________________________
Step 4: Copy the secret Value immediately
After you click Add, Azure displays the new secret in the Client secrets table.
- Locate the row you just created.
- In the Value column, click the Copy to clipboard icon.
- Save the copied value in a secure location (for example, your company password manager).
Critical: Azure shows the full secret Value only once. If you leave the page without copying it, you cannot retrieve it later. You will need to create a new secret.
Do not copy the Secret ID. The Secret ID is an internal reference for the secret record. Paystand requires the Value, not the Secret ID.
__________________________________________________
Step 5: Plan for expiration
Client secrets expire on the date you selected. Before expiration:
- Create a new client secret in Azure (repeat Part 1).
- Update the Client Value in the Paystand Dashboard (Part 2).
- After confirming the integration works, delete the old expired secret in Azure.
If a secret expires without being rotated, the Business Central connection in Paystand will stop working until a new secret is saved in the dashboard.
__________________________________________________
Part 2 — Enter the secret in the Paystand Dashboard
After copying the Azure secret Value, add or update it in Paystand.
Step 1: Open the Business Central integration
- Sign in to the merchant Paystand Dashboard.
- In the left navigation menu, go to Integrations.
- If a submenu appears, select Integrations again.
- Scroll to Microsoft Dynamics 365 Business Central in the integrations list.
__________________________________________________
Step 2: Expand the connection form
- Under Business Central, confirm the integration status (Connected or Inactive).
- Click Connect To Business Central to expand the connection form.
The expanded form shows fields for Environment, Company Name, Tenant Name, bank account IDs, GL accounts, Client ID, and Client Value.
__________________________________________________
Step 3: Paste the secret into Client Value
In the connection form:
- Confirm Client ID contains the Azure Application (client) ID from the Paystand app registration Overview page.
- In Client Value, paste the secret Value you copied from Azure in Part 1, Step 4.
The Paystand field is labeled Client Value, not “Client Secret.” It stores the Azure client secret value.
- Review the other required fields if this is a new connection or if any Business Central settings changed:
- Environment
- Company Name
- Tenant Name
- Paystand Bank Account ID in Business Central
- Merchant Bank Account ID in Business Central
- GL accounts (Fees, Discounts, Convenience Fees, Adjustments, Disputes, Refunds)
Security note: For security reasons, Paystand does not display a previously saved Client Value when you reopen the form. To rotate a secret on an existing connection, paste the new secret value and save again.
__________________________________________________
Step 4: Save the connection
- Click Connect To Business Central.
- Wait for the confirmation message: Connected to Business Central.
- Confirm the status changes to Connected.
If you see an authentication error, verify:
- You copied the Value, not the Secret ID
- Client ID matches the Azure Application (client) ID
- The secret has not expired
- You pasted the full value with no extra spaces
__________________________________________________
Troubleshooting
| Symptom | Likely cause | What to do |
| Invalid client secret provided / authentication failure | Wrong value copied, truncated value, or expired secret | Create a new secret in Azure, copy the full Value, paste into Client Value, and reconnect |
| Connection worked before but stopped | Secret expired | Check the Expires date in Azure Certificates & secrets, create a new secret, update Paystand |
| Secret ID was pasted instead of Value | Common mix-up between Azure columns | Use the Value column only |
| Client Value appears blank on reopen | Expected security behavior | Paste the current or new secret again when rotating |
| Cannot find App registrations | Insufficient Azure role | Ask an Application Administrator or Global Administrator to perform Part 1 |
__________________________________________________
References
Paystand internal source (implementation guide):
- Installation Guide for Business Central — Certificate and Secrets
Microsoft official documentation (validated June 2026):
- Register a Microsoft Entra app and create a service principal — Create a new client secret
- Use client secrets with Microsoft.Identity.Web — Create a client secret in the Azure portal
- Manage secret expiration and rotation
Azure portals: