Over payments

Over payments happen when end users send too much cryptocurrency.

They can occur when end users accidentally enter a number too high (e.g. they intend to send 0.01 ETH but send 0.1 ETH instead). In this case, the payment will still transition to a COMPLETE status.

To give greater flexibility to your end users on how much they send crypto top-ups is recommended.

How can I see the amount actually received?

On the transactionConfirmed webhook you can see amount actually received in the paidCurrency.actual field. You can compare this value to the paidCurrency.amount field which shows the expected amount.

Handling overpayments

There is flexibility to how to handle overpayments with BVNK. The recommended way to handle overpayments for the best customer experience is to adjust the final payment of the end user to match the higher total amount received. This avoids having to return small excess amounts of crypto, and rather crediting the full amount to the end user's account. This is the Settle Merchant Wallet setting, where the total sent amount will be deposited into the MID wallet that was linked to the transaction.

The total amount sent is given in the .actual fields described in the section above, which can then be used to adjust the end users total payment amount on your system.

In certain circumstances, such as regulatory issues, that may arise when having to deal with receiving more crypto than requested, there are two other options which can be used. These are Handle Manually and Auto Refund.

Handle manually will keep the excess fraction of the transaction in its originally sent crypto, and deposit that into an equivalent crypto wallet on your account, while the original payment amount is sent to the MID-linked wallet. You can then use the payout functionality to manually return the excess amount to the end user if required.

Auto Refund will send the original payment amount to the MID-linked wallet. Any additional amount will be kept separate and an automatic payout request will be created, generating a URL. This URL must be sent to the end user for final confirmation of the address where the excess funds should be sent.

Overpayment exception flows

The summary of the flow for 3 different outcomes is given below:

📘

To change your configuration or learn more, please contact your Account Manager or Integration Manager