The Settings tab lets you control how your CoinGate integration behaves at a general level — including naming, settlement rules, payment notifications, callback format, and underpayment tolerance.
These settings apply per integration, and the fields differ depending on whether you're configuring:
-
API Integration
-
Payment Button Integration
1. Navigate to your integration
-
Go to your CoinGate Business Dashboard
-
Click Integrations in the left sidebar
-
Choose API Management or Payment Buttons
-
Select the integration you want to configure
2. Adjust general invoice behavior – go to the Settings tab
The Settings tab allows you to define the basic behavior for how your invoices are created and settled.
-
Title
Name your integration (e.g. "Shopify Store EU"). This is for internal reference only.
-
Whitelisted IP addresses
Limit invoice creation requests to specific IP addresses (for API-based integrations only).
-
Display header title on invoice
Enable this toggle if you'd like the integration title to appear on customer invoices.
-
Settlement setting
Choose how incoming crypto is settled to your account:-
-
Default API / plugin settings – honors the
receive_currency
parameter from your API or plugin configuration. Example: if set to EUR, any received crypto is automatically converted to EUR. - Custom settings (advanced) – unlocks the Currency settings tab, allowing you to manually select settlement rules for each cryptocurrency (e.g., keep ETH, convert DOGE to USDC). This overrides API or plugin config.
-
Default API / plugin settings – honors the
-
-
Underpaid cover percentage (%)
Set a buffer to automatically approve slightly underpaid orders.
Example: If set to 2%, an order paid 98% of the required amount will still be marked as paid.
-
Paid notifications
Receive email alerts when a payment is received via this integration.
You can configure:-
- Frequency: Instant, Daily, or Weekly
- Email address(es): Add one or more recipients (e.g. finance@yourcompany.com)
-
-
Callback format
Choose how CoinGate sends data to your backend (for plugins or APIs):-
-
Form encoding (
application/x-www-form-urlencoded
) — required for plugin setups -
JSON (
application/json
) — suitable for API integrations
-
Form encoding (
-
Comments
0 comments
Article is closed for comments.