Integration Guide

Step 3: Additional Features

Now that your CoinPayments account is operational, you can leverage more features to manage your crypto assets effectively. By the end of this guide, you will be able to use the following features to optimize asset management and security:

• Recover Assets: Recover assets sent to the wrong address within the same blockchain.
• Auto-Sweep: Automate withdrawals or conversions when your wallet reaches a specified balance.
• Secured Vaulting: Add a time-release lock on specific wallets for enhanced security.
• Transaction History
• Webhook History
• Fiat Settlement (TBD)

These tools are designed to simplify your crypto operations while ensuring your funds are secure and accessible.

Recover Assets

Mistakenly sending assets to the wrong address can be a common issue, but CoinPayments offers a self-service solution to recover such assets sent to the wrong address for all tokens within the SAME blockchain. The feature allows for automatic or manual handling of recovery and is available ONLY for deposits to merchant addresses.

Example:

If you provide an ETH address to customers for deposits and a customer accidentally sends USDT.ERC20 to this address, CoinPayments will treat this as a mistake because token balances and native coin balances are managed separately. The system identifies the deposit's currency and automatically forwards the funds to your USDT primary balance. This ensures that assets are not lost due to address mismatches. Here's how to set up the feature:

Configure Automatic Handling

Configure Manual Handling

For greater control over how erroneous deposits are managed, you can opt for manual handling. This allows you to review flagged transactions and decide whether to claim the funds.

Auto-Sweep

The Auto-Sweep feature allows you to automatically withdraw and/or convert the entire balance of a specific coin wallet once it reaches a designated balance level.

Once enabled, it is a convenient tool for automating asset management and ensuring your funds are transferred or converted without manual intervention.

This feature needs to be set up for each coin individually.

• Automatically withdraw balances that exceed a specified minimum amount.
• Convert funds to another cryptocurrency if the destination address is for a different coin e.g. receive Bitcoin, convert automatically to USDT.

Configure Auto-Sweep

Secured Vaulting

The Vaulting feature provides an additional layer of security for your CoinPayments account by placing a time-release lock on specific coin wallets. This ensures that the balance in the locked wallet cannot be withdrawn, transferred, converted, or used in any way until it is unlocked.

• Restricted Access: While locked, your coins cannot be accessed or used, but payments and deposits to the wallet remain uninterrupted.
• Time-Release Lock: Once unlocked, a pre-specified delay (up to 56 hours) must pass before access is granted.
• Email Notifications: You'll receive an email notification when the lock is removed, giving you time to take action if your account has been compromised.

Locking Coins in the Vault

Transaction History

The Transaction History feature allows you to review all incoming and outgoing transactions within your account. This includes deposits, withdrawals, conversions, and payments for goods and services. It provides a comprehensive record of your account activity, ensuring transparency and accountability.

To access the feature in the main dashboard menu navigate to the Transactions tab.

Transaction Types

CoinPayments Transaction History tracks the following types of transactions:

• Received: Deposits sent to primary balances or API wallets/addresses.
• Sent: Withdrawals from primary balances or API wallets/addresses.
• Conversion: Currency conversions performed between currencies activated for your account.
• Invoice: Payments for invoices created using the Invoice Builder.
• Payment: Payments made via payment buttons, plugins, or API-generated invoices.

Transaction Details

The Transaction History provides detailed information for every transaction, including:

1. Transaction date.
2. Transaction type (e.g., received, sent, conversion, etc.).
3. Transaction status.
4. Currency involved, including source and destination currencies in case conversion is involved
5. Transaction amount in both crypto and fiat currencies.
6. Address or wallet where the transaction was sent or received.
7. Breakdown of the transaction amount, including gross, net, and fees (in both crypto and fiat currencies).
8. Transaction progress, including confirmations on the blockchain.
9. Blockchain transaction ID.
10. Support ID for addressing issues with the CoinPayments Support team.

Transaction Status Descriptions

