Skip to main content

​
The scenario

Acme Payments moves money for merchants. Marina Costa manages compliance, Rafael Souza is the engineer, Ana Ribeiro reviews cases. A merchant’s customer, Beatriz Nogueira, sends a 50,000 USD wire. The tenant’s rule Amount equals 50000 flags such transfers for review.

​
Part 1 — Marina prepares the tenant

1

Queues

Settings → Queues already has standard (default) and escalated; Marina adds high-value for the senior analysts.
2

Vocabulary

She adds the decline reason Source of funds unverified and the tags High Risk, PEP, VIP and SoF pending, and creates the Proof of address template.
3

Roles and people

In Team → Roles & Permissions she creates analyst, senior-analyst and engineer from the templates, then invites Rafael and Ana.

​
Part 2 — Rafael wires the integration

1

Data source and webhook

Data Sources shows the Frayme provider connected. In Settings → API he creates the webhook config docs-partner and stores its signing secret.
2

The flow

New Flow → Onboarding transaction review: Input → Integration (Frayme, Risk Score) → Assignment (risk_pct) → Rule → Split → Review in standard with a custom Escalate to senior action → a second Review in escalated → Approve / Deny. Result webhook is docs-partner.
3

Validate and activate

Validate flags an unwired timeout outcome; he wires it to Deny, saves and activates.
4

API key and a dry run

He creates the checkout-service key, then runs Submit case as a dry run and reads the Integration step’s evidence in Executions.

​
Part 3 — A case arrives

The merchant’s checkout service posts the transfer with the API key (Use the Case API). The risk lookup scores it in the review band; the case is parked in standard and case.pending_review reaches docs-partner.

​
Part 4 — Ana reviews

1

Claim and read

Ana presses Enter on the row, claims the case and reads Risk assessment and Data source results. She tags it High Risk and leaves a note.
2

Request information

She sends the Proof of address template. The case shows Awaiting customer information; the merchant’s systems email Beatriz.
3

Decide

The document arrives; Ana adds a note and approves. Because the score is high, Frayme asks Confirm High-Risk Approval.

​
Part 5 — The partner is notified

case.decided is delivered to docs-partner. Rafael confirms it in Webhook Delivery History and can resend if the merchant’s endpoint was down.

​
Part 6 — Marina oversees and corrects

Reviewing Cases → Approved, Marina disagrees: the proof of address did not cover the source of funds. She opens the case and uses Override decision to decline it with the reason Source of funds unverified. The timeline records the override and the merchant receives case.decision_overridden.