Sign in required

Sign in with your Aidaptive or Deuna Google account.

Access Denied

Your email is not authorized. Use an @aidaptive.com or @deuna.com account.

Aidaptive x Deuna

GetNet

ML Performance
Navigation
←Back to Hub
Experiment Performance
📈By Model Version 🎯By Processor ⚙Model vs Heuristic — AR ⚖Model vs Heuristic — DR
Platform Health
📈Approval Correlations ●Daily AR — aggregate ◉Daily AR — per merchant
Model Quality & PSP
🔬Model Quality 🚩PSP Error Analysis
Other Dashboards
🔍PSP Analysis (detailed) ↗ 📊Getnet Analysis ↗ ★Volaris ↗
Data as of 2026-08-14
Last run: 2026-08-14 09:03 PDT
Source: Snowflake PAYMENT_ML
Aidaptive x Deuna › Getnet · PROSA Correlations
Auto-refreshed  ·  15 min
📊Approval Rate by Model Version
Scoped to experiment —. One line per MODEL_VERSION — every getnet_psp_router:* release plus the heuristic-v0 baseline. Shadow-mode predictions ARE included so we get signal during the still-in-shadow rollout — the model line reflects what the router would have chosen if it had routed live.
ℹ Shadow-mode preview — model predictions included even where the router did not route live. Useful for validating model quality before flipping traffic; will look identical to live once traffic is flipped.
Comparison cohort Loading…
Hourly Approval Rate by Model Version (past 24h)
Loading…
Daily Approval Rate by Model Version (14-day)
Loading…
Daily AR Delta — Model vs Heuristic (14-day)
Loading…
Daily AR Delta — Model vs Heuristic - Weekly
Loading…
🎯Daily Approval Rate by Model — Per Processor
Same experiment, split by the downstream PSP the router selected (PREDICTED_VALUE in ATHIA_FEEDBACK). Bars = volume, lines = approval rate. One card per processor discovered in the last 14 days — no hardcoded processor list.
Daily Approval Rate by Model — Per Processor
Loading…
⚙Daily Approval Rate — Model vs Heuristic (14-day)
Shadow-mode traffic is excluded. Charts count only predictions where response_payload.is_shadow_mode = false — i.e. decisions that actually influenced routing. Experiment —. Bars = daily volume (right axis). Lines = approval rate (left axis, 0–100%).
ℹ
⚠ ML pipeline health
Comparison cohort Loading…
Model — 14d
—
— txns · — approved
Heuristic — 14d
—
— txns · — approved
Δ AR (Model − Heuristic)
—
last refresh —
Daily Approval Rate by Model (processed / total)
⚙Daily Decline Rate — Model vs Heuristic (14-day)
Same experiment, denied ÷ total. Bars = daily volume. Lines = decline rate (0–100%).
Model — 14d
—
— txns · — denied
Heuristic — 14d
—
— txns · — denied
Δ DR (Model − Heuristic)
—
lower is better
Daily Decline Rate by Model (denied / total)
📈Approval Correlations by Model
For each Getnet model, correlate its declared feature set against APPROVED over the last 30 days of PAYMENT_ML.ABTESTING.GETNET_PROSA_MCO_TRAINING_DATA. Numerics use Pearson r², categoricals use η² — both [0,1], higher = stronger signal. Feature lists come from data/getnet_*_features.txt. Refreshed every 15 min.
Sample size (30d)
—
rows analyzed
Overall approval rate
—
baseline
Active model
—
last refresh —
PSP Router — top features by association strength
Loading…
Loading…

13 declared features · hover a feature name for its meaning · click a row to see the top-5 values with approval-rate lift.

PROSA MCO — top features by association strength
Loading…
Loading…

49 declared features · hover a feature name for its meaning · click a row to see the top-5 values with approval-rate lift.

Looking for decline taxonomy, fixable-decline analysis, merchant breakdowns, etc.? See Getnet Analysis (detailed) →

📈Daily Approval Rate — Aggregate (14-day)
Single-line daily approval rate across all Getnet merchants in PAYMENT_ML.ABTESTING.GETNET_PROSA_MCO_TRAINING_DATA. Sanity check for platform-wide trend and outages.
Daily Approval Rate (14-day) — all merchants
Loading…
🎯Daily Approval Rate — per Merchant (14-day)
One line per Getnet merchant that had at least 100 transactions in the last 14 days. Same series as the aggregate chart above, just decomposed.
Daily Approval Rate (14-day) — per merchant
Loading…
🔬Model Quality — historical training runs
Per-training-run quality metrics for the getnet_psp_router models (dnn, gbdt, logreg) across the three downstream PSPs (cybersource, getnet, prosa). Source: —. Pick a metric to compare all archs side-by-side per PSP — click a legend entry to hide/show that arch. Line = per-training-run metric, faded bars = training-set size (right axis) so you can eyeball whether a spike is a real improvement or a small-sample fluke. Use the Version dropdown to pin the score cards, Radar, and Best-Arch table to a specific version across all 3 architectures (default = latest).
Metric
Version
Loading…
Version-over-Version Metric Delta
Architecture Comparison — Radar (latest)
Training Data Size vs Metric — Scatter
Best Architecture per PSP (latest)
Precision-Recall Tradeoff
Drill-down
🚩PSP Error-Code Analysis (30-day)
Cross-PSP volume + approval + decline-code breakdown across the 8-merchant GetNet cohort. Fed by an hourly upstream cron in DATA-Athena-Snowflake that writes CSVs the portal syncs each refresh. Full drill-down + tables: Explore PSP Analysis →
ℹ
Per-PSP volume + approval
Loading…

For (PSP × Brand) approval, decline categories, retry counterfactual and the full markdown summary, open the dedicated PSP Analysis page →