Each transaction type has specific statuses that provide updates on its progress:

Received:

• Created: Transaction is initiated by the customer and detected on the blockchain by CoinPayments.
• Confirmations: Indicates the number of confirmations received on the blockchain. Funds are deposited only after full confirmation.
• Completed: Transaction has the required confirmations, and funds are deposited into your wallet.

Sent:

• Created: Transaction is initiated and sent to the recipient (internal or external).
• Completed: For internal transactions, funds are deposited into the destination wallet; for external transactions, funds are placed on the blockchain and tracked until full confirmation.

Conversion:

• Created: Transaction is initiated by you for conversion.
• Funds Sent: Transaction is put on the blockchain to be sent to a 3rd party converter
• Funds Converted: Funds converted. Deposit in the destination currency is expected to be put on blockchain
• Funds Transferred: Incoming funds are detected on the blockchain.
• Conversion Completed: Funds deposited to your balance.

Invoice/Payment:

• Created: Payment for goods/services is initiated and detected on the blockchain.
• Confirmations: Indicates the number of confirmations the transaction has received on the blockchain. When transaction has received the required number of confirmations, it means that Coinpayments has received the funds and is planning the payout to your wallet/address depending on the payout mode selected for this specific currency in your Payment Settings.
• Payout Scheduled: Coinpayments has scheduled the payout of funds to your wallet balance based on your Payment Settings for the specific currency.
• Converting: Funds are being converted if the selected payout mode includes conversion.
• Sent to you: Converted funds are sent to the final destination wallet.
• Completed: Funds are either deposited to internal wallets after completing all blockchain confirmations or are sent to external addresses.

Export Transaction History

You can export transaction history to your device to manipulate the records locally for your accounting purposes. To export history click Export.

The history will be downloaded to your device in the .csv format.

You can filter out the records that you want to download by applying filters by date.

Webhook History

The Webhook History feature allows you to review all webhook notifications for all integrations, wallets and addresses for which webhook url has been provided. This includes deposits, withdrawals, conversions and payments made for buttons created via API and invoices created via API or e-commerce integrations.

To access the feature in the main dashboard menu navigate to Integrations > Webhook History.

Notification Transaction Types

CoinPayments Webhook History tracks notifications for the following types of transactions:

• Received, Sent, Conversion: transactions sent from/to API wallets/addresses. You can provide a url for the wallet or for a specific address within the wallet. In case you set up a url for an address, it overrides the url set up for the wallet where the address belongs.
• Invoice: Payments for invoices created using the API or e-commerce integration.
• Payment: Payments made via payment buttons generated via API integration.

Notification Details

The Webhook History provides detailed information for every transaction, including:

1. Webhook notification date and time.
2. Transaction type (e.g., received, sent, conversion, invoice, payment).
3. Transaction amount and currency.
4. Transaction status.
5. Webhook notification status.
6. Time when the notification was sent and number of tries to reach the webhook URL
7. Transaction support ID with the CoinPayments system.
8. Integration name under which transaction is performed.
9. Webhook URL.

Notification Statuses

Webhook notifications have the following statuses that provide updates on their progress:

• Sent: webhook notification successfully delivered to the webhook URL
• Failed: webhook notification failed to be delivered to the webhook URL and all the retries are expired

• Retrying: webhook notification is being delivered to the webhook URL. CoinPayments is retrying to deliver the notification to the webhook URL

Configuring Webhook Notifications

Dashboard UI

You can set up webhook notifications for invoices via CoinPayments Dashboard UI.

API

You can set up webhook notification via API when creating invoices, wallets and addresses.

For invoices, use webhooks object in the createInvoice endpoint request. Url provided for a specific invoice overrides the default webhook notification URL set up via Dashboard UI.

For wallets, use webhookUrl attribute in the createWallet endpoint request. Notifications for all transactions within the wallet will be sent to this address.

You can specify a webhook URL at the address level. For this use notificationUrl attribute in the createAddress endpoint request.