Skip to content

docs: add Arazzo workflow documentation for Open Payments API flows#773

Open
flarcos wants to merge 1 commit intointerledger:mainfrom
flarcos:arazzo-documentation
Open

docs: add Arazzo workflow documentation for Open Payments API flows#773
flarcos wants to merge 1 commit intointerledger:mainfrom
flarcos:arazzo-documentation

Conversation

@flarcos
Copy link
Copy Markdown

@flarcos flarcos commented Mar 31, 2026

Summary

This PR adds machine-readable API workflow documentation using the Arazzo Specification v1.0.1 for the core Open Payments flows.

What is Arazzo?

Arazzo is an OpenAPI Initiative specification for describing sequences of API calls and their dependencies. It sits alongside OpenAPI but focuses on workflows — how multiple API operations chain together to achieve a business outcome.

Workflows Documented

File Flow Steps
one-time-payment-fixed-receive.arazzo.yaml E-commerce checkout (fixed receive amount) 9
one-time-payment-fixed-send.arazzo.yaml Remittance (fixed send/debit amount) 9
recurring-payment.arazzo.yaml Subscription with interval-based GNAP grants 9
transaction-history.arazzo.yaml Listing & retrieving payment records 3 workflows
token-management.arazzo.yaml Token rotation, revocation, grant cancellation 3 workflows

Key Features

  • Spec-compliant: All documents conform to Arazzo v1.0.1
  • Source references: All operationId references resolve against the OpenAPI specs in open-payments-specifications/openapi/
  • Runtime expressions: Steps use $inputs.*, $steps.*.outputs.*, and $response.body.* to define data flow between API calls
  • Success criteria: Every step includes successCriteria assertions
  • Comprehensive: Covers the full Open Payments lifecycle — grants, incoming payments, quotes, outgoing payments, token management

How It Helps

  1. Developer onboarding — understand flows from a single structured document
  2. Tooling — enables automated testing, mock generation, and SDK scaffolding
  3. Interoperability testing — ASE implementers can validate compliance
  4. Standards adoption — one of the first production Arazzo implementations for a financial API

References

Add machine-readable API workflow definitions using the Arazzo
Specification v1.0.1 for the core Open Payments flows:

- one-time-payment-fixed-receive: e-commerce checkout (9 steps)
- one-time-payment-fixed-send: remittance pattern (9 steps)
- recurring-payment: subscription with interval grants (9 steps)
- transaction-history: listing/retrieving payments (3 workflows)
- token-management: token rotation, revocation, grant cancel (3 workflows)

All workflows reference the existing OpenAPI specs in
open-payments-specifications and use Arazzo runtime expressions
to define data flow between steps.
@netlify
Copy link
Copy Markdown

netlify bot commented Mar 31, 2026

Deploy Preview for openpayments-preview canceled.

Name Link
🔨 Latest commit aa5937a
🔍 Latest deploy log https://app.netlify.com/projects/openpayments-preview/deploys/69cc3462b0cf3a000869859b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant