Security & Funds Safeguarding

1. Overview

ArosaPay operates a protected payment mechanism in which buyer funds are captured at checkout, held by our licensed payment partner, and released only upon buyer approval or dispute resolution.

This page outlines:

• How funds are handled
• How access is controlled
• How transaction integrity is maintained
• How platform security is enforced

2. Funds Handling Framework

2.1 Custody Model

When a buyer completes payment:

• Funds are captured and recorded in the Secured Transaction Ledger.
• The merchant cannot access funds immediately.
• Funds remain held in custody until buyer approval or dispute resolution.
• Funds are released only when predefined transaction conditions are met.

2.2 Segregation of Funds

Held funds are:

• Recorded separately from platform operating revenue
• Not treated as platform income
• Not available for operational expenses

Internal ledger systems distinguish between:

• Secured transaction funds
• Merchant payable balances
• Platform service fees
• Operational accounts

This separation ensures transaction-level clarity and auditability.

2.3 Payout Controls

Merchant payouts are:

• Triggered only after transaction approval
• Subject to tier-based reserve policies
• Logged and traceable

Reserve balances, where applicable, are retained according to defined hold periods and automatically released when conditions are satisfied.

3. Ledger & Transaction Integrity

3.1 Immutable Ledger Architecture

All transaction events generate structured ledger entries. Each entry includes:

• Unique identifier
• Timestamp
• Event type
• Actor
• Amount
• Trace reference

Balances are derived from ledger entries and are not manually editable.

3.2 Idempotent Processing

To prevent duplicate processing:

• All payment requests use idempotency keys
• Webhooks are validated and de-duplicated
• Retry logic does not create duplicate ledger entries

This ensures financial accuracy even under network interruptions.

4. Access Controls & Administrative Governance

4.1 Role-Based Access Control (RBAC)

Internal systems restrict access based on role:

• Operations
• Risk & Compliance
• Engineering
• Support

Administrative permissions are limited to minimum necessary access.

4.2 Dual-Control Requirements

Certain actions require dual authorization, including:

• Manual fund release overrides
• Tier policy adjustments
• Payout destination changes
• Emergency account freezes

All such actions are audit-logged.

4.3 Audit Logging

Administrative and system-level actions are:

• Logged
• Time-stamped
• Attributed to specific accounts
• Non-editable

Audit trails are retained for compliance review and internal monitoring.

5. Data Security & Encryption

5.1 Data Transmission

All data in transit is encrypted using industry-standard TLS protocols.

5.2 Data Storage

Sensitive data is:

• Encrypted at rest
• Segmented by service
• Accessible only through authenticated service layers

Direct database access is restricted and monitored.

5.3 Credential Protection

Authentication systems include:

• Secure session handling
• Multi-factor authentication (where applicable)
• Rate limiting and anomaly detection

Passwords are not stored in plaintext.

6. Fraud Monitoring & Risk Controls

ArosaPay monitors transaction patterns in real time to detect:

• Abnormal dispute spikes
• Repeated failed delivery patterns
• Unusual transaction velocity
• Suspicious review activity
• Linked account behavior

Flagged accounts may be:

• Temporarily restricted
• Subject to additional verification
• Escalated for manual review

7. Incident Management

In the event of a system disruption or security incident:

• Incident response protocols are activated
• Access logs are reviewed
• Affected systems are isolated if necessary
• Service status updates may be published

Critical issues are escalated internally with defined response timelines.

8. Dispute Protection & Fund Freeze Mechanism

When a dispute is opened:

• Funds remain secured
• Release is paused
• Payout processing is suspended
• Evidence collection begins

No automatic release occurs while a dispute is active.

9. Business Continuity

ArosaPay maintains:

• Secure backups
• Redundant infrastructure components
• Failover procedures for critical services

Operational continuity planning is reviewed periodically.

10. Limitations

ArosaPay:

• Protects transactions processed through its system
• Does not insure off-platform agreements
• Does not guarantee delivery performance
• Does not provide legal arbitration services

Protection applies only to the secured transaction amount.

11. Transparency & Reporting

Performance metrics and safeguarding mechanisms are:

• Defined in published methodology
• Updated regularly
• Based on transaction-level data

ArosaPay does not modify metrics for commercial benefit.

12. Contact & Reporting Concerns

Security inquiries or vulnerability reports may be submitted to:

security@arosapay.com