What information do you need for the iFrame integration access?

For iFrame access, we would need a) your Wallet API URL, which is your callback API for the user, debit, and credit transactions with your system. Also, we would require b) the domains from which the iFrame will be initialised, including any dev/staging environments during the integration process (that means also localhost:port if your team will be initialising the iFrame from their local machines). For the wallet API, we just need the root URL at this point, not the fully working API itself. Once this is provided, together with the domain(s) you are going to load the iFrame from, we can set up the iFrame so you can initialise it already (from the whitelisted domains) in a logged-out mode. Later, when you fully set up the Wallet API, you'll be able to test betting and other related functionalities.