First Atlantic Commerce Integration Specs
Setting up your First Atlantic Commerce payment gateway integration
Welcome! If you’re looking for information about setting up your First Atlantic Commerce payment gateway integration with WebRezPro, you’ve come to the right place. If you have any questions or concerns, please don’t hesitate to contact our support department.
How does the integration work?
The First Atlantic Commerce payment gateway integration allows you to process payments for online bookings and other card-not-present transactions through WebRezPro.
The PCI-compliant integration securely sends card data entered into WebRezPro to the payment gateway, which encrypts the card data and sends the payment information to the payment processor. The payment processor then sends the approved or denied transaction response back to your payment gateway, which automatically delivers it to WebRezPro, authorizing the transfer of funds.
The integration stores tokens in place of card data, keeping guest credit card information out of your system to protect your business from liability. Using these tokens, you can charge credit cards on file for future payments through WebRezPro.*
*Please note: If 3D Secure is required, the option to store credit cards on file will not be available. The cardholder must enter a verification code every time the card is charged.
WebRezPro System Requirements
The First Atlantic Commerce integration requires the following:
- Confirmation of whether or not 3D Secure is required.
Please note: Neither WebRezPro nor First Atlantic Commerce determine if 3D Secure will be required. This is dictated by your bank or financial institution. - WebRezPro v10.5.28 or higher is required for integrations that do not require 3D Secure. WebRezPro v11.0.0 or higher is required for integrations that do require 3D Secure.
- Access to your First Atlantic Commerce payment gateway account.
Integration setup steps
- Contact your WebRezPro account executive to order the integration. A WebRezPro support specialist will email you to trigger the integration setup.
- You will need to complete the required account setup with First Atlantic Commerce and provide WebRezPro Support with the requested credentials from your payment gateway account, along with the date you would like the integration to go live.
- You will also need to confirm with your bank whether or not 3D Secure is required. Neither WebRezPro nor First Atlantic Commerce determine if 3D Secure will be required. This is dictated by your bank or financial institution.
Please note: If 3D Secure is required, guests will need to provide a verification code each time their credit card is charged. We strongly recommend configuring your guarantee policy in WebRezPro to automatically charge guests’ credit cards at time of booking for the full cost of the reservation as you will not be able to charge the guest’s credit card again until they are on site and able to provide the 3DS verification code for the payment. - Once we have received the required credentials for your payment gateway account, we will set up the integration in WebRezPro, ready for testing.
- On your requested go-live date, you will be required to participate in a 30-minute call (via Google Meet) to install and test the integration with WebRezPro Support. During this call, you will need:
- Access to your WebRezPro system
- Access to your First Atlantic Commerce payment gateway account
- A valid credit card (for testing)Card-on-file transactions (if applicable), payments, refunds, and authorizations (if applicable) will be tested during this process, guided by your WebRezPro support agent.
- When this testing is complete, WebRezPro Support will activate the integration.
Please note: Any existing cards on file for reservations made prior to the integration going live will need to be re-entered as new cards in order to be charged through the First Atlantic Commerce payment gateway. If you are using 3D Secure, credit cards cannot be added on file; you will need to re-enter the card information into WebRezPro at the time of payment, and guests must provide the 3DS verification code when the payment is processed.
Payments posted in WebRezPro prior to the integration going live cannot be refunded in WebRezPro. These payments must be refunded outside of WebRezPro, and a manual payment posted on the reservation for record-keeping purposes.
3D Secure is an additional layer of security for online credit and debit card transactions that requires the cardholder to authenticate their identity by entering a verification code at the time of payment. 3D Secure helps businesses reduce the risk of fraud and chargebacks and is required by some banking institutions. Your bank will confirm whether or not you need to use 3D Secure.
When 3D Secure is enabled, the guest must provide the 3DS verification code each time their credit card is charged, and the option to store and use credit cards on file will not be available.
When a payment or authorization is processed in WebRezPro, a 3D Secure modal will automatically open asking for the 3D Secure verification code. The cardholder will be notified of the transaction attempt and sent a 3DS verification code (usually via SMS). The cardholder must provide the verification code to the property so that the front desk agent can enter it into the 3D Secure modal to complete the transaction.
If the guest is booking online through the WebRezPro online booking engine and an automatic deposit is due at the time of booking, they will be prompted to enter the 3DS verification code when they submit their reservation/payment.
We strongly recommend configuring your guarantee policy in WebRezPro to automatically charge guests’ credit cards at time of booking for the full cost of the reservation as you will not be able to charge the guest’s credit card again until they are on site and able to provide the 3DS verification code for the payment.
Any existing cards on file for reservations made prior to the integration will need to be re-entered as new cards in order to be charged through the First Atlantic Commerce payment gateway integration.
If you are using 3D Secure, credit cards cannot be stored on file. You will need to contact the guest to obtain their credit card details and re-enter the card information into WebRezPro at the time of payment. Guests must provide the 3DS verification code when the payment is processed.
No, payments taken prior to the integration going live cannot be refunded through the integration. They must be refunded outside of WebRezPro (by cash or cheque, for example) and then manually posted to the reservation for record-keeping purposes.
If 3D Secure is not required, you can process payments for reservations received via GDS/OTA integrations using the credit card on file.
If 3D Secure is required, you will not be able to take payment for reservations received through GDS or OTA channels using the credit card on file. You will need to process the payment for these reservations when the guest is on site and able to provide the card information and 3DS verification code for the payment.
If 3D Secure is not required, you can use the virtual credit card added on file to process payment for an OTA/GDS reservation on or after the arrival date of the booking. Virtual credit cards are only valid on/after the reservation’s check-in date and are authorized for the room cost/taxes only (incidental charges incurred at the property must be paid directly by the guest).
If you are using 3D Secure and you receive virtual credit cards for GDS/OTA collect reservations, please contact your bank or financial institution to discuss options for charging these credit cards.
The First Atlantic Commerce integration does not currently support EMV.
Yes. If you would like to process authorizations through WebRezPro, WebRezPro Support can enable this for you.
If you are using 3D Secure and credit card authorizations are enabled, it is strongly recommended to set a default over-authorization amount to account for additional charges that may be incurred during the guest’s stay. The guest must provide the 3D Secure verification code at the time the authorization is added to the reservation.
WebRezPro does not control the length of validity for authorizations. For this reason, we recommend allowing credit card authorizations on the day of arrival. If credit card authorizations are enabled prior to arrival, it’s possible authorizations could be released prior to the guest’s check-in or check-out date.
No, First Atlantic Commerce does not support incremental authorizations (authorizations that automatically increase if the cost of the reservation is increased).
Yes. First Atlantic Commerce allows partial captures, but this feature must be enabled in your First Atlantic account. The amount captured can be equal to or less than the authorized amount. If you want to be able to process partial captures, reach out to First Atlantic Commerce to confirm/request that this feature is enabled.
Yes, this can be accommodated in the integration setup in WebRezPro. There are two ways to do this: a single payment gateway can be attached to all departments; or a separate payment gateway can be attached to each department.
