Skip to content

Add subscriptions with open payments blog article#223

Open
adrianboros wants to merge 3 commits intomainfrom
adrian/subscriptions-with-open-payments-poc
Open

Add subscriptions with open payments blog article#223
adrianboros wants to merge 3 commits intomainfrom
adrian/subscriptions-with-open-payments-poc

Conversation

@adrianboros
Copy link
Copy Markdown
Contributor

@adrianboros adrianboros commented Apr 28, 2026

PR Checklist

  • Linked issue added (e.g., Fixes #123)
  • I have run bun run format to ensure code is properly formatted
  • I have verified that bun run lint passes without errors
  • If blog post was added:
    • Ensure images have been optimised
    • Update dates to reflect the actual publishing date when merged (file names, folder names, and frontmatter)

Summary

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 28, 2026

Deploy Preview for interledger-org-developers ready!

Name Link
🔨 Latest commit f16f035
🔍 Latest deploy log https://app.netlify.com/projects/interledger-org-developers/deploys/69f10a85404cb10008a17f23
😎 Deploy Preview https://deploy-preview-223--interledger-org-developers.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@adrianboros adrianboros marked this pull request as ready for review April 28, 2026 19:11
@adrianboros adrianboros self-assigned this Apr 28, 2026
@JoblersTune
Copy link
Copy Markdown
Contributor

@adrianboros please optimise your images by running them through https://tinypng.com/

@hajjimo
Copy link
Copy Markdown
Contributor

hajjimo commented Apr 29, 2026

The post reads as if it's geared more towards academia. I suggest that the style be changed to make it more accessible for a general audience. Also, since OP implements GNAP for authorization, we should mention and reference it in the body of the post.

Copy link
Copy Markdown
Contributor

@mkurapov mkurapov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added some comments. I also agree with Mohammed about the tone, and I think we could trim this down a bit by having it slightly more high level.

It could also be nice to point to the code/PR where this was implemented in case others wanted to get an idea for a subscription service

- expose buyer and merchant subscription views in wallet,
- recover cleanly when recurring billing falls into a past-due state.

Testnet is the environment used to run this experiment end to end. The goal is not to declare the production architecture finished. The goal is to test whether Open Payments can credibly support subscription setup, renewal, and recovery, and whether the required system boundaries, grant handling, and user recovery paths are viable enough to justify deeper investment.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The goal is to test whether Open Payments can credibly support subscription setup, renewal, and recovery, and whether the required system boundaries, grant handling, and user recovery paths are viable enough to justify deeper investment.

Is it more correct to say that the goal was to test how a subscription engine could be built on top of Open Payments?

Comment on lines +76 to +79
<LargeImg
src="/developers/img/blog/2026-04-30/testnet-architecture-diagram.png"
alt="The Testnet Architecture Diagram"
/>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this image could be simplified? Since the reader doesn't need to know about GateHub. Also, it would be more correct to have Rafiki be diagrammed within the Wallet

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.

4 participants