Task Flow Mickael Rutembya · Flow Atlas

Payment Cancelled

Atomic steps for a user who cancelled payment and wants to retry or contact support.

Task intent

What the user is trying to do

« Understand why payment was cancelled and decide to retry or get help. »

Entry points

Element	Destination
Payment provider Cancel URL	`/paiement/cancelled/`
Payment page Cancel button	`/paiement/cancelled/`
Direct link From notification	`/paiement/cancelled/`

Flow

Adjacent routes — click a node to open it.taskflow

flowchart TD A["Start: user cancels payment"] --> B["/paiement/cancelled/"] B --> C["Show cancellation reason"] C --> D{"Next action?"} D -->|Retry| E["/paiement/"] D -->|Support| F["/contact/"] D -->|Home| G["/"] E --> H["End: retry payment"] F --> H G --> H click B "https://mickael-umt.com/paiement/cancelled/" "Open Cancelled" click E "https://mickael-umt.com/paiement/" "Open Payment" click F "https://mickael-umt.com/contact/" "Open Contact" click G "https://mickael-umt.com/" "Open Home" click H "https://mickael-umt.com/paiement/" "Open Payment"

Step inventory

ID	Step	Action	System state
S1	Open cancelled	Navigate to cancelled page	Order state loaded
S2	Review reason	Read cancellation context	No state change
S3	Act	Retry, contact, or leave	Navigation intent

Flow scenario

Scenario PC2

User aborts payment and retries

Trigger

User clicks cancel on payment provider
Provider redirects to cancelled URL

Experience

Cancelled page loads with reason and options.
User clicks retry and returns to payment.
Completes payment successfully.

Trust and safety rules

Cancellation reason is logged for support.
Order is not marked as paid.
Retry link preserves order context.

Interaction rules

Clear CTA to retry payment.
Support link available for issues.
No sensitive data exposed on cancelled page.

Result states

State	What the user sees	What happens next
Cancelled	Cancellation message and options	User retries or contacts support
Retry	Payment form	User completes payment