Task Flow Mickael Rutembya · Flow Atlas

Payment Return

/paiement/return/

Atomic steps for a user to return from payment provider and confirm order status.

Task intent

What the user is trying to do

« Return from the payment provider and confirm that the payment was successful. »

Entry points

ElementDestination
Payment provider Return URL/paiement/return/
Browser back After payment/paiement/return/
Direct link From confirmation email/paiement/return/

Flow

Adjacent routes — click a node to open it.taskflow
flowchart TD A["Start: user returns from provider"] --> B["/paiement/return/"] B --> C["Validate payment status"] C --> D{"Payment confirmed?"} D -->|Yes| E["Show success and receipt"] E --> F["End: order active"] D -->|No| G["Show error and support link"] G --> H["/contact/"] H --> F click B "https://mickael-umt.com/paiement/return/" "Open Return" click F "https://mickael-umt.com/paiement/confirmation/" "Open Confirmation" click H "https://mickael-umt.com/contact/" "Open Contact"

Step inventory

IDStepActionSystem state
S1ReturnNavigate to return URLPayment status fetched
S2ValidateConfirm transaction with providerStatus verified
S3DisplayShow result to userOrder updated

Flow scenario

Scenario PR1

User confirms successful payment

Trigger

  • User completes payment on provider page
  • Provider redirects to return URL

Experience

  1. Return page loads and validates payment.
  2. Success message and receipt are shown.
  3. Order is marked as paid.

Trust and safety rules

  • Return URL validates payment server-side.
  • No sensitive data is exposed in URL parameters.
  • Failed payments are logged for support.

Interaction rules

  • Validation is atomic; no double-processing.
  • Receipt is emailed regardless of page reload.
  • Support link available for discrepancies.

Result states

StateWhat the user seesWhat happens next
SuccessSuccess message and receiptOrder is active
FailureError message and support linkUser contacts support