Configure external gift card provider
Zenoti supports integration with external gift card providers to process gift card transactions through a third-party system. When you configure an external provider, gift card purchases, redemptions, balance checks, and refunds route through the provider instead of the native Zenoti gift card system. You can configure the integration at the organization level or at individual center levels.
Note: For conceptual background on how external providers work, see External gift card providers overview.
Audience: Organization administrators and managers who set up and manage external gift card provider integrations.
On this page
- Before you begin
- Supported providers
- Steps
- Navigate to the integration configuration
- Select a provider
- Enter the provider configuration
- Configure settlement details
- Configure bank account details (optional)
- Test the connection
- Save the configuration
- Configure at the center level
- Activate or change the active provider
- Void a provider
- Delete a provider configuration
- Integration behavior summary
- Tips
- Troubleshooting
- Related articles
Before you begin
Permission: Edit under GiftCards in the Loyalty Manager section — Required to configure external gift card provider settings.
- Obtain the provider credentials and connection details from your external gift card provider before you begin.
- Determine whether the integration applies to the entire organization or to specific centers only.
- Confirm with your provider which configuration values are required. For Blackhawk (DG), the organization-level fields are the API URL, API alias, username, and password; the center-level field is the store code only.
- If you plan to configure settlement, gather the settlement frequency, delay period, settlement type, start date, and readjustment percentage details from your provider.
- If you plan to configure Blackhawk (DG), third-party gift card integration must be enabled for your organization before you begin; the gift card provider configuration is available only when it is.
Important: External provider content applies only when Credit Pooling Service (CPS) integration is configured for your organization. Most organizations use native Zenoti gift cards and do not require this configuration.
Supported providers
Zenoti supports the following external gift card providers through the Credit Pooling Service (CPS).
| Provider | Description |
|---|---|
| SVS | SVS gift card processing. SVS manages the gift card balance, issuance, and redemption through its own platform. SVS integration is tablet-only — it is not supported on phone POS. Centers configured for SVS cannot sell Zenoti gift cards, and an SVS card must be the only item on the invoice. |
| ZenotiGiftCard | Zenoti's native gift card processing routed through the Credit Pooling Service. Use this option when you want centralized gift card management across multiple Zenoti organizations. |
| DG (Digital Glue / Blackhawk) | DG gift card processing. Requires third-party gift card integration to be enabled for your organization. This is the only confirmed third-party integration. |
Important: Zenoti supports only SVS, ZenotiGiftCard, and DG as external gift card providers. No other third-party providers are supported.
Steps
Navigate to the integration configuration
- Navigate to Configuration > Integrations > Gift Card Configuration.
- The gift card provider configuration page opens.
Select a provider
- On the configuration page, select the provider from the Provider dropdown.
- The configuration form updates to display the fields required for the selected provider.
Enter the provider configuration
Fill in the provider configuration fields. The exact fields depend on the provider you selected — confirm the required values with your provider.
For Blackhawk (DG) at the organization level, enter the following connection fields:
| Field | Description |
|---|---|
| API URL | Enter the API endpoint URL provided by Blackhawk. Zenoti connects to this endpoint for all gift card transactions. |
| API alias | Enter the API alias assigned by Blackhawk for your organization. |
| Username | Enter the authentication username assigned by the provider. |
| Password | Enter the authentication password assigned by the provider. |
Important: For Blackhawk (DG), the organization-level configuration requires only these four fields: API URL, API alias, username, and password. Do not enter WSDL URL, Merchant ID, Merchant Group ID, or Currency — these fields are not part of the current Blackhawk integration.
Tip: Field sets differ by provider. SVS and ZenotiGiftCard have their own connection field requirements. Confirm the exact fields with your provider before you begin.
Worked example: A Blackhawk-integrated organization might enter https://api.blackhawk-gc.example.com/v2 as the API URL, ACME_SALON_ALIAS as the API alias, and the username and password supplied in their Blackhawk onboarding documentation.
Configure settlement details
Settlement settings control how and when funds from gift card transactions are transferred between your organization and the provider. Not all providers support settlement configuration — confirm with your provider whether these fields apply.
| Field | Description |
|---|---|
| Settlement Frequency | Select how often settlements occur. Options depend on the provider and may include daily, weekly, or monthly. |
| Settlement Delay | Enter the number of days between a transaction and its settlement. |
| Settlement Type | Select the settlement method as specified by your provider. |
| Settlement Start Date | Enter the date from which settlement processing begins. |
| Readjustment Percentage | Enter the percentage used for readjustment calculations, if applicable. Your provider supplies this value based on your agreement terms. |
Configure bank account details (optional)
You can optionally enter bank account details to associate a bank account with the provider configuration.
| Field | Description |
|---|---|
| Account name | Enter the name on the bank account. |
| Account number | Enter the bank account number. |
| Routing number | Enter the bank routing number. |
| Bank name | Enter the name of the bank. |
Test the connection
Before you save the configuration, test the connection to verify that Zenoti can communicate with the provider.
- After you enter all required fields, click Test connection.
- The system attempts to connect to the provider using the credentials and URL you entered.
- If the test succeeds, a confirmation message appears. Proceed to save the configuration.
- If the test fails, verify the connection URL, credentials, and provider-specific details. Correct any errors and test again.
Note: A successful connection test confirms that the network connection and credentials are valid. It does not validate settlement or transaction processing.
Save the configuration
- After a successful connection test, click Save.
Note: The system stores the provider configuration for your organization and activates the provider via the active provider record.
Configure at the center level
By default, the provider configuration applies to the entire organization. You can override the configuration at the center level when specific centers use different provider credentials or settings.
- On the configuration page, switch the scope from Organization to Center.
- Select the center you want to configure.
- Enter the center-specific provider details. The center-level configuration uses fewer fields than the organization level. For Blackhawk (DG) at the center level, enter only the store code.
- Click Test connection to verify the center-level credentials.
- Click Save.
Note: When both organization-level and center-level configurations exist, the center-level configuration takes precedence for that center. All other centers use the organization-level configuration.
Activate or change the active provider
After you save the provider configuration, you must activate the provider for your organization.
- On the configuration page, locate the Active Provider section.
- Select the provider you want to activate from the list of configured providers.
- Click Save to set the selected provider as the active provider for gift card processing.
All new gift card transactions (purchases, redemptions, balance checks) route through the active provider after activation.
Note: Only one provider can be active at a time. Activating a new provider deactivates the previous one.
Void a provider
When you no longer use an external provider, you can void the configuration. Voiding disables the provider without deleting the configuration record.
- On the configuration page, locate the provider you want to void.
- Click Void.
- Confirm the action when prompted.
After you void a provider, no new transactions route through it. Existing gift cards processed through the voided provider remain in the system with their current balances.
Important: If you void the only active provider, the system reverts to native Zenoti gift card processing. Verify that your templates and center configurations are set up for native processing before you void.
Delete a provider configuration
To remove a provider configuration entirely:
- On the configuration page, locate the provider configuration you want to remove.
- Click Delete.
- Confirm the deletion when prompted.
Important: Deleting a provider configuration is permanent. Existing gift card transaction records are retained, but the provider connection settings are removed. You must re-enter all configuration details if you want to reconnect to the same provider in the future.
Integration behavior summary
| Scenario | Behavior |
|---|---|
| No external provider configured | All gift card operations use native Zenoti processing. |
| Organization-level provider active | All centers route gift card operations through the configured provider. |
| Center-level provider configured | The specified center routes operations through its center-level provider. Other centers use the organization-level provider. |
| Provider voided | The system stops routing operations through the voided provider. If no other provider is active, native processing resumes. |
| Provider deleted | The configuration is removed. Re-enter all details to reconnect. |
Tips
- Test before going live. Always use the Test connection button after entering or updating credentials. A failed test before saving prevents disruption to live gift card transactions.
- Center-level overrides are narrow. For Blackhawk (DG), the only center-level field is the store code. All other connection details (API URL, API alias, username, password) are set at the organization level and apply to all centers unless a center-level configuration overrides them.
- SVS centers have additional constraints. If you configure SVS, be aware that SVS integration is tablet-only, SVS-configured centers cannot sell Zenoti gift cards, and an SVS card must be the only item on the invoice. Communicate these constraints to your front desk staff before activating SVS.
- Coordinate settlement dates with your provider. The settlement start date and frequency must align with your provider agreement. Mismatched settlement settings can cause reconciliation discrepancies.
- Voiding is reversible; deletion is not. If you are unsure whether you will need a provider configuration again, void it rather than delete it. Voiding preserves the configuration record while stopping transaction routing.
Troubleshooting
The Test connection button returns an error. Verify that the API URL, API alias, username, and password are entered exactly as provided by your provider. Check for leading or trailing spaces in any field. If the error persists, contact your provider to confirm that your credentials are active and that the API endpoint is reachable from Zenoti's servers.
Gift card transactions are not routing through the external provider after saving. Confirm that the provider is set as the active provider in the Active Provider section and that you clicked Save after selecting it. If the provider was recently activated, allow a few moments for the change to take effect, then test a transaction.
The store code field is not appearing for a center-level Blackhawk (DG) configuration. Ensure you have switched the configuration scope to Center and selected the correct center. The store code field appears only at the center level for DG configurations. If the field is still missing, verify that the organization-level DG configuration has been saved successfully first.
SVS gift card transactions fail on phone POS. SVS integration is tablet-only and is not supported on phone POS. Ensure that SVS gift card sales and redemptions are performed only on tablet devices. If your center uses phone POS, use a different provider or native Zenoti gift card processing.