Features

Automating Settlement for Crypto Underpayments and Overpayments

26d agoPending

Hello Bachs Support,

We have integrated Bachs crypto checkout into Numbr (numbrtech.com). Live payments are working, and we want to handle underpayments and overpayments automatically.

Our goal is to credit each customer’s Numbr wallet with the naira equivalent of the actual crypto amount received and settled, rather than the amount originally requested.

For example, if a checkout requests $5:

A settled $3 payment should credit ₦4,140.

A settled $6 payment should credit ₦8,280.

This uses our saved rate of ₦1,380/$, with Numbr absorbing the processing fee.

Please help us confirm:

Automatic underpayment acceptance: Is there an API endpoint or account setting to accept the amount received as final settlement, without manually accepting each underpayment in the dashboard? Please share the documentation and any thresholds or restrictions.

Safe crediting status: Which statuses confirm that received funds are settled and safe to credit? In particular, should we wait for accepted, or can underpaid or overpaid already represent settled funds? Can those funds still be automatically refunded?

Amount fields: After acceptance, does amount remain the original requested crypto amount? Does amount_paid represent the cumulative gross crypto received, before merchant fees? Can acceptance change either field?

USD conversion: For crypto such as ETH or SOL, is there an authoritative USD value or exchange-rate field for the actual amount received? If not, is this calculation valid?

Original checkout USD amount × amount_paid ÷ original requested crypto amount

Additional transfers: If a customer sends multiple transfers to the same checkout, does amount_paid accumulate them? Can it increase after the payment has already reached a final status, and which webhook reports that change?

Please also provide sandbox instructions or sample checkout and payment API responses for a finalized underpayment and overpayment, including their statuses, amounts and webhook events.

We want to prevent duplicate credits and avoid manual payment tracing while ensuring customers receive the correct wallet credit.

Thank you, Numbr Team

0 comments