Transactions

Overview

The Transactions tab shows every payment Corgi Labs ingests from your payment provider, together with the risk evaluation behind it. For each payment, you can see which model evaluated it, the CORGI score, any rule that matched, and the final decision Corgi Labs applied.

Use the Transactions tab to:

• Look up a payment by customer email, IP address, payment ID, or last 4 digits of the card.

• Understand why a payment was allowed, blocked, reviewed, or sent to 3DS.

• During CORGI model ramp-up, compare CORGI model results with your existing provider while CORGI model evaluates part of your traffic.

Payments sync from your payment provider about every 2 hours. The Last synced time under the page title shows when the most recent sync ran.

How Corgi Labs evaluates a payment

Each risk column in the Transactions tab reflects one step of the evaluation pipeline, in this order:

1. Traffic split. During a phased rollout, each eligible payment is routed to either CORGI model or your existing provider (for example, Stripe Radar). The model a payment is routed to is its live model, and only the live model's decision counts. The Traffic split column shows which one it was, or None if the payment was outside the phased rollout.

2. CORGI score. CORGI model scores the payment from 0 to 100. The icon next to the score shows whether the score falls on the Allow or Block side of your block threshold. CORGI model also scores payments when it isn't the live model, so you can compare it with your existing provider. These scores carry a Shadow tag and have no effect on the payment decision.

3. Model decision. The Allow or Block decision of the live model shown in the Traffic split column:

• For CORGI model traffic, Model decision is the CORGI score compared with your block threshold, so it matches the CORGI score icon.
• For Stripe Radar traffic, Model decision is Stripe Radar's decision, even when the CORGI score suggests a different outcome. Block means Stripe Radar rated the payment highest risk.
• When the live model doesn't return a verdict, or Traffic split is None, Model decision shows Not evaluated.

1. Rule match. Rule Engine evaluates your rules against the payment. A matched Rule Engine rule overrides the live model decision and appears in the Rule match column. If no rule applies, the column shows No match and the live model decision stands. Rule match can also show a match from one of your Stripe Radar rules. Stripe Radar applies those rules itself, so they don't change Final decision.

2. Final decision. The action Corgi Labs applied to the payment, after the model decision and any matched rule. This appears in the Final decision column. If Rule Engine never made a decision for the payment, the column shows None.

When CORGI model evaluates 100% of your eligible traffic, every eligible payment shows CORGI model in the Traffic split column. The phased rollout columns are most useful while you are ramping up CORGI model on a portion of your traffic (for example, 30% or 70%).

Shadow scoring

During shadow testing, or for payments not assigned to CORGI model during a staged rollout, CORGI model still scores the payment. These scores appear with a Shadow tag. A shadow score lets you see what CORGI model would have decided without affecting the live outcome.

Transaction table

The transaction table has two groups of columns: payment details on the left and risk evaluation on the right.

Payment details

Risk evaluation

Select any row to open the transaction details page for that payment. The details page shows the payment's lifecycle, its CORGI and Stripe Radar scores, the rules that matched, and card and customer signals.

Status tabs

Tabs above the table group payments by outcome. Each count updates to match your current date range. Search and column filters don't change the counts.

Selecting a status tab, such as Blocked, also sets the Status filter. You can combine a status tab with other column filters. For example, selecting the Disputed tab and filtering Traffic split to Stripe Radar shows only disputed payments from Stripe Radar traffic.

Decisions and rule overrides

Final decision combines the model decision with your rules, following the Rule Engine evaluation order:

1. Request 3DS rules are evaluated first.

2. Allow rules.

3. Block rules.

4. Review rules are evaluated last.

If a rule matches, its action can change the final outcome. The type of rule determines whether the override icon appears.

Override icon

The override icon appears next to Model decision only when an Allow or Block rule reversed the model decision. For example, if the model returned Block but an Allow rule matched, you see the override icon next to the model's Block and the Final decision column shows Allow. Hover over the icon to see which rule overrode the model decision. To list only these payments, open the Model decision filter and select Rule override only.

Review and Request 3DS rules never show the override icon. When they change the outcome, Final decision differs from Model decision, but no icon marks the change. This is because Review and Request 3DS add a step rather than reversing the model's allow-or-block judgment.

For details on creating and managing rules, see Rule Engine.

Search and filter transactions

Use the date range picker to choose a preset, such as Last 30 days, or a custom range. The default is Last 3 months. Use the search box to find payments by customer email, IP address, payment ID, or last 4 digits of the card.

You can narrow the transaction list further using column filters. Most column headers have a filter icon that opens a list of available values. The Amount, CORGI score, and Date filters also let you sort, and the Amount filter lets you set an amount range and currency.

How filters work

• Within a column: each filter takes one value at a time, except Status. In the Status filter, selecting multiple values shows payments that match any of them (OR logic). For example, filtering Status to Refunded and Disputed shows payments that were refunded or disputed.

• Across columns: filters on different columns combine, so each filter you add narrows the list (AND logic). For example, filtering Traffic split to CORGI model and Rule match to Block shows only CORGI model payments where a Block rule matched.

• Bookmarkable: your search, status tab, and column filters are saved in the page URL, so you can bookmark or share a filtered view with your team. The date range isn't saved in the URL, so a shared link opens with the default date range (Last 3 months).

Export and choose columns

To download transactions as a CSV file, open the More options menu (⋮) next to the search box and select Export CSV. To show or hide columns, open the same menu and select Columns.

See what each model decided

These filter combinations help you isolate traffic by model and outcome:

To find payments blocked in Stripe Radar traffic, use the Blocked tab rather than Final decision: Block. Final decision shows only Corgi Labs' decision, so it doesn't include payments that Stripe Radar blocked natively.

Compare CORGI model with Stripe Radar

During ramp-up, you can use these filter combinations to compare what CORGI model would have done versus what Stripe Radar actually did:

In the CORGI score filter, CORGI model decision shows what CORGI model decided, or would have decided, for each payment: Allow, Block, or No score.

These comparisons are most valuable during a phased rollout, when both models are evaluating live traffic and you can measure the difference in outcomes.