Skip to content
Back to challenges
Company Tracks: Netflix-style and Stripe-styleConcept Challengeintermediate30 minPro

Stripe payment attempts

Model a payment-attempt event fact that captures every attempt and its status, not just successful charges.

How this preview works
Preview this problem before signing in. Sign in to save progress and submit work.

Concept

fact-table-grain

The primary modeling idea this problem reinforces.

Requirements

0

Business needs the model must satisfy.

Read the concept guide: Fact table grain
Scenario

A payments team wants failure and retry analytics, not just successful charges. Attempts move through created, processing, succeeded, and failed. The account and payment-method dimensions already exist.

Why this matters

A successful-charges-only table hides failures and retries. An attempt-grain event fact with a status captures the whole lifecycle and supports authorization-rate and retry analysis.

Requirements
    Read-only starter workspace
    Inspect the authored starting ERD, then open the workspace to edit and run the checks. Saving your progress needs a free account.

    Template

    The model users start from in the full workspace.

    Entities

    0

    Seeded tables visible in the public preview.

    Dialect

    postgresql

    Generated SQL target for this starter model.

    Mini Map

    This preview is read-only. Open the workspace to edit and verify; saving needs a free account.

    Open workspace

    Try the question first.

    The discussion has other people's approaches and solutions. Give it a real attempt before you read them.