Implementation guide
PMS, accounting or no API.
Compare the operating trade-offs and rollout sequence.
Read the guideIntegration guides
Choose the lightest connection that solves the job.
Start from the operator workflow and implementation owner, then select a supported portal, PMS, accounting or AI-agent path.
Choose a connection path.
Use these paths to compare the product, operating model and next decision.
Connections
Explore supported routes.
Review portal, platform, accounting and AI-agent options.
Explore connectionsAI agents
Keep operator approval visible.
See workflows that prepare results without implying unattended authorisation.
Explore AI agentsIntegration is not the first question.
Confirm the pain, owners, data and success event before choosing an API or file path. A portal pilot can be more useful than a long integration that never reaches live payment volume.
Match connection depth to operating value.
A connection should remove a named handoff, preserve a reliable source of truth and give an owner a clear exception path. Confirm fields, permissions, error handling, reconciliation ownership and recovery before treating any integration as complete.
Start with the lightest supported route that can reach a live payment. Add PMS, accounting or AI-agent depth after the pilot shows where additional automation creates measurable value.
Bring CasaPay into your operation.
Start with the connected workflow your portfolio needs, then confirm market availability and terms during onboarding.