System integrators and backend developers
Mapping out payment API integrations for a new property management system deployment.
Casos de uso
Acerca de
The Credit Card Processing mind map template provides a structured overview of payment operations across four major hospitality systems: Occ Map, Booking Engine, GDS, and Webervations. With 89 nodes organized into a matrix of system types and transaction methods, it maps out five core actions—Charge, Refund, Authorization, Capture, and Hold—for each combination of HAPI integration (Throughout, BE Only, Non-Hapi) and token acceptance. This template serves as a cheat sheet for developers and system integrators configuring payment flows in property management and booking platforms. It visually distinguishes between HAPI Throughout, Non-Hapi, HAPI BE Only, and Accept HAPI Tokens scenarios, making it easy to identify which transaction types are supported per integration path.
Términos y condicionesCuándo usar esta plantilla
Product managers and QA engineers
Auditing existing payment flows across multiple booking channels to identify gaps in transaction support.
Onboarding leads and technical trainers
Training new team members on the supported payment actions for each integration type.
Cómo usar esta plantilla
Paso 1
Open Template and Select System
Launch the Xmind file and expand the specific branch for the hospitality system you are currently configuring, such as Occ Map or GDS.
Paso 2
Map Integration and Transaction Details
Review the integration paths and transaction actions while adding technical notes or task markers to document your API configuration progress.
Paso 3
Export and Share Technical Documentation
Save your customized payment flow and export the map as an image or PDF to provide a clear reference for your development team.
Preguntas frecuentes
The template covers payment actions (Charge, Refund, Authorization, Capture, Hold) across four systems: Occ Map, Booking Engine, GDS, and Webervations. Each system is further divided by integration type: HAPI Throughout, Non-Hapi, HAPI BE Only, and Accept HAPI Tokens.
Open the .xmind file in Xmind. Navigate to the relevant system branch (e.g., Occ Map) and integration type (e.g., HAPI Throughout). Use the listed actions as a checklist to ensure your implementation supports the required transactions.
Yes, the template is fully editable in Xmind. You can add notes, icons, or new branches to customize it for your specific property management or booking system setup.
HAPI Throughout indicates the HAPI integration is used for all transaction types, while HAPI BE Only means HAPI is used only for back-end processing. The template lists the same five actions under both, but the actual API endpoints may differ.
While designed for hospitality systems (Occ Map, Booking Engine, GDS, Webervations), the structure can be adapted for any payment processing workflow by renaming branches and actions.
¿Tienes una plantilla inspiradora?
Comparte tus plantillas de mapas mentales con creadores de todo el mundo y empieza a ganar con tu trabajo.
Plantilla gratis