Connections
Explore CasaPay integrations.
Review current connection categories.
Explore connectionsIntegration guide
PMS, accounting system or no API: choose the right path.
Start from the workflow and success event, then select the lightest supported connection that can reach live rent payments reliably.
Portal or no-API workflow.
The operator portal can prove the request, payment, reconciliation and payout process without waiting for a deep technical project. It is useful for a bounded pilot or an operation with manageable volume.
Define how tenant and accounting data enters and leaves the process, who owns manual checks and what volume would justify deeper connection.
Property-management system connection.
A PMS connection can reduce duplicate data entry and keep tenancy or property context aligned. The exact objects, direction, frequency and supported platform depend on the implementation.
Confirm the source of truth, field mapping, identifier strategy, error queue, retry behaviour and process when the connection is unavailable. Avoid promising a named integration until it is live and approved.
Accounting connection.
Accounting workflows may use exports, file transfer or supported direct connections. Define when a payment is ready for posting and how fees, refunds, partial payments, allocations and reversals appear.
Reconciliation in CasaPay and posting in the accounting system are related but distinct. Test the real chart of accounts, entities and close process.
AI-agent workflow through MCP.
CasaPay can expose approved workflows to supported AI tools and agents through MCP. The current operator illustration shows the agent preparing a request and stopping for review.
Do not assume compatibility with every AI tool or unattended authorisation. Define permissions, approval, audit events and failure handling for each scenario.
A staged implementation plan.
Stage one confirms the operator, market, entity and payment route. Stage two reaches a live request and successful settlement. Stage three stabilises reconciliation and exceptions. Stage four adds the connection that removes measured work.
Use real activation and TPV evidence to decide whether to expand the integration scope.
| Path | Best starting point | Operator responsibility | Expansion signal |
|---|---|---|---|
| Portal or no API | Bounded pilot or manageable volume | Own data entry, review and export | Repeated manual handoff with measurable cost |
| PMS connection | Tenancy and property context must stay aligned | Own field mapping and error queue | Duplicate entry limits activation |
| Accounting connection | Posting and close workflow need structured output | Own chart-of-accounts and exception rules | File handling creates material close work |
| AI agent through MCP | Approved tasks can be prepared in chat | Own permissions, review and audit policy | Stable workflow with clear approval boundaries |
Questions operators ask.
Do we need an API to start?
No. The operator portal or an agreed no-API workflow can support a pilot.
Does CasaPay integrate with every PMS?
No. Supported platforms and depth must be confirmed during onboarding.
Can an AI agent send a RentLink automatically?
The current illustrated workflow prepares a request and stops for operator approval. Production permissions depend on the implementation.
What should happen if an integration fails?
The process should surface the failure, preserve the source event and give an owner a documented recovery path.
Bring CasaPay into your operation.
Start with the connected workflow your portfolio needs, then confirm market availability and terms during onboarding.