AI resources

Test the integration

The testing process allows you to verify that the configurations made during your integration work correctly before receiving real payments. With Wallet Connect, the test reproduces the complete flow: creating the agreement, the buyer approval, generating the payment token and processing a payment through the Orders API.

The tests are performed on the production endpoints using test credentials, which means there is no separate sandbox domain. Make sure to use the test Access TokenPrivate key used in the backend to authenticate requests. In Wallet Connect, the test and production Access Tokens and Public Keys are provided by the team responsible for creating your application. You can also view them in Your integrations > Integration data > Tests > Test credentials. The test Access Token starts with the prefix `APP_USR`. of the seller in all requests so as not to generate real charges.

Before starting, make sure the items below are available.

PrerequisiteDescription
Test accountsYou must have two distinct test accounts, and both are required: a seller account, to configure the application and perform the charges, and a buyer account, to approve the agreement and simulate the purchase.
Balance in the buyer's accountThe buyer's test account must have sufficient balance, as the payment is debited directly from the wallet. Set the amount when creating the test account.
Test credentialsThe seller's test Access Token is provided by the team responsible for your integration and can also be found in the Credentials section.

After validating the correct functioning of the integration in the test environment, replace the test credentials with the production ones and move on to go to production.