Four-Eyes Governance (Maker-Checker)

To satisfy institutional security and banking regulations, Depa enforces Four-Eyes Principles (Maker-Checker). Under this policy, high-value transfers initiated by one user ("Maker") cannot be executed until approved by a second qualified user ("Checker").

1. Configuring Four-Eyes PoliciesCopy Anchor Link

Policies cover fiat payments or blockchain payments, at vault or customer level. List the policies that apply to you:

curl https://sandbox.depasify.com/api/v1/four_eyes_policies \
  -H "Authorization: Bearer <admin_token>"

Then set the EUR threshold from which payments need approval:

RequestCopy Anchor Link

curl -X PUT https://sandbox.depasify.com/api/v1/four_eyes_policies/2d7f4a1c-9e3b-4c8a-a5d6-1f0b8e3c7a29 \
  -H "Authorization: Bearer <admin_token>" \
  -H "Content-Type: application/json" \
  -d '{ "threshold_eur": 50000 }'

2. The Maker-Checker WorkflowCopy Anchor Link

1. Maker creates the payment: a user initiates an outgoing payment of EUR 75,000. Because it exceeds the EUR 50,000 threshold, it's created as pending_approval.
2. Checkers review it: other users approve it with POST …/fiat_payments/{id}/approve (or …/blockchain_payments/{id}/approve), or reject it. Each user can review a payment once, and approval_progress shows the count, for example 1/2.
3. Execution: once it has enough approvals, the payment moves to ready_to_release and is sent. The payment records who initiated, approved or rejected it in initiated_by, approved_by and rejected_by.