Access
Limit who can act.
Define operator roles, approval boundaries and the people authorised to change payout settings.
Security and compliance
This page explains the control areas CasaPay and an operator should review. It does not substitute for signed terms, technical due diligence or market-specific legal advice.
Use these paths to compare the product, operating model and next decision.
Access
Define operator roles, approval boundaries and the people authorised to change payout settings.
Data
Keep tenancy evidence and payment-service identity checks distinct, with agreed retention and access rules.
Events
Map requested, pending, paid, failed, allocated and settled events precisely.
Review payment statesAn operator assessment should identify what personal and payment data enters CasaPay, which systems receive it, who can access it and how long it is retained. The answer can vary by market, integration and enabled module.
Do not infer a regulatory status, safeguarding arrangement or security certification from marketing copy. Request the current legal-entity, processor and control documentation during due diligence.
AI-agent and integration workflows should preserve the difference between preparing a request and approving or sending it. Payment and payout permissions should follow the agreed role model.
Audit needs include the actor, event, timestamp, amount, reference and relevant status transition. The final implementation scope must be confirmed with CasaPay.
Deposit rules, tenancy fees, payment surcharges, consumer protection and guarantee language differ by jurisdiction. A global statement cannot replace local review.
CasaPay maintains market-qualified language and should publish a dated claims register before broad regional promotion.
No. Only current evidence supplied during due diligence should be used to confirm a certification or audit status.
Use only the approved legal-entity and regulatory wording in the applicable agreement. This page intentionally does not make an unsupported blanket claim.
The current illustrated workflow prepares a request and stops for operator approval. Production permissions depend on the agreed implementation.
Start with the connected workflow your portfolio needs, then confirm market availability and terms during onboarding.