The problem is either in your contract/input data or the item has already been purchased. In the error message, the part after "execution reverted" is a response from your contract. You should recognize and know how to troubleshoot this. If there is no response from the node, then it’s likely your contract isn’t verified, or you don’t have error responses set up.

Troubleshooting:

1. Verify your smart contract. If you are using a proxy contract, please save the proxy address against the ABI of the implementation contract.
2. Check whether the input data corresponds to the ABI of the contract. You can use EVM ABI decoder.
3. If your smart contract requires whitelisting wallets, ensure that you have whitelisted both our Hot Wallet and Estimation addresses. The estimation wallet might change; it rarely happens, and we will tell you if it does. Please get in touch with us to get the list of Wert wallet addresses.
4. Ensure the amount contains no more than the allowed decimal digits. Please refer to Decimal Precision.
5. Please make sure there are no restrictions or limitations on your contract that would prevent us from executing the input data.
6. If the issue persists, please share a successful transaction hash from your wallet executing the same input data with us.

Input data was incorrect before being sent to the node (input variables/method name/etc do not match).

Troubleshooting: Check input data; variables or methods contain an error.

Node error.

Troubleshooting: See the node response in the description. Most likely invalid method name.

There is no such partner ID in Wert’s database.

Troubleshooting: There are two different credentials for Sandbox and Production. Ensure you log in using the correct partner_id that corresponds to the environment you want to test in.

The signature doesn’t correspond to the input data; the signature may be correct, but the wrong data was signed.

Troubleshooting:

1. Check whether all required parameters are signed and are in the correct order.
2. commodity_amount in your signed data must have no more than 8 decimal places. Round up if it doesn’t meet this requirement.
3. Check whether your private and public keys are correct.

The smart contract was not verified on Etherscan/Polyscan or Wert’s database.

Troubleshooting: Verify the contract on Etherscan/Polyscan. If you can’t verify the smart contract, please refer to this guide.

Smart Contracts are disabled for this partner ID.

Troubleshooting: Check whether you have logged into the correct environment (production/sandbox). If it’s correct, please contact Wert's partner support team and provide us with your Parter ID.

Commodity doesn’t exist.

Troubleshooting: Make sure you use the correct commodity, network and origin that corresponds to the environment (production or sandbox) you want to use. Please refer to Supported coins and blockchains.

There is an issue with verifying your smart contract.

Troubleshooting:

1. Check sc_address and address contain valid data.
2. Verify your smart contract.

Invalid data.

Troubleshooting:

1. The minimum order amount is approximately $1.50 on the sandbox and $5 on the production environment. Please update your commodity_amount if it is less than the required minimum.
2. Check whether address and sc_address contains correct data.

Troubleshooting: Update to the latest version of our SDK.

Troubleshooting: Create a new sandbox account with a random phone number; OTP is 0000.

Troubleshooting:

Please note that the OTP is always 0000 if you’re using the sandbox environment. Otherwise:

1. Ensure that you have a strong phone signal.
2. Verify that your mobile carrier is not experiencing any outages or undergoing maintenance.
3. Check your phone settings to ensure no restrictions are blocking SMS messages from abroad. Some carriers have internal security settings that block particular senders by default. You need to adjust these settings or contact your carrier to remove these restrictions.
4. If the issue persists, please contact us for further assistance.