Set up your payment gateway
Avantio allows you to connect different payment gateways to automate charges related to bookings.
The integration process depends on each provider. Some platforms require specific settings from your bank, while others need production credentials, tokenization, webhooks, or an active website to complete testing.
Before starting the technical process, you should confirm compatibility, sign the relevant contract, and complete the onboarding requested by the provider.
What will you learn in this article?
In this article, you will learn how to:
Prepare the necessary information before starting the connection.
Request the required activations from your bank or provider.
Identify the credentials needed for each platform.
Set up webhooks and tokenization.
Complete the connection with help from Avantio.
Run the necessary tests before processing real payments.
Troubleshoot the most common errors during integration.
Benefits
Connecting a payment gateway with Avantio allows you to:
Automate booking payments.
Reduce manual operations.
Apply authentication systems like 3D Secure.
Centralize payment configuration.
Improve transaction traceability.
Make pre-authorizations when the platform allows it.
Process subsequent payments according to your contracted setup.
Receive real-time payment notifications.
Make it easier to manage refunds and issues.
When should you do this setup?
You should start this setup when:
You have chosen your payment platform.
You have confirmed it operates in your country.
You know the associated costs.
The provider has approved your company account.
You have your production credentials.
Your bank has completed the necessary activations.
You want to replace a previous connection.
You need to automate payments from Avantio.
Before you start
It’s a good idea to check beforehand:
That your company is registered in a compatible country.
That you have signed the contract with the provider.
That the onboarding process is complete.
That you have admin access to the account.
That the credentials are for the production environment.
That your POS terminal is compatible with the required protocols.
That you have an active website if needed.
That you have decided who will manage the tests.
That you know which payment methods you will use.
That you have confirmed if you need pre-authorizations or tokenization.
It’s also recommended to coordinate activation with the team responsible for bookings, payments, and reconciliation.
Never share sensitive credentials through unauthorized channels. Provide the requested information via a ticket addressed to the Customer Experience team.
Connect your chosen platform with Avantio
Redsys via Worldline
Redsys via Worldline
This integration allows you to connect a Redsys POS terminal with Avantio Payments using the connector provided by Worldline.
Before you start
Contact Avantio’s Customer Experience team to check that your bank and POS terminal are compatible.
Currently, this integration is not available with Banco Sabadell.
Once compatibility is confirmed, Avantio will provide you with the relevant contract.
Request activations from your bank
After signing the contract, ask your bank for the following configurations:
Activation of the SIS REST PSPS protocol.
Linking your Redsys merchant to PSP OGONE SIS REST WITH EXTERNAL MPI.
Activation of MIT operations.
Activation of MOTO operations.
Enable 3D Secure v2.
Activation of pre-authorizations.
MOTO operations are required for certain transactions related to portals.
Pre-authorizations allow you to hold and release amounts, for example, to manage security deposits.
Additional setup for BBVA
If BBVA is your acquiring bank, you must also request activation of the optional CVC protocol.
If your bank needs additional technical information, they can contact Avantio at:
Required information
Once the bank has confirmed the activations, create a ticket for the Customer Experience team and provide:
Merchant ID or FUC.
MCC code or merchant category.
Terminal number.
Available payment methods.
Visa Acquirer BIN.
Mastercard Acquirer BIN.
Also indicate if your POS terminal supports other methods, such as American Express.
Follow these steps
Contact Avantio’s Customer Experience team.
Request a compatibility check for your bank.
Confirm your bank can work with the required protocol.
Review and sign the contract provided by Avantio.
Ask your bank to activate the SIS REST PSPS protocol.
Request linking your merchant to PSP OGONE SIS REST WITH EXTERNAL MPI.
Request activation of MIT and MOTO.
Ask for 3D Secure v2 to be enabled.
Request activation of pre-authorizations if you will manage deposits.
If you work with BBVA, request the optional CVC.
Wait for your bank to confirm all activations.
Gather the Merchant ID, MCC, terminal number, and Acquirer BIN.
Send the information to Avantio via a ticket.
Wait for the technical setup to be completed.
Make a test booking.
Check that the payment works.
Test subsequent operations or pre-authorizations if applicable.
Estimated activation time
The process can take from several days to several weeks.
The timeline depends on:
How quickly your bank responds.
The previous setup of your POS terminal.
Activation of the required protocol.
Validation of technical identifiers.
Final activation of the platform.
Axerve
Axerve
Before you start
Contact Axerve to sign the contract and request your account setup.
When you contact the provider, also request the Tokenization service if you need to use tokenized cards for future payments.
Once the contract is approved, Axerve will give you access to their intranet or back office.
Required credentials
From the Axerve dashboard you need to obtain:
ShopLogin.
ApiKey.
You will also need to set up a webhook URL to receive payment notifications.
Set up the webhook
The webhook allows Axerve to notify Avantio of transaction status changes in real time.
Request the URL from Avantio
Create a ticket for the Customer Experience team.
State that you are setting up Axerve.
Request the webhook URL for your account.
Keep the URL exactly as we provide it.
Add the URL in Axerve
Log in to the Axerve dashboard.
Go to Configurazione.
Select Ambiente.
Find the Url server to server field.
Paste the URL provided by Avantio.
Save the configuration.
Do not modify the URL or add extra spaces.
Follow these steps
Contact Axerve.
State that you will use the integration with Avantio.
Sign the contract.
Request the tokenization service if needed.
Complete the account verifications.
Access the Axerve back office.
Find your ShopLogin.
Get your ApiKey.
Create a ticket for the Customer Experience team.
Request the webhook URL.
Go to Configurazione → Ambiente → Url server to server.
Enter the provided URL.
Save the configuration.
Send Avantio your ShopLogin and ApiKey.
Wait for the integration to be completed.
Make a test booking.
Check that Axerve sends payment notifications.
Verify that the transaction status updates in Avantio.
Estimated activation time
The connection can be completed the same day once Avantio receives and validates the data provided by Axerve.
The timeline may increase if:
The contract is not yet approved.
Tokenization is not activated.
Credentials are incorrect.
The webhook is not set up.
The account is not enabled for production.
Amazon Payment Services
Amazon Payment Services
Before you start
Contact Amazon Payment Services to finalize the contract and start the onboarding process.
During this process, make sure to specify that you need to use tokenization.
Tokenization is required to securely store a card reference and perform the operations allowed by the platform without directly keeping sensitive data.
Required credentials
To activate the connection, you need:
MerchantId.
AccessCode.
ShaRequest.
ShaResponse.
The credentials must correspond to the production environment, unless specific test data is requested first.
Follow these steps
Contact Amazon Payment Services.
Confirm that the platform is available in your country.
State that you will use the integration with Avantio.
Finalize the contract.
Complete the onboarding documentation.
Request tokenization activation.
Wait for Amazon Payment Services to approve your account.
Request the integration credentials.
Make sure you have MerchantId, AccessCode, ShaRequest, and ShaResponse.
Create a ticket for the Avantio Customer Experience team.
Provide the credentials through the indicated secure channel.
Wait for Avantio to complete the configuration.
Make a test booking.
Complete the 3D Secure authentication.
Check that the transaction appears correctly.
Verify tokenization works when needed.
Pay attention to the details
All payments processed through this gateway will use 3D Secure by default.
Make sure the booking flow allows the guest to complete authentication successfully.
Estimated activation time
Activation usually takes several days.
The timeline mainly depends on completing onboarding, activating tokenization, and providing the credentials.
PowerTranz
PowerTranz
PowerTranz is the FAC version compatible with 3D Secure v2.
It replaces the previous FAC integration, which only supported 3D Secure v1.
Before you start
To complete the integration, you must have an active website.
The website will be used for testing:
In the test environment.
In the live or production environment.
Confirm with PowerTranz that your account and market are compatible with the version that supports 3D Secure v2.
Required credentials
Request from PowerTranz:
PowerTranzId.
PowerTranzPassword.
The credentials must correspond to the environment specified for each testing phase.
Follow these steps
Contact PowerTranz to start the onboarding process.
State that you will use the integration with Avantio.
Confirm that you will contract the version compatible with 3D Secure v2.
Provide PowerTranz with the required documentation.
Prepare an active website.
Request the test environment credentials.
Obtain the PowerTranzId and PowerTranzPassword.
Create a ticket for the Avantio Customer Experience team.
Provide the credentials through the indicated secure channel.
Coordinate with Avantio to run tests in the test environment.
Check that the authentication process works correctly.
Complete production environment activation with PowerTranz.
Provide the final credentials if they are different.
Run a test in the live environment.
Check that the payment appears in both Avantio and PowerTranz.
Confirm with Avantio that the integration is ready to use.
Expected result
At the end of the process:
PowerTranz will be connected with Avantio.
Payments will use 3D Secure v2.
You will be able to process cards in the supported currencies.
Transactions will be recorded in the provider's dashboard.
The website will be ready to complete the authentication flow.
Expected result
Once the selected platform is connected:
The gateway will be linked with Avantio.
You will be able to process payments for bookings.
Payments will use the available authentication.
Transactions will be sent to the corresponding provider.
Status changes will be updated through the configured mechanism.
You will be able to perform the operations allowed by your contract.
Subsequent payments or pre-authorizations will work when enabled.
You should not consider the integration complete until you have successfully completed a test booking.
Recommended next steps
After activating the platform:
Make a test booking with a small amount.
Check that the payment appears in Avantio.
Verify that the transaction appears in the provider's dashboard.
Confirm that the amount and currency are correct.
Check that 3D Secure is working.
Check webhook notifications when applicable.
Test tokenization if you have contracted it.
Review subsequent payments.
Test a pre-authorization if the platform allows it.
Check the refund procedure.
Confirm internal user permissions.
Document the procedure for handling incidents.
Inform your team before starting to process real payments.
Key data and options
Depending on the platform, you will need:
Redsys via Worldline: Merchant ID or FUC, MCC, terminal number, payment methods, and Acquirer BIN.
PowerTranz: PowerTranzId and PowerTranzPassword.
Amazon Payment Services: MerchantId, AccessCode, ShaRequest, and ShaResponse.
Axerve: ShopLogin, ApiKey, and webhook URL.
You may also need:
MIT activation.
MOTO activation.
3D Secure v2 configuration.
Pre-authorization activation.
Tokenization.
Active website.
Test and production credentials.
Server-to-server configuration.
Limitations and considerations
Keep in mind that:
The integration cannot be completed until the provider approves the account.
Timelines depend on the provider or the bank.
Credentials must match the correct environment.
Incorrect data can prevent the connection.
3D Secure activation depends on the account configuration.
Tokenization must be contracted when needed.
MIT and MOTO operations require specific authorization.
Pre-authorizations are not available if the bank does not enable them.
Webhooks must be configured exactly with the provided URL.
PowerTranz requires an active website for testing.
Redsys needs specific configurations from the bank.
Amazon Payment Services uses 3D Secure by default.
You should not process real payments before completing the tests.
Changing a credential can interrupt payments.
Before replacing an existing gateway, review what will happen with pending payments for already created bookings.
Best practices
Confirm compatibility before starting the process.
Always use a business account.
Complete onboarding before requesting the connection.
Request production credentials.
Never share passwords or keys in unauthorized channels.
Copy credentials without extra spaces.
Store keys in a secure manager.
Limit administrative access.
Enable two-factor authentication when available.
Set up 3D Secure v2 correctly.
Request tokenization from the start if you will need it.
Test in all necessary environments.
Verify webhooks after activation.
Check both initial and subsequent payments.
Document changes made by your bank.
Do not deactivate the previous connection until the new one is validated.
Practical example
A Spanish company wants to keep its Redsys POS conditions and automate its payments through Avantio Payments.
First, they contact Avantio to confirm that their bank is compatible.
After signing the contract, they ask the bank to activate the SIS REST PSPS protocol, MIT, MOTO, 3D Secure v2, and pre-authorizations.
Once the bank confirms the setup, the company provides Avantio with the Merchant ID, MCC, terminal number, and Acquirer BIN.
Avantio completes the configuration and the company makes a test booking. They also check a pre-authorization to ensure they can correctly hold and release a deposit.
After verifying all operations, they start using the connection for real bookings.
Common Errors
The bank does not recognize the requested protocol
Provide the bank with the full name of the protocol and the operations that need to be enabled.
If needed, the bank can contact Avantio at [email protected].
Redsys does not process subsequent payments
Check that MIT operations are enabled.
Also review the MOTO configuration when transactions are related to certain portals.
Pre-authorization is not working
Confirm with the bank that pre-authorizations are enabled on the relevant terminal.
General activation of the POS does not necessarily mean this operation is available.
Payment does not complete 3D Secure
Verify that 3D Secure v2 is enabled on the account and that the provider has set up authentication correctly.
PowerTranz cannot complete tests
Check that the website is up and accessible.
Also make sure you are using the PowerTranz version compatible with 3D Secure v2.
PowerTranz credentials do not work
Confirm whether the credentials are for the test or live environment.
Do not use test credentials to process live payments.
Amazon Payment Services rejects the connection
Check that MerchantId, AccessCode, ShaRequest, and ShaResponse are complete and belong to the same account.
Also verify that onboarding is complete.
Cannot process subsequent payments with Amazon Payment Services
Confirm that tokenization is enabled.
Having the gateway does not necessarily mean the tokenization service is enabled.
Axerve does not update payment status
Check the webhook configuration.
The URL must be added in:
Configurazione → Ambiente → Url server to server
Axerve ApiKey is not valid
Check that the key is for production and does not include spaces or extra characters.
Test booking works, but real payment does not
Confirm that the test was not only performed in a test environment.
Verify that the production account and credentials are active.
If something isn't working
Before contacting the Customer Experience team:
Check that the contract is finalized.
Verify that onboarding is complete.
Confirm that the account is approved.
Check that the credentials are correct.
Check if they belong to the test or production environment.
Verify that 3D Secure v2 is enabled.
Confirm that tokenization is enabled when needed.
Review the configurations made by the bank.
Check the webhook URL.
Confirm that the website is up and running.
Check the transaction status in the provider's dashboard.
Refresh the page and check the result again.
Make a new test booking.
If the issue persists, create a ticket and include:
Company name.
Platform used.
Bank or acquirer, if applicable.
Booking ID.
Date and time of the operation.
Amount and currency.
Transaction status.
Full error message.
Screenshots.
Environment where the error occurred.
Confirmation of the activations performed.
Do not include passwords, full ApiKeys, or other sensitive credentials in screenshots.
Frequently Asked Questions
Do I need to sign up for the platform before connecting it?
Do I need to sign up for the platform before connecting it?
Yes. You must sign the contract and complete onboarding directly with the bank or provider.
Avantio handles the technical integration, but does not replace the commercial contract.
How long does activation take?
How long does activation take?
It depends on the platform:
Redsys via Worldline can take days or weeks.
PowerTranz may require several days and different testing phases.
Amazon Payment Services usually takes several days.
Axerve can be activated the same day after receiving the correct information.
These timeframes are estimates.
What is tokenization?
What is tokenization?
Tokenization replaces card data with a secure reference.
It allows certain subsequent operations without directly storing sensitive card information.
What is a webhook?
What is a webhook?
A webhook is a URL that allows the platform to send automatic notifications to Avantio when the status of a payment changes.
In Axerve, it must be set up in the Url server to server section.
What is the difference between MIT and MOTO?
What is the difference between MIT and MOTO?
MIT are transactions initiated by the merchant on a previously authorized card.
MOTO is used for certain operations where payment is initiated via channels like mail or phone. In this integration, it may be needed to process some transactions from portals.
What are pre-authorizations for?
What are pre-authorizations for?
They allow you to temporarily hold an amount without making a final charge.
They can be used, for example, to manage deposits and later release the held amount.
Is it mandatory to make a test booking?
Is it mandatory to make a test booking?
Yes, it is highly recommended.
A test booking lets you check payment, authentication, notifications, and subsequent operations before working with real bookings.
Can I send credentials by email?
Can I send credentials by email?
Only use the secure channel indicated by the Customer Experience team.
Do not send passwords or sensitive keys through unauthorized channels.
Who can help me during the connection process?
Who can help me during the connection process?
You can contact your Account Manager or the Avantio Customer Experience team.
We can help you via a support ticket or, if needed, through a video call.