Adyen provides a self-service sign-up for a sandbox account. To sign up for an account visit the sign-up page and fill in the details.
To set up credentials for Adyen, head to their dashboard and navigate to Developers -> API credentials in the left hand sidebar.
Next, create a set of credentials. You will need to create a Web Service key and give it a name. We recommend setting the name to something that describes the use for the key, e.g. “Gr4vy”.
For most Adyen connectors you will need to then copy some of the following details into the Gr4vy dashboard.
Most live Adyen accounts have a custom API hostname configured. In those situations we need to know the value of the prefix of your domain name.
For example, if your live URL is
https://1797a841fbb37ca7-AdyenDemo-checkout-live.adyenpayments.com/checkout/v53/payments
then the live URL prefix would be 1797a841fbb37ca7-AdyenDemo
.
See Live URL prefix for more details.
For alternative payment methods it’s essential to also enable the allowed origin for your instance. This will allow us to connect to the Adyen API from our hosted components, like Gr4vy Embed.
For a given API credential, scroll down to the Client settings section where you will find the allowed origins configuration. Add one of the following domains based on your environment.
https://cdn.{gr4vy_id}.gr4vy.app
https://cdn.sandbox.{gr4vy_id}.gr4vy.app
The value of {gr4vy_id}
is the name of your Gr4vy instance.
It is required to set the environment to load the web components from for live Adyen transactions. This mainly applies to alternative payment methods and not card payments.
The environment should be set to one of the following, depending on your region.
If no value is provided, a default value of live
is used.
Region | Environment Value |
---|---|
Europe | live |
Australia | live-au |
US | live-us |
Asia Pacific South East | live-apse |
In the Adyen panel, “Webhook configuration” section, “Method” should be set to JSON.