By default, you can test all your card payment flows. However, if you require any alternative payment methods (e.g., PayPal, Sofort, iDEAL) you can contact our Integration team at email@example.com to enable them on your test account.
Once you've run some initial tests to make sure everything's running smoothly, you can then apply for a live account to start processing payments with us. Please contact our Sales team at firstname.lastname@example.org. We'll need you to complete an online application form, which will then be reviewed by our in-house Onboarding team.
We may ask you to provide further documentation, including corporate structure documentation, legal entity details, bank account information, and principal owners.
Once approved, you’ll execute a contract and we'll provide you with your production credentials.
We then recommend that you perform a test transaction, or run a pilot in production, before processing real customer transactions. This gives you the opportunity to ensure that everything is set up correctly and will work as expected.
After that, you're ready to start accepting live payments from your customers!
If you are the administrator of your Hub account, you can add new users from the Hub. Go to Settings > User management and click New user.
Once created, their profile will be added to the user list and they will receive an email inviting them to log in.
Take a look at our Hub settings guide for more information.
Yes. You can simulate a dispute by using specific combinations of payment methods and amounts, as described in our disputes testing guide.
Yes. To add a webhook in the Hub, go to Settings > Channels and click New webhook.
Once added, you can choose what event you want to receive webhooks for. To trigger the webhooks, just perform a transaction and take one of the actions you enabled. For example, if you chose the
payment_refunded event, just perform a refund and you will get a webhook.
Find out more about the events for which you can create webhooks.
You can find the Acquirer Reference Number (ARN) for a payment in the Payments section of the Hub. Just click on the relevant payment action to open up the summary, and you'll find the ARN under the Action details heading.
Alternatively, you can find the ARN in the response of the get payment actions endpoint, as well as in the payment_captured and payment_refunded webhook notifications.
Typically, this means that the customer's card issuing bank (or the acquirer) has declined the transaction. For example, if the CVV is incorrect or the card cannot be used for online transactions. The cardholder should contact their issuing bank to understand what has happened.
You can find out about the other response codes here.
Yes. Please contact our Integration team at email@example.com to activate this feature.
Also note that you need to let your account manager know you require this functionality, so the feature is ready for you when you go live.
There are two different ways to do this:
In order to enable dynamic billing descriptors on your account, please contact your customer success manager.
Once they are enabled, simply follow the instructions in this guide. Note that you can currently only set billing descriptors for payment requests.
Yes, you can test most of the alternative payment methods (APMs) we support in the sandbox environment.
To start testing, please contact your customer success manager or integration engineer to activate the APMs you want to test in your sandbox account.
Follow the links on our APM testing page to find out how to test each payment method.