This article serves as a one page reference for CSOPs during their first few weeks and applies to all support levels supporting the Digital Authorization (eAuthorization) product.
What Does the eAuthorization Product Do?
Sertifi’s eAuthorization solution allows a hotel to send a digital credit card authorization form to a client in order to securely collect payment details ahead of a stay.
Once the form is completed:
Credit card details are securely tokenized
Authorized Admins can unmask the card details at a later date
The hotel can charge the card based on the authorization provided
This workflow replaces faxed or emailed authorization forms and improves payment security and audit traceability.
Required Settings for eAuthorization to Function
All of the following settings must be configured correctly for eAuthorization to work as expected.
Payment Settings Enabled
Payment Settings must be enabled for the Payments section to appear in the portal.
Administration → Account Settings → Payment Settings
If Payment Settings are disabled, eAuthorization functionality will not be available.
Payment Gateway Configuration
A Payment Gateway must be configured.
Administration → Account Settings → Payment Settings → Gateways & Rules
Minimum requirements:
A default payment method must be set
CC must be selected as an available option
Important notes:
Credit Cards are required for eAuthorization
ACH cannot be used for pre authorization via eAuth
Document Library Visibility
The Document Library must be visible for the Credit Card Authorization form to appear as a sending option.
Administration → Account Settings → Sending Page Default → Document Library → Show
If set to Hide, the CC Authorization form will not be available when sending documents.
Security Group Configuration
Admins must belong to a Security Group that allows viewing unmasked credit card details.
Most commonly used Security Group:
Can View Unmasked CC
Administration → Account Settings → Security Groups
Without this Security Group, Admins cannot view card details even if eAuthorization is otherwise configured correctly.
SkyFlow Configuration
SkyFlow controls how long credit card details are retained and viewable within the portal.
Administration → Account Settings → Integrations → SkyFlow
Requirements:
SkyFlow must be enabled
The retention value must be greater than 0
Key behavior:
Card details are only viewable for the configured number of days
Once the retention period expires, card details can no longer be viewed
SkyFlow settings are not retroactive
Key Takeaways for Support
eAuthorization requires Payment Settings, a Payment Gateway, Document Library visibility, Security Group access, and SkyFlow
Missing any one of these settings will prevent proper eAuth functionality
Most visibility issues are caused by Security Group or SkyFlow configuration
ACH is not supported for eAuthorization workflows
Comments
0 comments
Please sign in to leave a comment.