Hello everybody 👋🏻
July was a packed month for us, so here’s a rundown of what we’ve been working on:
Rafiki Work Week
This year’s Rafiki Work Week was held in Cluj-Napoca, Romania. Almost 40 of us from different organizations worldwide gathered to discuss and improve Rafiki in many aspects:
Performance improvements - One of our tracks was improving Rafiki’s horizontal scalability—ensuring it can handle more load. The team explored a new event-driven design, and early tests with production-like environments show this approach significantly boosts throughput and reduces latency, paving the way for a more scalable Rafiki.
Documentation updates - We revamped Rafiki’s documentation to make it more user-friendly, with a restructured layout for easier navigation. Plus, we translated the docs into Spanish and added snippets for other programming languages.
Kubernetes Operator - Deploying and scaling Rafiki on Kubernetes is about to get easier. We kicked off development of a Kubernetes Operator to automate deployment and scaling. This will streamline operations for teams running Rafiki in production environments.
Card payments integration - We’re building services to enable card payments linked to payment pointers, allowing seamless transactions at point-of-sale (POS) terminals. This feature will bridge the gap between digital wallets and physical retail, making Rafiki even more versatile.
SEPA support - We have started exploring how SEPA integrates with Open Payments. This can allow transfers to wallet addresses to be routed directly to SEPA-compliant bank accounts, simplifying cross-border payments for European users.
Multi-tenancy
The wait is over! Multi-tenancy was merged in main last month, which brings many features, including:
- tenanted resources (peers, assets, quotes, wallet addresses etc.);
- CRUD operations for tenants;
- Admin API & UI updates for operator and tenants to configure tenant settings and tenanted resources.
Feel free to spin up Rafiki in local playground and let us know if you spot any issues!
New release
In early July, we released version 1.2.0-beta, which includes numerous features, fixes, and improvements, notably:
- We return objects with additional details in resource server errors.
- For certain quoting errors, we now provide a minimum amount value, guiding senders on how much to add to ensure successful transactions.
Moreover, Open Payments also has a new release that includes:
- Authorization Server's Grant Request spec now allows submitting only "debitAmount" or "receiveAmount" (not both) in an outgoing payment grant request.
- Removal of the "updatedAt" field from the incoming and outgoing payment resources.
Top comments (0)