What the iframe shows

Authentication gets the member a session. A second, separate choice decides which screen that session opens on.

That choice is the useCase claim, and it works the same way whichever authentication path you use. On the JWT path it is a claim in the token you sign. On the SAML path it is the UseCase attribute (or User.UseCase) in the assertion. Both default to the intake flow when absent.

The three values

• intake — start a new dispute. The member picks a transaction, answers the questionnaire, and files. This is the default.
• status — the member's disputes, past and in flight.
• landing — a home screen offering both.

Any other value is treated as intake, so a typo opens intake rather than failing.

landing can be turned off for your organization. When it is, a session asking for it is quietly downgraded and the member lands elsewhere. If you send landing and see the create flow, that is the reason, not a bad claim.

It overrides the URL you open

The iframe reads useCase from the session and redirects to the matching flow, whichever URL you loaded. A session with useCase: intake opened at the landing URL goes to the create flow; status goes to history.

So the URL alone does not decide what the member sees. Set both, and set them to agree.

Opening on a transaction you already chose

To open the flow on a transaction the member already tapped, call Create Intake Case with that transaction before you authenticate. It returns an intakeCaseId. Pass it as the intakeRef claim alongside useCase: intake, and the flow opens with that transaction already selected.

Identify the customer with customer.uuid and name the transaction with transactionId.

Opening one specific dispute

To take the member straight to a single dispute, send useCase: status together with disputeId.

disputeId must be a valid UUID. Anything else is ignored without an error, and the member lands on the dispute list instead — so if a deep link quietly goes to the wrong screen, check the value you sent.

A note on OIDC

The OIDC path does not carry useCase. Sessions created that way open on the default flow. If you need deep links into status or a specific dispute, use the JWT or SAML path.