IPN and API
Q: I've got an error "Notification key is null"
A: You should generate IPN secret key here
Q: 2fa does not accept codes from the application
A: Synchronise the time in the authenticator app. If the time differs, the app will generate incorrect codes.
Q: I can't use auth endpoint, i don't have a password
A: You should logout, open this page and enter your registration email. You will receive a link to create a password
Q: Where can I get a library for automating 2FA for payments?
A: Speakeasy, or you can Google other options yourself
Q: Got an error "withdrawals[0] does not match any of the allowed types"
A: You probably missed square brackets or used an incorrect URL in the body. Use the following example:
withdrawals: [{
"payout_description": "customer 1",
"ipn_callback_url": "https://url.com/callback/payout",
"withdrawals": [{
"unique_external_id": "somethingsomething",
"address": "address",
"currency": "btc",
"amount": 0.01
}]
}Q: I've got "Bad request error" when verifying the payout
A: The code is incorrect. There is a real possibility that you are trying to do this from a multi-user account - you must check this. Only the code from the master account email is suitable for verification.
Q: I'm creating a payment via API without fixed-rate option, but in response it's anyway set as "true"
A: You should set parameter is_fee_paid_by_user to false - fee paid by user feature can't work without fixed-rate, so if it's set as "true" - fixed-rate will be automatically also set as "true"
Payments and dashboard
Q: I've got "payCurrency [currency] is not allowed" error
A: This error occurs on invoices when the selected currency is disabled for payment on your account. Enable it here
Q: Payment received partially paid status even though the amount sent was exactly equal.
A: The partially paid status is based on the final fiat equivalent, even if the expected amount was sent. You can manually change payments from the partially paid status to finished in the personal account, directly in the payment details.
A: It means, deposit was sent via wrong network or wrong coin was sent. You can continue such payments manually on your side. Please take a look at this article; it describes how you can do it.
A: It means, that your user has sent you funds again to the same address. You can continue such payments manually on your side. Please take a look at this article; it describes how you can do it ( works the same as for "wrong asset confirmed" status ).
Q: Why doesn't your system recognize smart contracts?
A: Unfortunately, there are a vast number of different smart contracts. Each of them requires a separate technical integration into our system, which is why we add new ones gradually.
A: Please check your ip address here and whitelist both your IPv4 and IPv6 addresses in your dashboard
Withdrawals and custody
Q: Insufficient balance error/withdrawal was rejected without reason
A: This error occurs due to insufficient balance or an attempt to withdraw the full amount while fees are set to 'sender.' Please ensure you have enough funds or change the fee payer to 'receiver' in this section https://account.nowpayments.io/store-settings#details.
Q: My payout stuck in creating status.
A: Usually it means your payout is not verified with 2fa code. Please verify your payout with code from your email/authentication app. If you can't - it will be rejected automatically within 1 hour.
Q: 2FA code for withdrawal doesn't work
A: Please check if the code has been entered correctly. If it's correct, make sure you are using 2fa code from the same account payout was requested from. If you request payout from master account using sub account - you will need 2fa code from master account anyway.
Q: How can I disable custody?
A: Add a payout wallet in Payout Wallets Settings (https://account.nowpayments.io/store-settings#wallets), then disable Custodial Processing in Payment Details Settings here: https://account.nowpayments.io/store-settings#details. Please note that custody balances must be empty or nearly empty before custody can be disabled.