ComplianceIntegration checklist
Integration checklist
Day-one compliance checklist for new integrations on conomy_hq.
A practical checklist for integrating compliance correctly the first time. Each item is paired with the page that explains the underlying mechanism.
Customer records
Section titled “Customer records”- Create a
Customerfor every end user on first interaction. See Customers. - Surface
autoCreated: truerecords in your operator dashboard so the team can complete missing data. - Promote
operationLevel(PATCH /customers/{id}) when documentation is approved. See Customer operation levels. - Subscribe to
customer.levelChangedto keep your local state synced.
Documentation flow
Section titled “Documentation flow”- Subscribe to
payment.requiresReviewand route the event to the operator dashboard within minutes. - Build a UI that lets the operator (or end user) attach the requested document via
POST /payments/{id}/documents. See Supported documents. - Subscribe to
payment.reviewApprovedandpayment.reviewRejectedso your dashboard reflects the resolution. - Reflect
documentationStatuson the payment view:PENDING_UPLOAD,UPLOADED,APPROVED,REJECTED.
Limits
Section titled “Limits”- Confirm with
conomy_hqthe configured review threshold per currency. - Confirm the configured minimum amount per rail.
- Confirm the configured per-tier amount limits and reflect them in your UX (e.g. show the user the cap before they submit a request).
See Transaction limits.
Day-two operations
Section titled “Day-two operations”- Reconcile your customer records weekly: any
autoCreated: truecustomer that has been transacting should be reviewed and promoted. - Audit
REQUIRES_REVIEWpayments older than 24 hours and chase the document upload. - Track refund volume from
REJECTEDreviews — sustained spikes signal a documentation UX issue.
Final compliance check before going live
Section titled “Final compliance check before going live”- End-to-end test in sandbox: customer creation → topup that triggers review → document upload → operator approval → settlement.
- End-to-end test in sandbox: customer creation → topup that triggers review → operator rejection → automatic refund visible.
- Webhook handler verified for every compliance event:
payment.requiresReview,payment.reviewApproved,payment.reviewRejected,customer.levelChanged. - Operator dashboard escalates blocked payments to a human within an SLA you have committed to (we recommend ≤ 4 hours).