Frequently Asked Questions

Q: How do I obtain an API key?

A: Log in to the iPay dashboard, navigate to the API Keys section, and create a new key with your company, wallet, and callback URL. Then contact the iPay team to activate it — they will also register your redirect URL at this point.

Q: What is the redirect URL?

A: The page on your site where the customer lands after completing the payment (e.g. your deposit-success or dashboard page). It is registered by the iPay team when your API key is activated. It only closes the customer journey — never credit a deposit based on the redirect; credit it when the server-to-server callback arrives.

Q: What happens if my callback URL is down?

A: iPay may retry sending the notification. Ensure your endpoint is reliable and logs errors for debugging.

Q: Can I use multiple wallets?

A: Yes, add multiple wallets in the dashboard and create separate API keys for each.

Q: How do I verify the secret token?

A: Compare the authorization HTTP header of the callback request with the secret token provided by iPay. Reject mismatches. The token is not part of the JSON body.

Q: Why are some callback fields spelled unusually?

A: The callback sends transferedAmount (single r) and transactionFeePrecent exactly as written. Match these keys literally in your parser — see the JSON Payload Explanation.

For more questions, contact support@i-pay.io.

Wondering why so many processors say no? See what the MATCH list is and how it blacklists forex brokers and casinos.