Skip to main content
Further technical details of both authentication mechanisms can be found in our Authentication section.
No need to whitelist your IP addresses.
Reach out to our Implementation team. Provide them with the currencies you would like to test with. Also, let them know if you would like very specific account balances. We will get back to you with the ready setup.
You can get credentials to access our Sandbox at any time. There are no prerequisites to be met. You can request it and have it right away. Also, the Implementation team could also organize a brief demo of our API capabilities.Regarding credentials to accessing Production, you should have completed the onboarding and KYC on Ebury’s side. Preferably, you should have also completed a fair amount of testing in Sandbox before requesting the Production credentials. All credentials are communicated via our Welcome email.
We offer a standard solution in this case. We configure an API Technical contact on every underlying client. The API Technical contact can orchestrate and manage each of the workflows that the underlying client might be interested in. Depending on the customer’s needs, the API Technical contact can be configured with different permissions. Let us discover your problem statement together and then propose the nature of the API Technical contact required.
No, both the API and EBO have the same behavior. For example, a user will be treated to the same behavior whether he creates a mass payment via EBO or API or needs to authorize a payment.

Still having a question?

You can submit your question or request through our contact form. Please provide as much detail as possible so we can assist you effectively.Get in touch