Configuration and Testing

Read Before Testing

During the integration process, if you do not already have a merchant ID, please apply for a merchant account.

If you need a test merchant ID, please contact BasicEx Payment customer support.

Testing may involve not only the integration of BasicEx Payment services and invoice payments but also how you handle common payment exceptions.

You should consider testing the following types of transactions:

Full payment invoices paid on time (within 15 minutes of invoice generation).
Full payment invoices paid after the invoice has expired (1 hour later).
Unpaid invoices (payment amount less than the required invoice amount).
Overpaid invoices (payment amount exceeds the required invoice amount).
Invoices with or without miner fees:
Attempting to force an invalid transaction with a low-value invoice without paying any wallet fees. An invalid transaction is one where the payment has been made but the BasicEx Payment server has not received any confirmations within an hour of receiving it.
Partial and full refund invoices.
Listening for instant payment notifications (webhooks) and interacting with them.
Other test scenarios will depend on your specific requirements, and it is recommended to test each functionality of your application before going into production.

It is not advisable or necessary to conduct load testing on our API. If load testing is detected, your application may be subject to rate limits.