<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>The Interledger Community 🌱</title>
    <description>The most recent home feed on The Interledger Community 🌱.</description>
    <link>https://community.interledger.org</link>
    <atom:link rel="self" type="application/rss+xml" href="https://community.interledger.org/feed"/>
    <language>en</language>
    <item>
      <title>Open Payments Developer Awareness Sprint: Building Local Developer Capacity in Barranquilla, Colombia</title>
      <dc:creator>Kelly Villa</dc:creator>
      <pubDate>Wed, 28 Oct 2026 19:26:36 +0000</pubDate>
      <link>https://community.interledger.org/02kellyv/open-payments-developer-awareness-sprint-building-local-developer-capacity-in-barranquilla-1h2o</link>
      <guid>https://community.interledger.org/02kellyv/open-payments-developer-awareness-sprint-building-local-developer-capacity-in-barranquilla-1h2o</guid>
      <description>&lt;p&gt;&lt;strong&gt;Brief Project Description&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The Open Payments Developer Awareness Sprint, led by CaribeDev Foundation in Barranquilla, Colombia, introduced local developers and technology students to Interledger and Open Payments through hands-on workshops, a mini hackathon, and personalized technical training. The project combined foundational learning with practical implementation, helping participants explore wallet integration, payment flows, and the Interledger Open Payments SDK. Across three activities, the project recorded 49 attendance instances. The initiative aimed to strengthen local developer capacity and expand awareness of open, interoperable payment technologies.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Progress Report:&lt;/strong&gt; &lt;a href="https://drive.google.com/drive/folders/1B5FqWNxzlFyh-auZNvY2AYAQ5Prx2d9R?usp=drive_link" rel="noopener noreferrer"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Project Update&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;During the funded period, CaribeDev Foundation implemented three activities designed to build practical knowledge of Interledger and Open Payments among developers and technology students in Barranquilla, Colombia.&lt;/p&gt;

&lt;p&gt;The project began with an introductory workshop on July 25, 2026, followed by a mini hackathon on August 1, 2026. The final activity, an intensive technical workshop, took place on September 21, 2026, after being rescheduled from September 19 due to a weather-related power outage at the venue.&lt;/p&gt;

&lt;p&gt;Across the three activities, the project recorded 49 attendance instances: 22 at the introductory workshop, 20 at the mini hackathon, and 7 at the final intensive workshop. These figures represent attendance across activities, not necessarily unique individuals.&lt;/p&gt;

&lt;p&gt;The project progressed from foundational concepts and guided exercises to practical implementation challenges and personalized technical reinforcement. The final workshop revisited topics from the mini hackathon, giving participants additional time to work through technical questions and strengthen their understanding.&lt;/p&gt;

&lt;p&gt;One key lesson was the importance of adapting delivery to local circumstances and allowing time for hands-on guidance. Although the final activity had lower attendance than the earlier sessions, its smaller format enabled more personalized support.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Project Impact &amp;amp; Target Audience(s)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The project primarily served developers, programmers, technology students, and other members of the local technology community in Barranquilla and the Colombian Caribbean.&lt;/p&gt;

&lt;p&gt;By offering free learning opportunities, the initiative reduced financial barriers to accessing technical education and created opportunities for participants to explore payment technologies through practical activities rather than theory alone.&lt;/p&gt;

&lt;p&gt;Participants were introduced to Interledger and Open Payments concepts, including wallet-to-wallet payment flows and the use of the Interledger Open Payments SDK. The mini hackathon provided an opportunity to apply this knowledge through implementation and integration challenges.&lt;/p&gt;

&lt;p&gt;The project supports the Interledger Foundation’s mission by increasing awareness of open payment technologies and building developer capacity to understand and experiment with interoperable payment systems.&lt;/p&gt;

&lt;p&gt;The activities were open and free to participants. While the project sought to broaden access to technical learning, it did not collect sufficient demographic data to quantify participation by specific marginalized groups. CaribeDev remains committed to promoting inclusive access to technology education across the Colombian Caribbean.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Progress on Objectives, Key Activities&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Objective 1:&lt;/strong&gt; Introduce developers to Interledger and Open Payments
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Activity 1 — Introduction to Interledger and Open Payments&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
&lt;strong&gt;Date:&lt;/strong&gt; July 25, 2026&lt;br&gt;&lt;br&gt;
&lt;strong&gt;Attendance:&lt;/strong&gt; 22 participants&lt;/p&gt;

&lt;p&gt;The introductory workshop presented the fundamentals of Interledger and Open Payments and included a guided technical session. Participants explored the Interledger Open Payments SDK and key components of a wallet-to-wallet payment flow, including webhooks, Incoming Payments, Quotes, Interactions, and Outgoing Payments.&lt;/p&gt;

&lt;p&gt;The session established the foundational knowledge needed for the subsequent practical activities.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Supporting documentation:&lt;/strong&gt; (&lt;a href="https://drive.google.com/drive/folders/1B5FqWNxzlFyh-auZNvY2AYAQ5Prx2d9R?usp=drive_link" rel="noopener noreferrer"&gt;https://drive.google.com/drive/folders/1B5FqWNxzlFyh-auZNvY2AYAQ5Prx2d9R?usp=drive_link&lt;/a&gt;)&lt;/p&gt;

&lt;h3&gt;
  
  
  Objective 2: Encourage practical implementation through collaborative development
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Activity 2 — Mini Hackathon: Implementation and Integration of the Interledger Wallet&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
&lt;strong&gt;Date:&lt;/strong&gt; August 1, 2026&lt;br&gt;&lt;br&gt;
&lt;strong&gt;Attendance:&lt;/strong&gt; 20 participants&lt;/p&gt;

&lt;p&gt;The mini hackathon challenged participants to apply their knowledge by working on the implementation and integration of an Interledger wallet. The activity emphasized practical problem-solving and experimentation with Open Payments.&lt;/p&gt;

&lt;p&gt;Prizes were awarded to recognize the teams’ work, encouraging participants to engage with the technology through a hands-on development challenge.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Supporting documentation:&lt;/strong&gt; (&lt;a href="https://drive.google.com/drive/folders/1T8QR3123wOqCxYznqTgrFkU4QKiYKGiI?usp=drive_link" rel="noopener noreferrer"&gt;https://drive.google.com/drive/folders/1T8QR3123wOqCxYznqTgrFkU4QKiYKGiI?usp=drive_link&lt;/a&gt;)&lt;/p&gt;

&lt;h3&gt;
  
  
  Objective 3: Reinforce technical knowledge and support continued learning
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Activity 3 — Intensive Open Payments Technical Workshop&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
&lt;strong&gt;Date:&lt;/strong&gt; September 21, 2026&lt;br&gt;&lt;br&gt;
&lt;strong&gt;Attendance:&lt;/strong&gt; 7 participants&lt;/p&gt;

&lt;p&gt;The final workshop revisited the technical topics covered during the mini hackathon in an intensive, personalized format. Led by Joel Rodríguez, the session gave participants additional time to review implementation concepts, address technical questions, and strengthen their understanding of the topics.&lt;/p&gt;

&lt;p&gt;The activity was rescheduled from September 19 to September 21 because of a weather-related power outage at the venue.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Supporting documentation:&lt;/strong&gt; (&lt;a href="https://drive.google.com/drive/folders/1ljNLQLVWpbGWtwSMy7ZLZhNNYUMnA0ut?usp=drive_link" rel="noopener noreferrer"&gt;https://drive.google.com/drive/folders/1ljNLQLVWpbGWtwSMy7ZLZhNNYUMnA0ut?usp=drive_link&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;Each individual event report includes photographs and additional evidence of implementation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Communications and Marketing
&lt;/h2&gt;

&lt;p&gt;CaribeDev communicated the initiative through its community channels and event promotion activities to reach developers and technology students in Barranquilla and the surrounding region.&lt;/p&gt;

&lt;p&gt;The project also shared its outcomes with the Interledger community through a public project update, documenting the activities, participation, lessons learned, and future direction.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Public project update:&lt;/strong&gt; &lt;a href="https://community.interledger.org/02kellyv/open-payments-developer-awareness-sprint-building-local-developer-capacity-in-barranquilla-4a2o"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The individual event reports provide further documentation of the activities and include photographs of the sessions. Project-related technical learning resources are also available in the &lt;a href="https://carlos-ponton2.gitbook.io/interledger-open-payments" rel="noopener noreferrer"&gt;Interledger Open Payments guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What’s Next?
&lt;/h2&gt;

&lt;p&gt;CaribeDev plans to build on the knowledge and community engagement generated through this initiative by continuing to create free opportunities for developers to explore open technologies and build practical skills.&lt;/p&gt;

&lt;p&gt;The experience highlighted the value of combining introductory learning, collaborative implementation, and personalized technical support. Future activities can build on this approach while allowing more time for participant follow-up, troubleshooting, and continued experimentation.&lt;/p&gt;

&lt;p&gt;CaribeDev also intends to continue sharing relevant learning resources with its community and exploring opportunities to strengthen local engagement with Interledger and Open Payments.&lt;/p&gt;

&lt;h2&gt;
  
  
  Community Support
&lt;/h2&gt;

&lt;p&gt;We welcome connections with educators, developer communities, technical mentors, and organizations interested in expanding access to open payment technologies in Latin America.&lt;/p&gt;

&lt;p&gt;Opportunities for continued collaboration, technical mentorship, access to learning resources, and future developer-focused initiatives would help build on the foundation established through this project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Additional Comments
&lt;/h2&gt;

&lt;p&gt;CaribeDev Foundation thanks the Interledger Foundation for supporting this initiative and helping create opportunities for local developers to learn about and experiment with Open Payments.&lt;/p&gt;

&lt;p&gt;The project reinforced the importance of making emerging payment technologies more accessible through free, practical, community-driven learning experiences.&lt;/p&gt;

&lt;h2&gt;
  
  
  Relevant Links/Resources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://carlos-ponton2.gitbook.io/interledger-open-payments" rel="noopener noreferrer"&gt;Interledger Open Payments Guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://drive.google.com/file/d/1INVKpuwp9saU9Jn-oK8HKDeAx4Mic2jB/view?usp=drive_link" rel="noopener noreferrer"&gt;Progress Report&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://drive.google.com/file/d/1aYnLupAiiCaSlMYcknx9JNK69dcAwtYj/view?usp=drive_link" rel="noopener noreferrer"&gt;Event 1 — Introduction to Interledger and Open Payments&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://drive.google.com/file/d/1PWCKtcYm3TjFpGxDT-iZQDJ2GmJ50CMv/view?usp=drive_link" rel="noopener noreferrer"&gt;Event 2 — Mini Hackathon: Implementation and Integration of the Interledger Wallet&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://drive.google.com/file/d/1BJvwwOwKKqs2qYI4F7xQXch7OhTM8Wf_/view?usp=drive_link" rel="noopener noreferrer"&gt;Event 3 — Intensive Open Payments Technical Workshop&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>finalreports</category>
    </item>
    <item>
      <title>Ruby Language Support for Kiota — ILF Grant Progress Report</title>
      <dc:creator>Andrea Peruffo</dc:creator>
      <pubDate>Tue, 06 Oct 2026 12:28:56 +0000</pubDate>
      <link>https://community.interledger.org/andreatp/ruby-language-support-for-kiota-ilf-grant-progress-report-m32</link>
      <guid>https://community.interledger.org/andreatp/ruby-language-support-for-kiota-ilf-grant-progress-report-m32</guid>
      <description>&lt;h2&gt;
  
  
  Brief Project Description
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/microsoft/kiota" rel="noopener noreferrer"&gt;Kiota&lt;/a&gt; is Microsoft's open source generator that turns an OpenAPI description into a typed API client. Its Ruby target existed but was classified as Experimental: the integration test was broken, Ruby carried 15 test suppressions (more than every other language combined), composed types and several response shapes were not handled, and the runtime gems were scattered across pre-1.0 repositories. This grant closes those gaps so that Kiota produces correct, idiomatic Ruby clients from standard OpenAPI descriptions, with the Open Payments APIs as the reference use case, and moves the Ruby target from Experimental toward Preview. All work is merged upstream.&lt;/p&gt;

&lt;h2&gt;
  
  
  Project Update
&lt;/h2&gt;

&lt;p&gt;Two of the three funded months are done and the project is on the original timeline.&lt;/p&gt;

&lt;p&gt;The headline is that a payment now goes end to end through Open Payments using only Kiota-generated Ruby clients. The demo at &lt;a href="https://github.com/andreaTP/kiota-ruby-op-poc" rel="noopener noreferrer"&gt;https://github.com/andreaTP/kiota-ruby-op-poc&lt;/a&gt; generates the three clients (wallet address, auth server, resource server) from the official Open Payments 1.4.0 descriptions and runs the flow from &lt;a href="https://github.com/interledger/open-payments-example" rel="noopener noreferrer"&gt;interledger/open-payments-example&lt;/a&gt;: read both wallets, incoming payment grant, incoming payment, quote grant, quote, interactive outgoing payment grant approved in the browser, grant continuation, outgoing payment, then polling until the incoming payment is paid in full. Only two things are hand written: a Kiota authentication provider that adds the GNAP token and signs each request (RFC 9421 HTTP message signatures with Ed25519, RFC 9530 Content-Digest), and the flow itself. The README covers running it against a local stand-in that verifies the tokens and signatures, and against the Interledger test network.&lt;/p&gt;

&lt;p&gt;Getting there took 29 pull requests to &lt;a href="https://github.com/microsoft/kiota" rel="noopener noreferrer"&gt;microsoft/kiota&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota-ruby" rel="noopener noreferrer"&gt;microsoft/kiota-ruby&lt;/a&gt; and the former per-gem repositories (all linked below). Along the way the four Ruby runtime gems were consolidated into one repository and released as 0.24.0 (Ruby 3.3+), and the Ruby integration-test suppressions went from 15 to 1 (Microsoft Graph beta, which is not tested for Ruby by design).&lt;/p&gt;

&lt;p&gt;The main struggle matched what I anticipated in the proposal as "hidden semantic gaps". Several problems only surfaced when real payloads went through the generated code: enum members were sent with their Ruby name (&lt;code&gt;"IncomingPayment"&lt;/code&gt;) instead of their wire value (&lt;code&gt;"incoming-payment"&lt;/code&gt;), so every grant request was rejected, and a &lt;code&gt;oneOf&lt;/code&gt; without a discriminator, which Open Payments uses for grant, continue and error responses, came back as an empty object. Both are fixed in &lt;a href="https://github.com/microsoft/kiota/pull/8314" rel="noopener noreferrer"&gt;kiota#8314&lt;/a&gt; and &lt;a href="https://github.com/microsoft/kiota-ruby/pull/171" rel="noopener noreferrer"&gt;kiota-ruby#171&lt;/a&gt;. Some fixes were breaking changes to the gems (enum values, unset scalars no longer written as &lt;code&gt;null&lt;/code&gt; or &lt;code&gt;""&lt;/code&gt;), which is why they were made now, while the target is still Experimental, rather than later.&lt;/p&gt;

&lt;p&gt;A second input that shaped the work was an independent report by @wiebren on &lt;a href="https://github.com/microsoft/kiota/issues/7956" rel="noopener noreferrer"&gt;kiota#7956&lt;/a&gt;, who ran a generated Ruby client through a 29-case contract suite they use across languages. All eight itemized failures are now fixed.&lt;/p&gt;

&lt;p&gt;The one scope change against the month-2 plan is that the Text, Form and Multipart serialization gems are not started yet. The Open Payments blockers and the correctness issues above were more valuable to users and took the time. The serialization gems move to month 3, see "What's Next".&lt;/p&gt;

&lt;h2&gt;
  
  
  Project Impact &amp;amp; Target Audience(s)
&lt;/h2&gt;

&lt;p&gt;The direct beneficiaries are Ruby developers who want a typed client for an OpenAPI-described API without writing it by hand, and the Interledger ecosystem in particular. Ruby is widely used by small teams and in fintech, and before this work there was no viable path to an Open Payments client in Ruby: Kiota's Ruby output did not compile against real-world descriptions. &lt;a href="https://github.com/microsoft/kiota/issues/7956" rel="noopener noreferrer"&gt;kiota#7956&lt;/a&gt; was opened by a community member precisely to get an Open Payments Ruby SDK, and the generated clients now cover that use case. This lowers the barrier for Rails and Ruby shops to integrate Open Payments, which supports the Foundation's mission of broadening who can build on the Interledger Protocol.&lt;/p&gt;

&lt;p&gt;Secondary beneficiaries are all Kiota users: two of the fixes landed in the core generator and apply to every language (&lt;a href="https://github.com/microsoft/kiota/pull/8138" rel="noopener noreferrer"&gt;kiota#8138&lt;/a&gt; makes generation reproducible, &lt;a href="https://github.com/microsoft/kiota/pull/8193" rel="noopener noreferrer"&gt;kiota#8193&lt;/a&gt; by @Om-singhaI stops an inline type from clobbering a component with the same name), and the Ruby target now runs the same CI as the mature languages.&lt;/p&gt;

&lt;p&gt;The project does not target a specific demographic group. The work is upstream, open source (MIT) and free to use, so anyone can benefit from it without a relationship to me or to the Foundation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Progress on Objectives, Key Activities
&lt;/h2&gt;

&lt;p&gt;Status against the proposal, grouped as in the original submission. Links go to the merged pull requests.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Critical fixes&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Objective&lt;/th&gt;
&lt;th&gt;Status&lt;/th&gt;
&lt;th&gt;Links&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Binary/stream type support&lt;/td&gt;
&lt;td&gt;Done. Stream request bodies are sent, binary responses reach the right adapter method, binary aliases resolve to the right model.&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://github.com/microsoft/kiota/pull/8256" rel="noopener noreferrer"&gt;kiota#8256&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8265" rel="noopener noreferrer"&gt;kiota#8265&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota-ruby/pull/163" rel="noopener noreferrer"&gt;kiota-ruby#163&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HTTP send method dispatch (void, collection, collection of primitives)&lt;/td&gt;
&lt;td&gt;Done. All five send variants exist in the adapter and the generator dispatches every response shape to the right one.&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://github.com/microsoft/kiota-ruby/pull/155" rel="noopener noreferrer"&gt;kiota-ruby#155&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8256" rel="noopener noreferrer"&gt;kiota#8256&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Text, Form and Multipart serialization gems&lt;/td&gt;
&lt;td&gt;Not started, moved to month 3.&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://github.com/microsoft/kiota/issues/2077" rel="noopener noreferrer"&gt;#2077&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/issues/3032" rel="noopener noreferrer"&gt;#3032&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/issues/1049" rel="noopener noreferrer"&gt;#1049&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Triage the 15 integration test suppressions&lt;/td&gt;
&lt;td&gt;Done. 1 suppression remains (Microsoft Graph beta, excluded on purpose). Ruby CI now generates and lints 19 descriptions, including GitHub, Stripe, Notion and Meraki, and runs mock-server tests for errors, inheritance, query parameters, discriminators, enums and default values.&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://github.com/microsoft/kiota/pull/8116" rel="noopener noreferrer"&gt;kiota#8116&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8127" rel="noopener noreferrer"&gt;kiota#8127&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8131" rel="noopener noreferrer"&gt;kiota#8131&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8255" rel="noopener noreferrer"&gt;kiota#8255&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8301" rel="noopener noreferrer"&gt;kiota#8301&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;High-severity gaps&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Objective&lt;/th&gt;
&lt;th&gt;Status&lt;/th&gt;
&lt;th&gt;Links&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Composed types (union/intersection)&lt;/td&gt;
&lt;td&gt;Done, with and without a discriminator, including primitive and array members.&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://github.com/microsoft/kiota/pull/8065" rel="noopener noreferrer"&gt;kiota#8065&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8209" rel="noopener noreferrer"&gt;kiota#8209&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8314" rel="noopener noreferrer"&gt;kiota#8314&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota-ruby/pull/106" rel="noopener noreferrer"&gt;kiota-ruby#106&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota-ruby/pull/142" rel="noopener noreferrer"&gt;kiota-ruby#142&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota-ruby/pull/151" rel="noopener noreferrer"&gt;kiota-ruby#151&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota-ruby/pull/171" rel="noopener noreferrer"&gt;kiota-ruby#171&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Backing store (complete or remove)&lt;/td&gt;
&lt;td&gt;Open. Decision planned for month 3, after asking the maintainers and users whether anyone depends on it.&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scalar vs parsable request body discrimination&lt;/td&gt;
&lt;td&gt;Done. Scalar bodies and enum collections are serialized.&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://github.com/microsoft/kiota-ruby/pull/158" rel="noopener noreferrer"&gt;kiota-ruby#158&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8256" rel="noopener noreferrer"&gt;kiota#8256&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Unit test coverage&lt;/td&gt;
&lt;td&gt;In progress. Every fix above came with unit tests and mock-server integration tests; a dedicated coverage pass is planned for month 3.&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Completeness and quality&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Objective&lt;/th&gt;
&lt;th&gt;Status&lt;/th&gt;
&lt;th&gt;Links&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Enum handling (collections, defaults by wire name, wire values)&lt;/td&gt;
&lt;td&gt;Done.&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://github.com/microsoft/kiota/pull/8053" rel="noopener noreferrer"&gt;kiota#8053&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8256" rel="noopener noreferrer"&gt;kiota#8256&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8314" rel="noopener noreferrer"&gt;kiota#8314&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota-ruby/pull/158" rel="noopener noreferrer"&gt;kiota-ruby#158&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Typed errors, status code and headers on &lt;code&gt;ApiError&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Done.&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://github.com/microsoft/kiota-ruby/pull/153" rel="noopener noreferrer"&gt;kiota-ruby#153&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota-ruby/pull/171" rel="noopener noreferrer"&gt;kiota-ruby#171&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Idiomatic Ruby output (RuboCop clean, frozen string literals, &lt;code&gt;attr_accessor&lt;/code&gt;, no &lt;code&gt;ruby -w&lt;/code&gt; warnings, autoloaded models)&lt;/td&gt;
&lt;td&gt;Done.&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://github.com/microsoft/kiota/pull/8037" rel="noopener noreferrer"&gt;kiota#8037&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8052" rel="noopener noreferrer"&gt;kiota#8052&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/pull/8301" rel="noopener noreferrer"&gt;kiota#8301&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Unset scalars left off the wire&lt;/td&gt;
&lt;td&gt;Done.&lt;/td&gt;
&lt;td&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/154" rel="noopener noreferrer"&gt;kiota-ruby#154&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Runtime gem stabilization toward 1.0&lt;/td&gt;
&lt;td&gt;In progress. The four gems now live in one repository with a shared release process, released as 0.24.0 requiring Ruby 3.3+.&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://github.com/microsoft/kiota-ruby/pull/112" rel="noopener noreferrer"&gt;kiota-ruby#112&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota-ruby/pull/140" rel="noopener noreferrer"&gt;kiota-ruby#140&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Primary error message, deprecation annotations&lt;/td&gt;
&lt;td&gt;Open, month 3.&lt;/td&gt;
&lt;td&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/issues/63" rel="noopener noreferrer"&gt;kiota-ruby#63&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Quickstart documentation&lt;/td&gt;
&lt;td&gt;In progress. The Open Payments demo README is a working quickstart; the upstream docs page is planned for month 3.&lt;/td&gt;
&lt;td&gt;&lt;a href="https://github.com/andreaTP/kiota-ruby-op-poc" rel="noopener noreferrer"&gt;https://github.com/andreaTP/kiota-ruby-op-poc&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Maturity from Experimental toward Preview&lt;/td&gt;
&lt;td&gt;To be proposed to the maintainers once month 3 lands.&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Expected outcomes from the proposal&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Correct, idiomatic SDKs for standard OpenAPI specs: yes, verified on 19 public descriptions plus Open Payments.&lt;/li&gt;
&lt;li&gt;Integration test passes end to end: yes.&lt;/li&gt;
&lt;li&gt;Suppressions from 15 to zero: 15 to 1, the last one is intentional.&lt;/li&gt;
&lt;li&gt;All 4 serialization formats via published gems: JSON only so far, the other three are month 3.&lt;/li&gt;
&lt;li&gt;Test coverage at parity with other languages: in progress.&lt;/li&gt;
&lt;li&gt;All work merged upstream: yes, every change is in microsoft/kiota or microsoft/kiota-ruby.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Communications and Marketing
&lt;/h2&gt;

&lt;p&gt;All of the work happened in public on GitHub, through pull requests, reviews and issue threads with the Kiota maintainers. The main public writeup is the summary I am posting on &lt;a href="https://github.com/microsoft/kiota/issues/7956" rel="noopener noreferrer"&gt;kiota#7956&lt;/a&gt;, the issue that motivated the Open Payments use case, with the itemized list of what changed and what is still open. The demo repository at &lt;a href="https://github.com/andreaTP/kiota-ruby-op-poc" rel="noopener noreferrer"&gt;https://github.com/andreaTP/kiota-ruby-op-poc&lt;/a&gt; documents how to generate the clients and send a payment on the Interledger test network.&lt;/p&gt;

&lt;p&gt;I am also in touch with the Kiota team on their Discord. The proposal has no marketing budget. A blog post walking through the Open Payments flow in Ruby is planned once the month-3 work is released.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's Next?
&lt;/h2&gt;

&lt;p&gt;The remaining month (to November 10, 2026) covers the month-3 plan plus the item moved from month 2:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Text, Form and Multipart serialization gems in microsoft/kiota-ruby, closing &lt;a href="https://github.com/microsoft/kiota/issues/2077" rel="noopener noreferrer"&gt;#2077&lt;/a&gt;, &lt;a href="https://github.com/microsoft/kiota/issues/3032" rel="noopener noreferrer"&gt;#3032&lt;/a&gt; and &lt;a href="https://github.com/microsoft/kiota/issues/1049" rel="noopener noreferrer"&gt;#1049&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Backing store: complete or remove, based on maintainer and community input.&lt;/li&gt;
&lt;li&gt;Remaining completeness items: primary error message, deprecation annotations.&lt;/li&gt;
&lt;li&gt;Unit test coverage expansion in the generator's Ruby writers and in the gems.&lt;/li&gt;
&lt;li&gt;Runtime gem stabilization: a release that bundles the above, and the path to 1.0 agreed with the maintainers.&lt;/li&gt;
&lt;li&gt;Quickstart documentation on the Kiota docs site, and a blog post on the Open Payments flow.&lt;/li&gt;
&lt;li&gt;Proposing to the maintainers that Ruby moves from Experimental to Preview.&lt;/li&gt;
&lt;li&gt;Final report by December 10, 2026.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Community Support
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Try it on Open Payments.&lt;/strong&gt; If you write Ruby and have a test wallet, run the demo against the Interledger test network and report anything odd. Real usage is what found the last two blockers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is a Ruby Open Payments SDK wanted?&lt;/strong&gt; The generated clients could be the basis of an official &lt;code&gt;open-payments&lt;/code&gt; gem, in the way the TypeScript and PHP SDKs exist today. I would value a conversation with the Open Payments team about whether that is desirable and who would own it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backing store.&lt;/strong&gt; If anyone depends on the backing store in Ruby, I would like to hear it before the keep-or-drop decision is made.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Additional Comments
&lt;/h2&gt;

&lt;p&gt;Thanks to Vincent Biret (@baywet) for reviewing every pull request promptly, to @wiebren for the detailed contract-suite report, to @mahmudsudo for opening the Open Payments issue, and to @Om-singhaI for the core fix on component name collisions.&lt;/p&gt;

&lt;p&gt;As stated in the proposal, AI tooling (Claude Code) was used throughout for analysis and implementation, with every change reviewed by me before it was submitted and then by the Kiota maintainers before it was merged.&lt;/p&gt;

&lt;h2&gt;
  
  
  Relevant Links/Resources (optional)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Open Payments demo: &lt;a href="https://github.com/andreaTP/kiota-ruby-op-poc" rel="noopener noreferrer"&gt;https://github.com/andreaTP/kiota-ruby-op-poc&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Tracking issue with the public summary: &lt;a href="https://github.com/microsoft/kiota/issues/7956" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/issues/7956&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Ruby runtime gems: &lt;a href="https://github.com/microsoft/kiota-ruby" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby&lt;/a&gt; (release v0.24.0)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Generator pull requests, microsoft/kiota:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8037" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8037&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8052" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8052&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8053" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8053&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8065" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8065&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8116" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8116&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8127" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8127&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8131" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8131&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8138" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8138&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8209" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8209&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8255" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8255&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8256" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8256&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8265" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8265&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8301" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8301&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota/pull/8314" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8314&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Runtime pull requests, microsoft/kiota-ruby:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/106" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby/pull/106&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/112" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby/pull/112&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/140" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby/pull/140&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/142" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby/pull/142&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/151" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby/pull/151&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/153" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby/pull/153&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/154" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby/pull/154&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/155" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby/pull/155&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/158" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby/pull/158&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/163" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby/pull/163&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-ruby/pull/171" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-ruby/pull/171&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Former per-gem repositories, before the consolidation:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-abstractions-ruby/pull/106" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-abstractions-ruby/pull/106&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-serialization-json-ruby/pull/88" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-serialization-json-ruby/pull/88&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-authentication-oauth-ruby/pull/73" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-authentication-oauth-ruby/pull/73&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/microsoft/kiota-http-ruby/pull/85" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota-http-ruby/pull/85&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Core fix benefiting all languages: &lt;a href="https://github.com/microsoft/kiota/pull/8193" rel="noopener noreferrer"&gt;https://github.com/microsoft/kiota/pull/8193&lt;/a&gt;&lt;/p&gt;

</description>
      <category>grantreports</category>
      <category>software</category>
      <category>progressreport</category>
    </item>
    <item>
      <title>ILP Pathways (Benedict College) — ILF Grant Progress Report</title>
      <dc:creator>Chantil Wright Galloway</dc:creator>
      <pubDate>Tue, 29 Sep 2026 18:31:40 +0000</pubDate>
      <link>https://community.interledger.org/benedictedu/ilp-pathways-benedict-college-ilf-grant-progress-report-45cg</link>
      <guid>https://community.interledger.org/benedictedu/ilp-pathways-benedict-college-ilf-grant-progress-report-45cg</guid>
      <description>&lt;h2&gt;
  
  
  Brief Project Description
&lt;/h2&gt;

&lt;p&gt;ILP Pathways brings Interledger Protocol education to Benedict College, a historically Black college in Columbia, South Carolina. Through a three-tier cascade model, twelve students (the "Benedict 12") learn the Interledger Protocol and Open Payments in a FinTech course and on a Rafiki deployment in our Business Innovation Lab. They then consult with 15–20 Black- and minority-owned Columbia businesses and mentor 60 youth, ages 8–18, at a Digital Finance and Innovation Summer Camp. All curriculum will be released under a Creative Commons (CC BY 4.0) license so other HBCUs can adopt the model.&lt;/p&gt;

&lt;h2&gt;
  
  
  Project Update
&lt;/h2&gt;

&lt;p&gt;The grant began in March 2026, and the foundation is in place. Our biggest win this fall: the Benedict 12 cohort has been selected, and our FinTech course, BA 439 FinTech Strategy and Management, is approved for Spring 2027. Dr. James Ross is now building it in Canvas, the College's learning management system.&lt;/p&gt;

&lt;p&gt;Our main struggle has been timing. Institutional course approval and procurement move on the academic calendar, not the grant calendar. At our kickoff with the ILF Program Team, we agreed to move the summer camp to 2027, and a no-cost extension set the project end date at September 1, 2027. In September we recalibrated the full timeline with the Program Team: Fall 2026 is our build-and-recruit semester, the course launches in Spring 2027, and the camp runs in June–July 2027.&lt;/p&gt;

&lt;h2&gt;
  
  
  Project Impact &amp;amp; Target Audience(s)
&lt;/h2&gt;

&lt;p&gt;ILP Pathways serves Black, Indigenous, and People of Color (BIPOC) communities at every tier:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Benedict College students.&lt;/strong&gt; Benedict is a historically Black college, and most of our students are first-generation college attendees. Few have had exposure to payments infrastructure or open financial standards. The Benedict 12 gain technical skills in Interledger and Open Payments, paid stipends, and consulting experience.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Black- and minority-owned small businesses in Columbia.&lt;/strong&gt; Student consulting teams will help 15–20 businesses explore lower-cost, interoperable payment options through Open Payments.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;K-12 youth from underserved Columbia neighborhoods.&lt;/strong&gt; Sixty youth, ages 8–18, will learn digital finance from near-peer college mentors who look like them.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The project supports the Interledger Foundation's mission by growing awareness of Interledger in communities that have been left out of financial technology, training a new group of HBCU students on Rafiki and Open Payments, and releasing open curriculum other institutions can reuse. The project is in its foundation phase, so outcomes will be measured starting with the Spring 2027 course, with pre/post assessments of technical proficiency and financial literacy running through the summer 2027 camp.&lt;/p&gt;

&lt;h2&gt;
  
  
  Progress on Objectives, Key Activities
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Objective&lt;/th&gt;
&lt;th&gt;Status&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Grant executed; ILF kickoff&lt;/td&gt;
&lt;td&gt;Complete&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Faculty capacity-building&lt;/td&gt;
&lt;td&gt;Underway, supported by ILF contractor Casey Ariel Diké&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;FinTech course approved and scheduled&lt;/td&gt;
&lt;td&gt;Complete: BA 439 FinTech Strategy and Management, Spring 2027; course build in Canvas underway&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Benedict 12 selected&lt;/td&gt;
&lt;td&gt;Complete&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rafiki infrastructure and Open Payments testing&lt;/td&gt;
&lt;td&gt;Specifications complete; installation being coordinated with College IT&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Minority-owned business partnerships (15–20)&lt;/td&gt;
&lt;td&gt;Outreach begins alongside cohort training&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;BA 439 launch&lt;/td&gt;
&lt;td&gt;On schedule for Spring 2027&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Summer Camp for 60 K-12 youth&lt;/td&gt;
&lt;td&gt;On schedule for June–July 2027&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;How our plan has evolved:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;One course instead of two.&lt;/strong&gt; Our proposal described an Interledger internship and a separate FinTech course. Working with our dean, we consolidated both into BA 439, the School of Business's special-projects course. This avoided a new-course approval cycle and keeps the Interledger content, hands-on Rafiki work, and consulting projects in one place.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Faculty capacity-building.&lt;/strong&gt; At ILF's direction before award, capacity-building is provided by ILF contractor Casey Ariel Diké at no cost to the grant, in place of the outside consultant in our original budget.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Summer camp moved to 2027.&lt;/strong&gt; Agreed at kickoff, so the camp can build on a fully trained Benedict 12.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Lab infrastructure specifications:&lt;/strong&gt; two servers running Ubuntu Server LTS, a managed network switch, battery backup, and encrypted backup storage. One server will sit in the Innovation Lab and one in our Cybersecurity area.&lt;/p&gt;

&lt;h2&gt;
  
  
  Communications and Marketing
&lt;/h2&gt;

&lt;p&gt;Recruitment for the Benedict 12 was carried out across the Tyrone Adam Burroughs School of Business and Entrepreneurship. Our budget does not include paid marketing. Broader public sharing will begin with the Spring 2027 course launch and the release of our first open curriculum modules.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's Next?
&lt;/h2&gt;

&lt;p&gt;Over the rest of the grant period we will:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Install the lab infrastructure and bring our Rafiki node online&lt;/li&gt;
&lt;li&gt;Begin the Benedict 12's hands-on training and baseline assessments&lt;/li&gt;
&lt;li&gt;Finish building BA 439 and launch it in Spring 2027&lt;/li&gt;
&lt;li&gt;Recruit 15–20 minority-owned business partners and match them with student consulting teams&lt;/li&gt;
&lt;li&gt;Develop the K-12 camp curriculum for three age groups, then recruit 60 youth and deliver the camp in June–July 2027&lt;/li&gt;
&lt;li&gt;Award FinTech Certificates, host a community showcase, and publish our open curriculum&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Community Support
&lt;/h2&gt;

&lt;p&gt;We would welcome connections with ILF grantees who have deployed Rafiki in a university or teaching-lab setting, especially anyone who has built student exercises around Open Payments. We are also interested in guest speakers from the Interledger community for our Spring 2027 cohort, and in introductions to organizations running youth financial-literacy programs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Additional Comments
&lt;/h2&gt;

&lt;p&gt;We are grateful to the ILF Program Team for their flexibility in aligning the project with the academic calendar.&lt;/p&gt;

&lt;h2&gt;
  
  
  Relevant Links/Resources (optional)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://benedict.edu" rel="noopener noreferrer"&gt;Benedict College&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>progressreports</category>
    </item>
    <item>
      <title>Kavodax: Exploring Open, Standards-Based Cross-Border Payments using Stablecoins</title>
      <dc:creator>Gharsa Amin (Kavodax)</dc:creator>
      <pubDate>Sun, 27 Sep 2026 19:10:27 +0000</pubDate>
      <link>https://community.interledger.org/gharsaamin_167/kavodax-exploring-open-standards-based-cross-border-payments-using-stablecoins-bl4</link>
      <guid>https://community.interledger.org/gharsaamin_167/kavodax-exploring-open-standards-based-cross-border-payments-using-stablecoins-bl4</guid>
      <description>&lt;h1&gt;
  
  
  Kavodax: Exploring Open, Standards-Based Cross-Border Payments
&lt;/h1&gt;

&lt;p&gt;&lt;em&gt;Tags: #opensource #interledgerprotocol #ilfgrantee #interledgerfoundation&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The Payment Problem We're Exploring
&lt;/h2&gt;

&lt;p&gt;Sending money across borders today usually means building a custom, one-off connection between whichever two financial platforms are involved. Every new partner, every new corridor, every new bank means engineering time spent solving the same problem again from scratch. That friction slows things down and drives up costs, costs that are ultimately passed on to the people who can least afford them.&lt;/p&gt;

&lt;p&gt;This hits hardest along corridors like Africa and Latin America, where many workers send remittances home to support their families. &lt;/p&gt;

&lt;p&gt;These payments are often slow, expensive, and dependent on intermediaries that add fees at every step. Meanwhile, smaller financial platforms serving these regions frequently lack the resources to build and maintain custom integrations with every bank or payment network they need to reach. The result is a fragmented system where good technology exists but doesn't talk to itself and the people paying the price are the ones with the least room to absorb it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who Is This For?
&lt;/h2&gt;

&lt;p&gt;This project centers on two groups. First, &lt;strong&gt;senders&lt;/strong&gt; — typically workers sending cross-border payments to family or business partners abroad, who need a fast, affordable, and reliable way to move money internationally. Second, &lt;strong&gt;independent platforms and financial service providers&lt;/strong&gt; who want to connect to Kavodax's payment network to serve their own customers, but don't have the engineering resources to build a bespoke integration for every partner they work with.&lt;/p&gt;

&lt;h2&gt;
  
  
  What We Want to Test
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Core hypothesis:&lt;/strong&gt; &lt;em&gt;Open Payments can help independent financial platforms connect to Kavodax's orchestration layer to send and receive cross-border payments by replacing custom, bilateral integrations with a single, standardized way to interact.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;We want to find out whether an outside platform — one that has never spoken to Kavodax before — can discover a Kavodax wallet address, negotiate a payment, and complete a transaction using nothing but the Open Payments standard. If that works, it suggests a real path toward lower-cost, faster-to-launch financial services for underserved corridors.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Payment Flow We'll Explore
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;[Independent Open Payments participant] → [Resolves Kavodax wallet address] → [Open Payments negotiation: incoming payment → quote → outgoing payment] → [Execution through Kavodax's orchestration and settlement infrastructure] → [Funds delivered to recipient]&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In practice: an outside sender interacts with a Kavodax wallet address using the Open Payments protocol. Kavodax creates the required payment resources, and its existing orchestration layer takes care of actually moving the money — whether that's over traditional banking rails or through stablecoin-backed balances — while the sender never needs a custom-built connection to make it happen.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://community.interledger.org/remoteimages/uploads/articles/jdzje1gss14dtjdg19yu.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.interledger.org/remoteimages/uploads/articles/jdzje1gss14dtjdg19yu.png" alt=" " width="1367" height="558"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 1: The Kavodax dashboard — customer wallet balances (USDC, USDT, CAGD) and orchestration actions (Send, On-ramp, Off-ramp) that the Open Payments layer will sit on top of.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How We Plan to Use Open Payments
&lt;/h2&gt;

&lt;p&gt;Kavodax operates as an &lt;strong&gt;orchestration layer&lt;/strong&gt;: our own APIs sit at the center, coordinating everything from account balances and wallet infrastructure to banking rails and settlement partners across the corridors we serve. Open Payments will sit above that orchestration layer as a standard interface, not a replacement for it. It handles how a sender and Kavodax find each other, agree on the terms of a payment, and communicate intent — using wallet addresses, quotes, and incoming/outgoing payment resources. Our existing APIs and transaction engine still handle the actual movement and safekeeping of funds, working alongside our banking partners and wallet infrastructure. The goal is for Open Payments to become the common language external partners can use to reach Kavodax's orchestration layer, instead of each one requiring its own custom connection.&lt;/p&gt;

&lt;h2&gt;
  
  
  What We're Already Building
&lt;/h2&gt;

&lt;p&gt;Kavodax isn't starting from zero. We're already live across &lt;strong&gt;70+ countries&lt;/strong&gt;, with a working dashboard and public APIs powering on-ramp and off-ramp flows. Customers hold balances in stablecoins like USDC and USDT, alongside &lt;strong&gt;CAGD (CAD Global Dollars)&lt;/strong&gt; — our own CAD-backed stablecoin — and can already move funds in and out of those balances in a live sandbox environment.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://community.interledger.org/remoteimages/uploads/articles/au0f2ddyeh0d76jxri8r.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.interledger.org/remoteimages/uploads/articles/au0f2ddyeh0d76jxri8r.png" alt=" " width="1555" height="2200"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 2: Kavodax's off-ramp corridors each connecting stablecoin balances to local payout rails.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;What's still ahead, and what this Accelerator is specifically for, is the interoperability layer on top of our orchestration APIs: standards-level Open Payments support (rather than only internal, Kavodax-to-Kavodax flows), the authorization flow required for a truly independent participant to connect (GNAP-based grant negotiation and HTTP message signing), and validating all of this against an outside Open Payments implementation rather than just our own systems talking to themselves.&lt;/p&gt;

&lt;h2&gt;
  
  
  What We Hope to Demonstrate
&lt;/h2&gt;

&lt;p&gt;By the end of the Accelerator, we want to show that an independent Open Payments participant — with no prior relationship to Kavodax — can resolve a Kavodax wallet address, complete the full payment flow, and have funds settle through our existing orchestration infrastructure. Success looks like:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://community.interledger.org/remoteimages/uploads/articles/nz58my8zzq41fh4nv9ft.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://community.interledger.org/remoteimages/uploads/articles/nz58my8zzq41fh4nv9ft.jpeg" alt=" " width="495" height="619"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A working payment completed end-to-end by an outside party with no custom integration.&lt;/li&gt;
&lt;li&gt;The required authorization steps (including secure message signing) functioning correctly between two independent systems.&lt;/li&gt;
&lt;li&gt;Transaction events properly recorded and monitored under our existing compliance controls.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Looking Beyond the Accelerator
&lt;/h2&gt;

&lt;p&gt;If successful, this proof of concept becomes the foundation for onboarding real partner platforms across the 70+ countries and corridors we already serve — without the months of custom integration work that would otherwise be required. It also lays the groundwork for expanding CAGD and our orchestration APIs into new settlement corridors, and bringing more financial service providers into a shared, interoperable network built on top of the infrastructure we've already deployed.&lt;/p&gt;

&lt;h2&gt;
  
  
  What We're Excited to Learn
&lt;/h2&gt;

&lt;p&gt;We're eager to see how Open Payments performs when a truly independent counterpart — not just our own systems talking to themselves — interacts with Kavodax's orchestration layer in practice. We also want to learn what parts of the onboarding and authorization process create friction for outside developers, so we can share that back with the wider Interledger community.&lt;/p&gt;

&lt;h2&gt;
  
  
  About Kavodax
&lt;/h2&gt;

&lt;p&gt;Kavodax Inc. is a registered Money Services Business (FINTRAC) and licensed Payment Service Provider with the Bank of Canada, operating as an orchestration layer for faster, more affordable cross-border payments. We're live across &lt;strong&gt;70+ countries&lt;/strong&gt;, with public APIs powering customer wallets, stablecoin balances — including CAGD, our own CAD-backed stablecoin — and live on/off-ramp corridors. We're grateful to the Interledger Foundation for the opportunity to test whether open standards can make that experience faster and fairer for everyone who connects to our network.&lt;/p&gt;

&lt;p&gt;Kavodax Email address: &lt;a href="mailto:contact@kavodax.com"&gt;contact@kavodax.com&lt;/a&gt;&lt;br&gt;
Linkedin Profile: &lt;a href="https://www.linkedin.com/in/gharsanay-amin/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/gharsanay-amin/&lt;/a&gt; &lt;br&gt;
&lt;a href="https://www.linkedin.com/company/kavodax/?viewAsMember=true" rel="noopener noreferrer"&gt;https://www.linkedin.com/company/kavodax/?viewAsMember=true&lt;/a&gt; &lt;br&gt;
&lt;a href="https://x.com/Kavodax" rel="noopener noreferrer"&gt;https://x.com/Kavodax&lt;/a&gt; &lt;/p&gt;

</description>
      <category>opensource</category>
      <category>interledgerfoundation</category>
      <category>stablecoins</category>
      <category>ilfgrantee</category>
    </item>
    <item>
      <title>Wava: Exploring How Open Payments Could Connect Latin America's Domestic Payment Rails</title>
      <dc:creator>Carlos Agudelo</dc:creator>
      <pubDate>Fri, 25 Sep 2026 22:28:41 +0000</pubDate>
      <link>https://community.interledger.org/wava/wava-exploring-how-open-payments-could-connect-latin-americas-domestic-payment-rails-4nek</link>
      <guid>https://community.interledger.org/wava/wava-exploring-how-open-payments-could-connect-latin-americas-domestic-payment-rails-4nek</guid>
      <description>&lt;p&gt;&lt;em&gt;An Open Payments Accelerator project by Wava · Colombia and Peru&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The Payment Problem We're Exploring
&lt;/h2&gt;

&lt;p&gt;Latin America has quietly built some of the fastest and cheapest domestic payment systems in the world. In Colombia, money moves instantly through wallets tens of millions of people use daily. In Peru, QR payments clear through the compensation chamber in seconds. Inside any one country, paying has never been easier.&lt;/p&gt;

&lt;p&gt;Cross a border, and that progress disappears. Each system was built for its own market, with its own rules, its own currency, and no shared way to address an account on the other side. A business operating in Colombia and Peru cannot simply move money between them. It either builds a separate integration, banking relationship, and compliance process in each country, or falls back on correspondent banking and card networks that are slower and costlier than the local rails sitting at both ends of the same transaction.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;The businesses most likely to benefit from instant, low-cost payments are often the least able to reach across a border.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Who Is This For?
&lt;/h2&gt;

&lt;p&gt;On the sending side is an everyday customer in Peru paying for something — a marketplace purchase, a subscription, a service. They want to pay the way they always do, without knowing the business is in another country.&lt;/p&gt;

&lt;p&gt;On the receiving side is a merchant operating across more than one Latin American market, carrying the fragmentation: separate integrations per country, balances in unconnected systems, and the cost of moving its own money home. For a large company, it is an annoyance. For a smaller merchant, it is often why they never expand across the border at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  What We Want to Test
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;We believe Open Payments can help merchants operating across Latin American markets to collect in one country and receive funds in another, by providing a shared way to address, quote, and clear a payment between systems that were never designed to connect.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;What we do not know is whether an open standard can sit above national infrastructure without requiring it to change. Domestic rails are stable, regulated, and widely adopted; anything asking them to adopt something new is unlikely to get far. What interests us is interoperability that is additive rather than disruptive.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Payment Flow We'll Explore
&lt;/h2&gt;

&lt;p&gt;We have deliberately narrowed to a single flow, in one direction, between two countries where we already operate.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Customer in Peru → pays through a local payment method → Open Payments addressing, quoting and clearing → merchant receives funds in Colombian pesos&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A customer in Peru pays using a local QR-based method, cleared through the compensation chamber. The Colombian destination account is identified through an Open Payments address, and the conversion is quoted before anything moves. The transfer clears between two connector nodes we operate, and the merchant is paid out in Colombian pesos through a domestic rail.&lt;/p&gt;

&lt;p&gt;The merchant sees one transaction and one reconciled record instead of two disconnected balances. The return direction is a stretch goal, not a promise.&lt;/p&gt;

&lt;h2&gt;
  
  
  How We Plan to Use Open Payments
&lt;/h2&gt;

&lt;p&gt;Open Payments sits in the middle of this flow, not at either end. The local methods on both sides stay exactly as they are.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Addressing&lt;/strong&gt; — a standard way to identify the receiving account across the border, so neither country's system needs a bespoke integration with the other.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quoting&lt;/strong&gt; — a consistent way to know what a cross-currency transfer costs before it executes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Clearing&lt;/strong&gt; — moving value between two connector nodes we run ourselves, using Rafiki, so neither domestic rail needs a direct relationship with the other.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What We Hope to Demonstrate
&lt;/h2&gt;

&lt;p&gt;By the end of the four months, we aim to show a working corridor between Peru and Colombia in a controlled near-live environment. Three indicators will tell us whether it worked:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A payment completes end to end — collected in Peru, cleared at a locked rate, paid out in Colombian pesos. Funds release only against confirmed bank settlement: that gate is by design, not a gap.&lt;/li&gt;
&lt;li&gt;Every transaction reconciles across the clearing record, our ledger, and settlement on each rail. Where it does not, we want to know exactly why.&lt;/li&gt;
&lt;li&gt;At least one merchant we already work with completes the flow and tells us whether it solves their real problem.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We are not aiming to launch a product in four months. We are aiming to find out whether this works, and to be honest about where it does not.&lt;/p&gt;

&lt;h2&gt;
  
  
  Looking Beyond the Accelerator
&lt;/h2&gt;

&lt;p&gt;If it works, the next steps are real production volume and extending the pattern to further markets, Ecuador being the most obvious. The more interesting question is whether it generalises: a layer that connects two countries without either rail changing could, in principle, connect many.&lt;/p&gt;

&lt;h2&gt;
  
  
  What We're Excited to Learn
&lt;/h2&gt;

&lt;p&gt;We arrive with real infrastructure but limited hands-on experience with Interledger. That is exactly why the Accelerator appealed to us. Three questions we want to answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How do our cross-currency design, locked quotes, clearing decoupled from batched settlement, and gated release hold up in practice? FX is the one piece we've never operated; pressure-testing it with the Interledger team is the draw.&lt;/li&gt;
&lt;li&gt;Where does the standard hold against real domestic infrastructure, and where does it strain? We expect to find edges the documentation does not show.&lt;/li&gt;
&lt;li&gt;What does a merchant need to see for this to feel trustworthy? Interoperability only matters if the person receiving the money believes it will arrive.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  About Wava
&lt;/h2&gt;

&lt;p&gt;Wava builds API-based collections, disbursements, and treasury tools on top of Latin America's local payment rails, for fintechs, marketplaces, and e-commerce businesses that need to move money through the methods their customers actually use. Our infrastructure is live in Colombia and Peru, under local entities and banking sponsorship in both markets.&lt;/p&gt;

&lt;p&gt;Our founding team: Carlos Agudelo, who has spent over a decade building companies across the region, and Luciano Pallotti, who previously built infrastructure for corporates and governments and now builds and runs Wava's platform. We came to this problem by hitting it ourselves — after doing the unglamorous work of establishing banking and compliance in two countries, we still couldn't offer merchants something as basic as moving their money between them.&lt;/p&gt;

&lt;p&gt;Learn more at &lt;a href="https://wava.co" rel="noopener noreferrer"&gt;wava.co&lt;/a&gt;.&lt;br&gt;
Explore our Public API at &lt;a href="https://docs.wava.co" rel="noopener noreferrer"&gt;docs.wava.co&lt;/a&gt;.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Happy by ShujaaPay: Exploring Open Payments-Native Content Hosting &amp; Real-time Mobile Wallet Settlement</title>
      <dc:creator>Rewel Mumbo</dc:creator>
      <pubDate>Tue, 22 Sep 2026 13:35:58 +0000</pubDate>
      <link>https://community.interledger.org/shujaapay/-happy-by-shujaapay-exploring-open-payments-native-content-hosting-real-time-mobile-wallet-4kk6</link>
      <guid>https://community.interledger.org/shujaapay/-happy-by-shujaapay-exploring-open-payments-native-content-hosting-real-time-mobile-wallet-4kk6</guid>
      <description>&lt;h2&gt;
  
  
  &lt;strong&gt;The Payment Problem We're Exploring&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Amina Wanjiku produces viral digital stories and cultural documentation on local heritage from her base in Turkana. &lt;br&gt;
Although her work regularly reaches hundreds of thousands of viewers, her monthly income from these videos remains negligible.&lt;br&gt;
Crucially, this shortfall stems from a deep-seated infrastructure gap: global creator platforms rely heavily on credit cards, operating under the assumption that fans will set up recurring monthly subscriptions. &lt;/p&gt;

&lt;p&gt;In Kenya, however, credit card adoption remains below 5%, whereas more than 30 million adults rely on Safaricom's M-Pesa every day for their routine transactions.&lt;/p&gt;

&lt;p&gt;Consequently, existing payment pathways struggle to support localized monetization.&lt;br&gt;
 Viewers who wish to back creators or unlock individual video segments for Kes 20 shillings (approx $0.015) frequently lack access to international cards. &lt;br&gt;
Furthermore, regional ad rates remain low, and international payment systems rarely support direct mobile wallet payouts without imposing steep exchange fees or extended hold periods.&lt;br&gt;
 As a result, willing audiences and local creators remain separated by fundamentally incompatible payment systems.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Who Is This For?&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;To address these challenges, this initiative focuses on two distinct groups within the creative economy:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Content Receivers (Creators):&lt;/strong&gt; Independent video journalists, podcasters, writers, and educators across East Africa who require direct payouts into their primary mobile money accounts without payout minimums or platform holds.&lt;br&gt;
&lt;strong&gt;Content Consumers (Supporters):&lt;/strong&gt; Domestic mobile users looking to send small tips or pay for individual pieces of content directly from their phone balances, alongside international fans seeking a straightforward way to contribute in their local currencies without high transfer fees.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://community.interledger.org/remoteimages/uploads/articles/pqhb0rsp39hri7ox6pa8.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://community.interledger.org/remoteimages/uploads/articles/pqhb0rsp39hri7ox6pa8.jpeg" alt=" " width="1376" height="768"&gt;&lt;/a&gt;&lt;br&gt;
Figure 2: Happy Portal creator dashboard showing live tips, content unlocks, and mobile balance management.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;What We Want to Test&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;CORE HYPOTHESIS:&lt;/strong&gt; &lt;em&gt;Open Payments standards can enable sustainable digital content monetization in Africa by bridging global funding sources with local mobile money rails through low-cost micro-transactions.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;To test this hypothesis, the project evaluates whether open payment standards offer a practical alternative to restrictive paywalls and conventional credit card processing. &lt;br&gt;
By piloting sub-shilling media metering alongside low-cost single-item unlocks, we aim to demonstrate that flexible payment options can effectively sustain creators while remaining accessible to mobile-first users.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;The Payment Flow We'll Explore&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Specifically, the primary payment workflow to be tested during the program connects online user interactions directly to real-time mobile wallet settlement:&lt;br&gt;
[Supporter on Mobile or Web]  →  [Tap 'Unlock for KES 20']  →  [Open Payments &amp;amp; Interledger Routing]  →  [Instant M-Pesa Payout to Creator]&lt;/p&gt;

&lt;p&gt;In practice, when a supporter selects content on the &lt;a href="https://happy.shujaapay.me/" rel="noopener noreferrer"&gt;Happy Portal&lt;/a&gt;, the system seamlessly resolves the creator's wallet address, generates a fee quote, and requests transaction approval. &lt;br&gt;
Value then moves across the Interledger network, granting immediate access to the content while instantly settling funds into the creator's M-Pesa account.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://community.interledger.org/remoteimages/uploads/articles/8lsiygp8o8wyamf8hax4.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.interledger.org/remoteimages/uploads/articles/8lsiygp8o8wyamf8hax4.png" alt=" " width="1189" height="1294"&gt;&lt;/a&gt;&lt;br&gt;
Figure 3: Overview of the payment and settlement architecture from user action to wallet deposit.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;How We Plan to Use Open Payments&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;To accomplish this, Open Payments serves as the underlying interoperability protocol for the portal, successfully replacing proprietary payment gateways and fragmented networks:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Universal Wallet Addresses:&lt;/em&gt;&lt;/strong&gt; Standardized handles simplify account discovery and payment routing across different platforms.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Quotes and Incoming Payments:&lt;/em&gt;&lt;/strong&gt; Real-time exchange rates are calculated before processing, providing clear conversion details between foreign currencies and Kenyan Shillings.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Interactive Grants:&lt;/em&gt;&lt;/strong&gt; Defined authorization parameters give supporters clear control over spending limits without exposing underlying account details.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Micro Payments:&lt;/em&gt;&lt;/strong&gt; Enabling sub-shilling media metering and low-cost single-item unlocks for fine-grained content access.&lt;/p&gt;

&lt;p&gt;Ultimately, routing transactions over the Interledger Protocol enables effortless cross-currency transfers. &lt;br&gt;
This allows international supporters to pay in their preferred local currency, while creators receive their earnings directly in local mobile money.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;What We Hope to Demonstrate&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;By the end of the accelerator, we want to show something concrete: that a supporter anywhere in the world can tap once, and a creator in remote Kenya can receive real money in their M-Pesa wallet seconds later, without either of them touching a bank account, a card, or a foreign exchange desk.&lt;br&gt;
More specifically, we aim to validate three key outcomes:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Working Global-to-Local Rails:&lt;/em&gt;&lt;/strong&gt; Open Payments and the Interledger Protocol can carry real value between global wallets and local mobile money rails, not as a proof of concept on a slide but as a working flow that ordinary people can use.&lt;br&gt;
&lt;strong&gt;&lt;em&gt;Meaningful Micro-Payments:&lt;/em&gt;&lt;/strong&gt; Creators can earn from micro-payments small enough to feel natural, where twenty Kenyan shillings (approx $0.015) is a transaction and not a rounding error, and where the creator keeps the vast majority of what their audience pays.&lt;br&gt;
&lt;strong&gt;&lt;em&gt;Reusable Open Tooling:&lt;/em&gt;&lt;/strong&gt; This model can be opened up for other builders, so the tools we develop around RFC 9421 signing, GNAP authorization, and mobile money settlement become reusable pieces that strengthen the wider Interledger ecosystem.&lt;/p&gt;

&lt;p&gt;The deeper point is about fairness. Right now, the global creator economy extracts value from African creators and returns very little of it. If we can prove that open, interoperable payment rails can reverse that flow, we will have shown something that matters far beyond Kenya.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Looking Beyond the Accelerator&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Following the initial pilot in Kenya, subsequent expansion plans will focus on integrating additional mobile money providers across East and West Africa, including MTN MoMo and Airtel Money.&lt;br&gt;
Connecting regional mobile wallet infrastructure directly to open financial standards builds broader access across the digital economy. &lt;br&gt;
In tandem with this growth, the project also intends to publish open-source client adapters to help regional publishers easily implement similar payment capabilities.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;What We're Excited to Learn&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;From a behavioral standpoint, we want to observe how African audiences respond to frictionless micro-unlocks compared to traditional monthly subscriptions. &lt;br&gt;
Technically, we are eager to evaluate Open Payments API, RFC 9421 signature verification and Rafiki Interledger connectors over volatile mobile data connections, and we look forward to sharing these findings openly with the broader Interledger community.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;About ShujaaPay&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;ShujaaPay is a financial technology infrastructure company based in Nairobi Kenya, founded by Rewel Mumbo and Naaman Kiptoo. &lt;br&gt;
We build open, borderless payment rails for Africa's digital workforce, developing AI-powered financial inclusion software that connects open payment standards directly with African payment networks. &lt;/p&gt;

&lt;p&gt;Through Happy, our goal is to give African creators full financial access and dignity. Accordingly, we are deeply grateful to the Interledger Foundation for supporting this work through the Open Payments Accelerator Program 2026.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;## &lt;strong&gt;Our Team&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Rewel Mumbo is a Senior Data Scientist, entrepreneur, and student at &lt;a href="https://ouk.ac.ke/" rel="noopener noreferrer"&gt;The Open University of Kenya&lt;/a&gt;; he leads ShujaaPay as the Founder and CEO, while Naaman Kiptoo is a software engineer, co-founder and our Chief Technology Officer. &lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;What We're Already Building&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;ShujaaPay is not starting from scratch. We already operate a production-ready Open Payments gateway with a self-hosted Rafiki connector, live Bank and M-Pesa B2C payout connectors, and a TigerBeetle double-entry ledger engine.&lt;br&gt;
We are also building cross-border payment tools for freelancers, remote workers, and digital creators who need to receive payments from international clients and platforms without the delays and fees of legacy intermediaries.&lt;br&gt;
Our work extends to AI-agent commerce through the ShujaaPay Model Context Protocol (MCP) Server, which enables autonomous agents to execute cross-border payouts to bank accounts and mobile money rails.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Communities and Markets We Serve&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We work with independent African creators, freelancers, and digital workers who earn from global platforms but are locked out of fair payout rails. &lt;br&gt;
Our markets span Kenya, Uganda, Ghana, Nigeria, and the wider East and West African region, with plans to expand to North America, Middle Eeast, Europe, Latin America and South Asia.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;What Motivated Us&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We started ShujaaPay after witnessing firsthand how African creators and freelancers are excluded from the global digital economy. Through research at &lt;a href="https://ouk.ac.ke/" rel="noopener noreferrer"&gt;The Open University of Kenya&lt;/a&gt; and creator communities like the &lt;a href="https://dccak.ke/" rel="noopener noreferrer"&gt;Digital Content Creators Association of Kenya (DCCAK)&lt;/a&gt;, we identified several financial interoperability gaps in content monetization. &lt;/p&gt;

&lt;p&gt;International payment platforms charge exorbitant fees, impose arbitrary holds, and often refuse to serve African accounts entirely. Domestically, mobile money dominates, yet it remains disconnected from global payment standards. &lt;br&gt;
We built ShujaaPay to close that gap and to prove that open protocols like Open Payments and Interledger can deliver real financial inclusion for the Global South.&lt;/p&gt;

&lt;p&gt;Learn more and follow our journey at: &lt;br&gt;
&lt;a href="https://happy.shujaapay.me" rel="noopener noreferrer"&gt;https://happy.shujaapay.me&lt;/a&gt;&lt;br&gt;
&lt;a href="https://www.shujaapay.me" rel="noopener noreferrer"&gt;https://www.shujaapay.me&lt;/a&gt;,&lt;br&gt;
&lt;a href="https://www.linkedin.com/in/rewel-mumbo-20ab4253/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/rewel-mumbo-20ab4253/&lt;/a&gt;, &lt;a href="https://www.linkedin.com/in/nv-ms/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/nv-ms/&lt;/a&gt;,&lt;br&gt;
&lt;a href="https://www.linkedin.com/company/shujaapay/" rel="noopener noreferrer"&gt;https://www.linkedin.com/company/shujaapay/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>interledgerprotocol</category>
      <category>ilfgrantee</category>
      <category>interledgerfoundation</category>
    </item>
    <item>
      <title>Interledger Foundation Launches 2026 NextGen Higher Education Grant</title>
      <dc:creator>Julaire Hall</dc:creator>
      <pubDate>Tue, 15 Sep 2026 17:26:50 +0000</pubDate>
      <link>https://community.interledger.org/interledger/interledger-foundation-launches-2026-nextgen-higher-education-grant-oml</link>
      <guid>https://community.interledger.org/interledger/interledger-foundation-launches-2026-nextgen-higher-education-grant-oml</guid>
      <description>&lt;p&gt;&lt;strong&gt;Universities and higher education institutions are invited to submit Letters of Intent for projects preparing students to shape the future of open, inclusive digital finance.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The 2026 Call for Letters of Intent for the Interledger–NextGen Higher Education Grant is now open! This grant supports universities and higher education institutions that want to create meaningful learning and hands-on experiences around &lt;a href="https://interledger.org/open-payments" rel="noopener noreferrer"&gt;Open Payments&lt;/a&gt;, interoperability, digital financial inclusion, and emerging financial technologies.&lt;/p&gt;

&lt;p&gt;Through NextGen, institutions can receive up to USD $50,000 for projects of up to 12 months that give students opportunities to learn, research, experiment, build, and engage with the ideas and technologies shaping the future of digital financial systems.&lt;/p&gt;

&lt;p&gt;For the Interledger Foundation, education is an important part of building a more open and interoperable financial ecosystem. Creating the infrastructure for a different kind of financial future also means ensuring the next generation of developers, entrepreneurs, researchers, policymakers, and financial leaders has the knowledge and opportunity to help build it.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;NextGen is about investing in people as much as it is about technology. If we want a future where financial systems are more open, interoperable, and inclusive, we have to give students the opportunity to understand these systems, question them, and imagine what comes next. Education is an important part of Interledger’s strategy because the students learning and experimenting today will be among the people designing, implementing, and advocating for the financial infrastructure of tomorrow&lt;/em&gt;.&lt;br&gt;
  — &lt;strong&gt;Chris Lawrence, Chief Program Officer, Interledger Foundation&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Over the past several years, the Interledger Foundation has worked with higher education institutions across different regions to explore what this kind of learning can look like in practice. Our NextGen education community has included institutions such as the &lt;strong&gt;University of Cape Town in South Africa, Bowie State University, Benedict College, and Alabama A&amp;amp;M University in the United States, The Hague University of Applied Sciences in the Netherlands, United States International University-Africa in Kenya, Covenant University in Nigeria, and Western Sydney University in Australia&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Across these institutions, students and faculty have explored Open Payments through workshops, curriculum development, research, hackathons, technical experimentation, entrepreneurship programs, and other campus-based activities. Each institution has approached the work differently, reflecting an important part of the NextGen vision: building local capacity while connecting students to a broader global conversation about the future of financial systems.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What We’re Looking For in 2026&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We are interested in partnering with institutions that can create faculty-led, student-centered initiatives that move beyond awareness and give students meaningful opportunities to engage with open payments and digital financial inclusion.&lt;/p&gt;

&lt;p&gt;Projects may include curriculum development, student labs, research, hackathons, technical exploration, prototype development, interdisciplinary learning, and other approaches that connect academic learning with real-world challenges.&lt;/p&gt;

&lt;p&gt;Institutions interested in participating are invited to submit a two-page Letter of Intent on their university’s official letterhead, introducing their institution, proposed project, intended students and participants, key activities, anticipated outcomes, and connection to Open Payments and interoperability.&lt;/p&gt;

&lt;p&gt;Shortlisted institutions will subsequently be invited to develop and submit a full proposal.&lt;/p&gt;

&lt;p&gt;Learn more about the &lt;a href="https://interledger.org/grant/education/nextgen" rel="noopener noreferrer"&gt;&lt;strong&gt;Interledger–NextGen Higher Education Grant&lt;/strong&gt;&lt;/a&gt;, review the &lt;a href="https://drive.google.com/drive/u/0/folders/1Ung_SdO7MuTTy-DAKHNj4fhRNUkL1Jp1" rel="noopener noreferrer"&gt;&lt;strong&gt;2026 Program Resource Kit&lt;/strong&gt;&lt;/a&gt; to access the application guidelines, and submit your Letter of Intent through the Interledger Foundation’s application portal. &lt;strong&gt;Applications for Phase 1 are reviewed on an ongoing basis, and applications close on Monday, December 14, 2026&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;We’re looking forward to meeting the next group of institutions and students, helping to imagine what an open and inclusive financial future can become.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://submit.interledger.org/submit/366290/2026-interledger-nextgen-higher-education-call-for-lois/eligibility" rel="noopener noreferrer"&gt;APPLY NOW BUTTON&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>education</category>
      <category>nextgen</category>
      <category>openpayments</category>
      <category>announcements</category>
    </item>
    <item>
      <title>FLIQA'S Second Interim Project Report</title>
      <dc:creator>Ela Oblak</dc:creator>
      <pubDate>Fri, 11 Sep 2026 14:59:15 +0000</pubDate>
      <link>https://community.interledger.org/elaoblak_537/fliqas-second-interim-project-report-2o4a</link>
      <guid>https://community.interledger.org/elaoblak_537/fliqas-second-interim-project-report-2o4a</guid>
      <description>&lt;h2&gt;
  
  
  Brief Project Description
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;FLIQA&lt;/strong&gt; uses open banking to enable direct account-to-account payments, helping businesses reduce costs, eliminate intermediaries, and manage finances more efficiently. Users enjoy greater transparency and security with every transaction. &lt;br&gt;
By integrating &lt;strong&gt;the Interledger Protocol&lt;/strong&gt; alongside traditional banking infrastructure, FLIQA aims to improve interoperability between different payment systems and expand access to modern payment infrastructure for SMEs and underserved communities. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Through Open Payments APIs&lt;/strong&gt;, the platform supports new payment flows across currencies and ledgers, providing a secure, low-cost alternative to card- and cash-based payments while giving businesses greater control of their funds.&lt;/p&gt;

&lt;h2&gt;
  
  
  Project Update
&lt;/h2&gt;

&lt;p&gt;Months 5-8 marked an important time for the project: Interledger moved from being an additional account type in our data model to becoming a payment method users can choose, price, and complete. To support this transition, we rebuilt the FLIQA payment dialog around the Open Payments flow, extended the backend and the Payment/Service API to treat payment type as a first-class dimension, and introduced an ILF Sandbox so that partners and merchants can see and test the flow end- to- end without any production dependency.&lt;/p&gt;

&lt;p&gt;In parallel, we concentrated our business and market development efforts primarily on &lt;strong&gt;Colombia&lt;/strong&gt;. We conducted a detailed assessment of the Colombian regulatory environment for fintechs and financial institutions - including the transition towards a mandatory Open Finance regime under Decree 0368 of April 2026, the licensing perimeter of the Superintendencia Financiera, the position of small community banks and savings-and-credit cooperatives, and the operating conditions facing micro, small, and medium enterprises. We also assessed the practical requirements and implications of establishing a foreign fintech business in the market.&lt;/p&gt;

&lt;p&gt;The most significant milestone of the period is that we made first contact with &lt;strong&gt;Bre-B&lt;/strong&gt;, Colombia's interoperable instant payment system operated by Banco de la República. We connected to the Bre-B sandbox and successfully performed a manual payment initialisation. This is the first time FLIQA has touched a Colombian domestic payment rail directly, and it opens a credible path to offering ILP-based and domestic instant payments side by side within the same checkout.&lt;/p&gt;

&lt;p&gt;The honest counterpoint is that the UAE workstream remained deprioritised through this period. The geopolitical conditions identified in our previous report have not improved. We therefore made a deliberate decision to concentrate our engineering and commercial resources on Colombia rather than divide capacity between two markets.&lt;/p&gt;

&lt;h2&gt;
  
  
  Project Impact &amp;amp; Target Audience(s)
&lt;/h2&gt;

&lt;p&gt;Our target communities are underserved individuals and micro, small, and medium enterprises (&lt;strong&gt;MSMEs&lt;/strong&gt;) &lt;strong&gt;in Colombia&lt;/strong&gt;. The groups that ultimately benefit include Women &amp;amp; Girls, who remain measurably behind in both access to and active use of financial products in Colombia; Black, Indigenous, and People of Colour, particularly Afro-Colombian and Indigenous communities in rural departments where exclusion is deepest; People with disabilities, for whom a digital-first, device-independent payment flow removes the need to reach a physical branch; and informal-economy participants and rural populations with no bank branch within reach.&lt;/p&gt;

&lt;p&gt;What changed in this period is that the impact case moved from argument to mechanism. Colombia's headline inclusion figure is high - roughly 96% of adults hold some deposit or credit product -  but the distribution behind it is what matters for our work. Rural access sits around 66% against near-universal urban access, and active use falls to roughly 53% in rural areas against about 89% in urban ones. A persistent gender gap of several percentage points runs through both access and use. Meanwhile, more than 70% of transactions in the country are still made in cash. The problem is therefore not primarily account ownership; it is that a very large number of people and micro-businesses hold an account they cannot but cannot use it practically for transactions, at a price they can accept, in the places they live and trade.&lt;/p&gt;

&lt;p&gt;This period’s work translates to that. Showing the fee to the user before they authorize a payment is not cosmetic: for a merchant with thin margins and for a payer sending a small amount, an unpriced payment is an untrusted payment. Removing the country-and-provider selection step in favor of direct provider selection reduces the number of decisions a first-time or low-confidence user has to make. Accepting a Payment Pointer as an input, with validation, means an ILP identity is now something a Colombian merchant can be paid through without understanding anything about the protocol behind it. And the Bre-B connection means we can put an interoperable, effectively free-to-end-user domestic rail next to the ILP rail in the same interface, which is the practical form financial inclusion takes in this market.&lt;/p&gt;

&lt;p&gt;On the &lt;strong&gt;institutional side&lt;/strong&gt;, our regulatory research identified a specific and underserved constituency that we had not fully appreciated at the outset: Colombia's savings-and-credit cooperatives and small community financial institutions. Around 171 cooperatives carry out financial intermediation in Colombia, serving over four million members, employing close to 14,000 people, and operating across 23 of the country's 32 departments. In roughly 40 municipalities, a cooperative is the only financial intermediary with any physical presence at all. Because most of these entities sit under the Superintendencia de Economía Solidaria rather than the Superintendencia Financiera, they fall largely outside the perimeter of the mandatory Open Finance regime and are slower to appear in the national instant-payment ecosystem. That is precisely the gap an interoperable, ledger-agnostic protocol is built to close, and it has become an explicit part of our Colombian impact thesis.&lt;/p&gt;

&lt;h2&gt;
  
  
  Progress on Objectives, Key Activities
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Product: a payment dialog rebuilt for Interledger
&lt;/h3&gt;

&lt;p&gt;Our first report described extending the data model to hold Open Payments accounts and payment pointers. In this period, we took the next step and altered the user-facing payment dialog so that an ILF payment is a first-class option rather than a special case added onto an open-banking flow. Three changes were necessary:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Direct provider selection&lt;/strong&gt; at the start of the payment. Previously, a payer had to select a country and then a provider before anything else could happen - a sequence that makes sense for bank-based open banking but not for Interledger, where the provider is not tied to a jurisdiction. The payer now selects the provider directly when the payment is initiated.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Display the fee to the user&lt;/strong&gt;. The dialog now displays the applicable fee before the payer authorizes the payment. This is a transparency requirement we consider non-negotiable for the communities we serve, and it is also what allows a payer to make a genuine comparison between an ILP payment and the alternatives available to them.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Payment Pointer as a direct input&lt;/strong&gt;, with validation. The payer can enter a Payment Pointer as the destination, with format and resolution checks performed at entry, so that errors are identified immediately rather than at settlement.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Taken together, these changes mean the Open Payments flow is now materially shorter and clearer than our standard open-banking flow, which is a useful demonstration. &lt;/p&gt;

&lt;h3&gt;
  
  
  2. Backend and API: payment type as a first-class dimension
&lt;/h3&gt;

&lt;p&gt;Supporting these changes required corresponding changes to the underlying infrastructure. We altered the payment providers table to hold the supported payment types and altered the provider service to filter providers by that type. On the Payment API and Service API, we exposed the listing of payment providers by payment type - Open Banking, ILF, and future types - so that any client of our API can retrieve exactly the set of providers relevant to the rail it intends to use.&lt;/p&gt;

&lt;p&gt;This is deliberately generic. It means adding a further rail - Bre-B being the immediate candidate - is a matter of registering a payment type and its providers rather than a further round of interface changes&lt;/p&gt;

&lt;h3&gt;
  
  
  3. ILF Sandbox (additional effort beyond the original scope)
&lt;/h3&gt;

&lt;p&gt;We added an &lt;strong&gt;ILF Sandbox&lt;/strong&gt; for demonstration and testing purposes. This was not in the original plan and represents additional effort taken on during this period, but it proved necessary: partners and prospective merchants consistently asked to see the flow before committing, and integrators need a non-production environment to work against.  The sandbox demonstrates the complete ILF payment flow and materially eases integration for third parties, streamlining subsequent partner and integration discussions.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Colombia: first steps on the Bre-B integration
&lt;/h3&gt;

&lt;p&gt;Bre-B is Colombia's interoperable instant payment system, operated by Banco de la República. Its interoperability and settlement mechanism went live on 23 September 2025, with the system fully opening on 6 October 2025, with 227 participating financial institutions. Users transact through "llaves" - simple aliases that stand in for full account details - and the system runs 24/7. Adoption has been rapid: by mid-2026, the ecosystem had registered well over 100 million keys and around 35 million linked users, processing approximately &lt;strong&gt;five million&lt;/strong&gt; operations per day, and transfers are free to end users until at least 2028.&lt;/p&gt;

&lt;p&gt;During this period, we connected to the Bre-B sandbox and manually performed a payment initialization. This validates FLIQA's ability to connect to the rail and gives us a concrete basis for the next stage of work. The immediate next steps are to offer Bre-B as an additional payment tier on the FLIQA Point of Sale, and to integrate it into the FLIQA sandbox environment alongside the ILF Sandbox so that the two rails can be demonstrated and tested side by side.&lt;/p&gt;

&lt;p&gt;The strategic point for the Interledger community is that this is not a competing choice. Bre-B is an excellent domestic rail but is not designed for cross-border payments; Interledger addresses the cross-border use case. A merchant checkout that can present both, priced transparently and selected by the payer, is a stronger argument for Open Payments in Latin America than either rail alone.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Colombia: regulatory and business-environment assessment
&lt;/h3&gt;

&lt;p&gt;A substantial share of our effort in Months 5–8 went into understanding, in detail, what it would take to operate in Colombia. &lt;strong&gt;The findings below&lt;/strong&gt; shaped both our product decisions and our go-to-market sequencing, and we share them here because we believe they are useful to other Interledger grantees considering the region.&lt;/p&gt;

&lt;h4&gt;
  
  
  5.1 The supervisory perimeter and licensing
&lt;/h4&gt;

&lt;p&gt;Colombia does not have a single, dedicated "fintech licence". Activities are regulated by what an entity does rather than what it calls itself, and the Superintendencia Financiera de Colombia (SFC) supervises every entity that takes funds from the public. The relevant regulatory structure is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;SEDPE&lt;/strong&gt; (Sociedad Especializada en Depósitos y Pagos Electrónicos) — the e-money and electronic deposits licence. It permits deposit-taking, electronic deposit accounts, and card issuance, but explicitly prohibits financial intermediation, i.e., lending. Minimum capital is in the order of 2 million USD. &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Compañía de financiamiento&lt;/strong&gt; — an intermediate tier that may both take deposits and lend. &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Establecimiento bancario&lt;/strong&gt; — a full banking licence, with minimum capital in the order of USD 30 million.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Authorisation typically takes over a year. Separately, Decreto 1692 of 2020 governs low-value payment systems and the acquiring activity: it opened acquiring to new entrants, defined the distinct roles in the payment chain, and set governance and access-transparency obligations for payment system administrators and payment service providers. For FLIQA, the significant conclusion is that a properly structured partnership model - operating alongside a licensed local entity rather than seeking our own deposit-taking licence - is not only faster but also the more appropriate regulatory approach for our business model. This is a direct validation of the KAMIN partnership strategy set out in our first report.&lt;/p&gt;

&lt;h4&gt;
  
  
  5.2 Open Finance: from voluntary to mandatory
&lt;/h4&gt;

&lt;p&gt;The most consequential development of the reporting period is that Colombia moved its Open Finance framework from voluntary to mandatory. Decree 0368, signed on 7 April 2026, establishes a mandatory Sistema de Finanzas Abiertas covering entities supervised by the SFC - credit institutions, SEDPEs, trust companies, brokers, pension fund managers, insurers, and collaborative financing entities. It rests on the principle that the data belongs to the user rather than to the entity holding it, and requires prior, express, informed, and revocable consent, with the receiving entity separately confirming authorisation before it accesses data.&lt;/p&gt;

&lt;p&gt;The implementation runway matters for our timing: the SFC has up to six months from the decree to publish technical standards, up to twelve months to launch the participant directory, and obliged entities then have a further twelve months (extendable by six) to enable data access. In other words, the operative APIs land well after our grant period, and any Colombian deployment inside the grant window must be built on today's bilateral and partner-mediated arrangements rather than on the mandatory regime.&lt;/p&gt;

&lt;p&gt;Two features of the final decree are directly relevant to us and were not present in the draft. First, payment initiation was &lt;strong&gt;structurally separated&lt;/strong&gt; from the Open Finance framework. Colombia has therefore mandated data sharing but not payment initiation, which leaves initiation to be arranged contractually - and leaves a gap that an interoperable payment standard could help address. Second, the final text dropped the requirement that &lt;strong&gt;data recipients also act as data providers&lt;/strong&gt; and removed the trusted-third-party verification layer, which lowers the barrier to participation for a company in our position. Colombia is behind Brazil on Open Finance maturity but is moving faster than Mexico or Chile, which we read as a favorable window.&lt;/p&gt;

&lt;h4&gt;
  
  
  5.3 Small community banks and cooperatives
&lt;/h4&gt;

&lt;p&gt;Colombia's community-level financial institutions are structurally distinct from its banks, and this emerged as one of the more important findings of our research. Financial intermediation at the community level is carried out largely by cooperatives, split into two supervisory regimes: cooperativas financieras, which fall under the SFC, and the much larger group of cooperativas de ahorro y crédito, which fall under the Superintendencia de Economía Solidaria. Around 171 such entities operate, with more than 4.2 million members - a gain of over 600,000 in five years - nearly 14,000 employees, and coverage across 23 of the 32 departments. In approximately 40 municipalities, the local cooperative is the only financial intermediary with a physical presence.&lt;/p&gt;

&lt;p&gt;Because most of these institutions sit outside the SFC perimeter, they are largely outside the scope of the mandatory Open Finance regime and are slower and less well-resourced to connect to national payment infrastructure. They serve exactly the rural, low-income and Indigenous populations the grant targets, and they have neither the technical capacity nor the regulatory obligation to build interoperability themselves. We regard this as the clearest institutional opportunity for Open Payments in Colombia, and we will develop it further in the remainder of the grant.&lt;/p&gt;

&lt;h4&gt;
  
  
  5.4 Conditions for micro, small and medium enterprises
&lt;/h4&gt;

&lt;p&gt;MSMEs represent the demand side of our Colombian case. They constitute roughly 98% of the country's business landscape and generate approximately 80% of national employment. Of the more than 300,000 new productive units registered in 2024, over 99% were microenterprises. Yet fewer than 30% of MSMEs access formal credit, according to Bancóldex, and a significant proportion remain at a basic stage of digitalization,  according to the Ministry of Commerce, Industry and Tourism. Closure rates within the first five years are high, and financing access is a principal cause. &lt;/p&gt;

&lt;p&gt;The consequences for payment acceptance are concrete. A microenterprise operating largely in cash, with no formal credit history and limited digital tooling, cannot absorb card-scheme merchant fees, cannot wait days for settlement, and is unlikely to complete a complex onboarding process. An account-to-account payment with transparent pricing, low fees, immediate settlement, and a short onboarding process is not a marginal improvement for this segment - it can determine whether a business can accept digital payments at all. It is also the mechanism by which a business begins to build the transaction record that eventually unlocks credit.&lt;/p&gt;

&lt;h4&gt;
  
  
  5.5 Conditions for foreign entrants
&lt;/h4&gt;

&lt;p&gt;For a foreign company, Colombia is welcoming from a company-law perspective but demanding from a financial-regulatory perspective. Establishing a local vehicle - most commonly a Sociedad por Acciones Simplificada, or a branch of the foreign parent - is relatively straightforward and can be completed quickly, and foreign capital may hold full ownership. The friction lies elsewhere: foreign investment must be registered with Banco de la República under the exchange-control regime, and payment flows are subject to foreign-exchange reporting obligations that a payments business must design for from the outset rather than retrofit. Beyond the formalities, the main constraints remain those we identified in our first report and which this period's research confirmed: the SFC authorization timeline, the depth of incumbent relationships in merchant acquiring, and the practical impossibility of building institutional trust from outside the market at the speed a grant timeline requires. All of this continues to point to the partner-led entry model we have adopted.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. UAE and Pay10 — status
&lt;/h3&gt;

&lt;p&gt;Our first report scheduled the integration of Pay10's APIs for Month 8. That work has not proceeded. The geopolitical conditions in the region that we flagged in May have not eased, and rather than commit engineering resources to an integration whose commercial counterpart we cannot yet schedule with confidence, we held the UAE workstream at low intensity and redirected that capacity to Colombia and to the platform work described above. We want to be transparent with the Foundation that this is a real deviation from the month-by-month plan in our first report, not a reframing of it. Our assessment is that the platform work delivered instead — the payment dialog, the payment-type architecture, the sandbox — is rail-agnostic and directly reusable when the UAE integration does proceed, so the deviation delays rather than eliminates the value of this work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Communications and Marketing
&lt;/h2&gt;

&lt;p&gt;FLIQA continues to grow primarily through direct conversation -  networking events and direct engagement with partners, merchants, and industry stakeholders - while becoming more intentional about sharing our work publicly through LinkedIn posts, website updates, and other content focused on open banking, digital payments, and financial innovation. Our journey is documented on LinkedIn and on our website, in both English and Slovenian.&lt;/p&gt;

&lt;p&gt;We continued to use LinkedIn as our primary public communications channel, publishing content around open banking, Pay-by-Bank, payment interoperability, digital payments, and the broader development of the European payments ecosystem. These posts helped us communicate the project's progress beyond direct partner conversations and create a public record of our work. &lt;a href="https://www.linkedin.com/pulse/why-pay-by-bank-future-payments-fliqa-payments-fe05e/?trackingId=ZrnQzUCRZVFI1Hepe7N%2FnQ%3D%3D" rel="noopener noreferrer"&gt;link&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We also use Instagram to communicate topics related to open banking, digital payments and payment infrastructure through visual and accessible content, with the aim of making concepts that can be technically complex easier to understand. On LinkedIn, we similarly aim to make discussions around payment protocols, interoperability and financial innovation accessible to a broader audience, rather than communicating only to people with a technical or financial background. &lt;/p&gt;

&lt;p&gt;Our public communication is complemented by direct conversations with partners, merchants and other industry stakeholders. These conversations help us understand which aspects of Open Payments and Interledger require further explanation and inform how we communicate the technology and its practical benefits more clearly. &lt;/p&gt;

&lt;p&gt;Where relevant, we also used events and industry networking to communicate FLIQA's work and establish conversations with potential partners in the markets we are exploring. &lt;a href="https://www.linkedin.com/feed/update/urn:li:activity:7471130589593718784/" rel="noopener noreferrer"&gt;link&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The ILF Sandbox added in this period also serves a communications purpose: it gives us something concrete to show rather than simply describe when we introduce Open Payments to a prospective partner, which has already changed the character of those conversations.&lt;/p&gt;

&lt;p&gt;Taken together, these activities have allowed us to combine direct partner engagement with a more consistent public presence, while using the product and sandbox itself as practical communication and demonstration tools.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's Next?
&lt;/h2&gt;

&lt;p&gt;The remainder of the grant period is where the work moves from platform capability to deployment and validation in Colombia.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Bre-B as a payment tier on the FLIQA Point of Sale. Building on the successful sandbox initialization, we will expose Bre-B as an additional payment tier at the point of sale, alongside open banking and ILF payments.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Bre-B in the FLIQA sandbox environment. Integrating Bre-B into our sandbox so that merchants and integrators can test the domestic instant rail and the Interledger rail in the same environment.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;KAMIN API integration to gain access to local payment rails and expand our merchant reach in Colombia.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Completing the GateHub integration, including automated payment pointer acquisition and sandbox/test wallet configuration.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Colombian pilot with our first merchants, validating the end-to-end flow in a live environment. This remains the central deliverable of the grant.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;ILF and Open Payments visibility on the FLIQA website and tenant portal.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In the UAE, our position is that we will resume the Pay10 integration when regional conditions allow, but not within this grant window. We would rather deliver one credible pilot in Colombia than two incomplete ones.&lt;/p&gt;

&lt;h2&gt;
  
  
  Community Support
&lt;/h2&gt;

&lt;p&gt;Our ask from the first report stands and has become more specific. We are looking for an introduction to a Colombian merchant - or to someone who can introduce us to one -  willing to take part in the testing phase of our product. We need a partner who can help us verify the integration workflow, the payment flow, and the overall merchant experience in a real environment before we expand the rollout.&lt;/p&gt;

&lt;p&gt;Two further asks have emerged from this period's work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Contact with Colombian savings-and-credit cooperatives&lt;/strong&gt; or community financial institutions, or with the bodies that represent them. As set out above, these institutions serve the populations this grant targets, sit outside the mandatory Open Finance perimeter, and lack the capacity to build interoperability alone. If anyone in the Interledger community has a relationship in Colombia's cooperative financial sector, an introduction would be genuinely valuable.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Experience of running Open Payments alongside a domestic instant payment rail.&lt;/strong&gt; We are about to present Interledger and Bre-B as parallel options in the same checkout. If another grantee has done something comparable - with Pix, UPI, SPEI or similar - we would welcome a conversation about what worked, particularly on how the choice was presented to the payer and how fees were communicated.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Additional Comments
&lt;/h2&gt;

&lt;p&gt;One observation from this period may be useful to the Foundation more broadly. Colombia has just mandated open data sharing while deliberately leaving payment initiation outside that mandate. The country has simultaneously built a fast, free, high-adoption domestic instant rail in Bre-B. The combination creates an unusual opening: there is a regulated appetite for interoperability, a proven public willingness to adopt new payment rails, and no mandated standard for initiation — which is precisely the space Open Payments is designed to occupy. We therefore see Colombia as one of the more favourable jurisdictions for Interledger adoption in Latin America over the next two years, and we would be glad to share our regulatory research with other grantees working in the region.&lt;/p&gt;

&lt;h2&gt;
  
  
  Relevant Links / Resources
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Sources for the Colombian regulatory assessment&lt;/strong&gt;&lt;br&gt;
Decreto 0368 of 7 April 2026 (mandatory Open Finance System) — &lt;a href="https://dapre.presidencia.gov.co/normativa/normativa/DECRETO%20No.%200368%20DEL%2007%20DE%20ABRIL%20DE%202026.pdf" rel="noopener noreferrer"&gt;https://dapre.presidencia.gov.co/normativa/normativa/DECRETO%20No.%200368%20DEL%2007%20DE%20ABRIL%20DE%202026.pdf&lt;/a&gt; &lt;br&gt;
Brigard Urrutia — Colombia launches its mandatory Open Finance system — &lt;a href="https://www.bu.com.co/en/insights/noticias/colombia-launches-its-mandatory-open-finance-system" rel="noopener noreferrer"&gt;https://www.bu.com.co/en/insights/noticias/colombia-launches-its-mandatory-open-finance-system&lt;/a&gt; &lt;br&gt;
URF — Colombia consolida el Sistema de Finanzas Abiertas obligatorio — &lt;a href="https://www.urf.gov.co/w/colombia-consolida-el-sistema-de-finanzas-abiertas-obligatorio" rel="noopener noreferrer"&gt;https://www.urf.gov.co/w/colombia-consolida-el-sistema-de-finanzas-abiertas-obligatorio&lt;/a&gt; &lt;br&gt;
Banco de la República — Bre-B interoperability launch — &lt;a href="https://www.banrep.gov.co/en/news/bre-b-continues-progress" rel="noopener noreferrer"&gt;https://www.banrep.gov.co/en/news/bre-b-continues-progress&lt;/a&gt; &lt;br&gt;
Banco de la República — Working paper on Bre-B design, implementation and outlook — &lt;a href="https://www.banrep.gov.co/en/publications-research/working-papers/paper-bre-b-february-2026" rel="noopener noreferrer"&gt;https://www.banrep.gov.co/en/publications-research/working-papers/paper-bre-b-february-2026&lt;/a&gt; &lt;br&gt;
Banco de la República — Panorama of savings and credit cooperatives — &lt;a href="https://www.banrep.gov.co/es/publicaciones-investigaciones/reporte-estabilidad-financiera/recuadro-2-primer-semestre-2024" rel="noopener noreferrer"&gt;https://www.banrep.gov.co/es/publicaciones-investigaciones/reporte-estabilidad-financiera/recuadro-2-primer-semestre-2024&lt;/a&gt; &lt;br&gt;
Superintendencia Financiera de Colombia — SEDPE information — &lt;a href="https://www.superfinanciera.gov.co/publicaciones/10101317/informes-y-cifrascifrassociedades-especializadas-en-depositos-y-pagos-electronicos-sedpe-10101317/" rel="noopener noreferrer"&gt;https://www.superfinanciera.gov.co/publicaciones/10101317/informes-y-cifrascifrassociedades-especializadas-en-depositos-y-pagos-electronicos-sedpe-10101317/&lt;/a&gt; &lt;br&gt;
Decreto 1692 de 2020 — low-value payment systems and acquiring — &lt;a href="https://www.funcionpublica.gov.co/eva/gestornormativo/norma.php?i=153787" rel="noopener noreferrer"&gt;https://www.funcionpublica.gov.co/eva/gestornormativo/norma.php?i=153787&lt;/a&gt; &lt;br&gt;
Supersolidaria — Cooperativas de ahorro y crédito — &lt;a href="https://www.supersolidaria.gov.co/es/entidad/cooperativas-de-ahorro-y-credito" rel="noopener noreferrer"&gt;https://www.supersolidaria.gov.co/es/entidad/cooperativas-de-ahorro-y-credito&lt;/a&gt; &lt;br&gt;
OECD — Financing SMEs and Entrepreneurs 2026: Colombia — &lt;a href="https://www.oecd.org/en/publications/financing-smes-and-entrepreneurs-2026_075d8058-en/full-report/colombia_00b286cf.html" rel="noopener noreferrer"&gt;https://www.oecd.org/en/publications/financing-smes-and-entrepreneurs-2026_075d8058-en/full-report/colombia_00b286cf.html&lt;/a&gt; &lt;br&gt;
Facephi Observatory — Open Finance Colombia 2026 — &lt;a href="https://facephi.com/observatory/en/open-finance-colombia-2026-the-mandatory-path-toward-financial-inclusion/" rel="noopener noreferrer"&gt;https://facephi.com/observatory/en/open-finance-colombia-2026-the-mandatory-path-toward-financial-inclusion/&lt;/a&gt; &lt;/p&gt;

</description>
      <category>progressreports</category>
    </item>
    <item>
      <title>Bridgy Fed — ILF Grant Final Report</title>
      <dc:creator>Ryan</dc:creator>
      <pubDate>Wed, 09 Sep 2026 18:41:32 +0000</pubDate>
      <link>https://community.interledger.org/snarfed/bridgy-fed-ilf-grant-final-report-5hfp</link>
      <guid>https://community.interledger.org/snarfed/bridgy-fed-ilf-grant-final-report-5hfp</guid>
      <description>&lt;h2&gt;
  
  
  Image/Banner
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://community.interledger.org/remoteimages/uploads/articles/5vr0xexk2kshzz4uopd1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.interledger.org/remoteimages/uploads/articles/5vr0xexk2kshzz4uopd1.png" alt="A New Social logo" width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Brief Project Description
&lt;/h2&gt;

&lt;p&gt;Bridgy Fed is an infrastructure service that bridges ActivityPub, ATProto, and the web. The project was to bridge Web Monetization over Bridgy Fed so users on one side of the ecosystem could handle payments from the other.&lt;/p&gt;

&lt;h2&gt;
  
  
  Project Update
&lt;/h2&gt;

&lt;p&gt;We're done! We finished before publishing &lt;a href="https://community.interledger.org/quillmatiq/bridgy-fed-ilf-grant-progress-report-3gmg"&gt;our interim report&lt;/a&gt; last year, so the status and result are the same as there. From that report:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Over the last few months, we've completed our deliverables. We had two main goals:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Introduce a Web Monetization Lexicon for the ATmosphere (ATProto ecosystem standard)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;We partnered with the Lexicon Community to develop the ATProto standard, and the finalized shared lexicon is documented &lt;a href="https://github.com/lexicon-community/lexicon/tree/main/community%2Flexicon%2Fpayments#readme" rel="noopener noreferrer"&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Bridge Web Monetization between ActivityPub and ATProto&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The Bridgy Fed integration can be found &lt;a href="https://github.com/snarfed/bridgy-fed/issues/2098" rel="noopener noreferrer"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Project Impact &amp;amp; Target Audience(s)
&lt;/h2&gt;

&lt;p&gt;From &lt;a href="https://community.interledger.org/quillmatiq/bridgy-fed-ilf-grant-progress-report-3gmg"&gt;our interim report&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Our target audience is ActivityPub instance owners and ATProto platform developers who wish to include payments via the Web Monetization standard. Users or platform admins can bridge accounts over Bridgy Fed and expect platforms in the other ecosystem who also support Web Monetization to handle payments as if they were native.&lt;/p&gt;

&lt;p&gt;On the ATProto side, we've already seen the at://work professional social platform adopt the new Web Monetization lexicon we helped standardize. We're hoping to see more developers in either ecosystem take advantage of this new functionality.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Progress on Objectives, Key Activities
&lt;/h2&gt;

&lt;p&gt;We're done!&lt;/p&gt;

&lt;h2&gt;
  
  
  Communications and Marketing
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;We've been promoting this at conferences and in discussions with our various partners. This led to the at://work integration, along with some ActivityPub developers who have started working on Web Monetization integration. We'll hopefully have more platforms to share soon.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What’s Next?
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;We'll continue evangelizing this integration wherever we can and will be testing with developers who adopt it. &lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Community Support
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;We'd love to chat with other developers who are already integrating Web Monetization so we can test across ecosystems. Our goal is to have as many cross-network demos as possible to share with our users.&lt;/p&gt;

&lt;p&gt;We're also a non-profit run by two full-time volunteers and three volunteer board of directors. Any donations to our &lt;a href="https://www.patreon.com/ANewSocial" rel="noopener noreferrer"&gt;Patreon&lt;/a&gt; or &lt;a href="https://store.anew.social/" rel="noopener noreferrer"&gt;merch purchases&lt;/a&gt; would help sustain this project.&lt;/p&gt;
&lt;/blockquote&gt;

</description>
      <category>finalreport</category>
      <category>finalreports</category>
    </item>
    <item>
      <title>Reflections from UN Open Source Week 2026</title>
      <dc:creator>Vineel R. Pindi</dc:creator>
      <pubDate>Wed, 09 Sep 2026 14:31:00 +0000</pubDate>
      <link>https://community.interledger.org/interledger/reflections-from-un-open-source-week-2026-3n2k</link>
      <guid>https://community.interledger.org/interledger/reflections-from-un-open-source-week-2026-3n2k</guid>
      <description>&lt;p&gt;Nearly twenty years ago, I joined the open source movement as a student volunteer. Back then, I knew it mostly through the open web community: people from different countries and backgrounds working together on an open web browser. People could help shape something they used.&lt;/p&gt;

&lt;p&gt;If you’d told me back then that open source would become a priority for governments and major organisations, with these conversations taking place at the United Nations, I wouldn’t have believed it.&lt;/p&gt;

&lt;p&gt;In June 2026, I represented the &lt;a href="https://interledger.org/" rel="noopener noreferrer"&gt;Interledger Foundation&lt;/a&gt; at &lt;a href="https://www.unopensource.org/" rel="noopener noreferrer"&gt;UN Open Source Week&lt;/a&gt; in New York, alongside &lt;a href="https://www.linkedin.com/in/chrislarry" rel="noopener noreferrer"&gt;Chris Lawrence&lt;/a&gt;, our Chief Programs Officer. We met people working in government, universities and open source communities, including several of our partners. The discussions covered public services and payment systems that people depend on.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://community.interledger.org/remoteimages/uploads/articles/jpedvuze5i4xwgrdxdbq.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://community.interledger.org/remoteimages/uploads/articles/jpedvuze5i4xwgrdxdbq.jpeg" alt=" " width="1280" height="720"&gt;&lt;/a&gt;&lt;br&gt;
From left to right: David Higgings, Ed Cable, Chris Lawrence, Vineel Reddy&lt;/p&gt;

&lt;p&gt;The question that stayed with me through the week was:&lt;br&gt;
As governments and institutions adopt open source, how do we make sure the communities behind it have a say in the decisions?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://transcripts.un.org/en/asset/k1c/k1cqj3jcdx" rel="noopener noreferrer"&gt;DPI Day - Digital Public Infrastructure&lt;/a&gt; is about people&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One of the sessions that resonated with me was “&lt;a href="https://www.linkedin.com/posts/on-dpi-day-june-24-2026-cfi-and-some-share-7473117178481958912-wknp/" rel="noopener noreferrer"&gt;Building Inclusion: Identity, Payments, and the Real Cost of Digital Public Infrastructure&lt;/a&gt;” during DPI Day.&lt;/p&gt;

&lt;p&gt;The discussion went beyond building digital identity and payment systems to whether people could use and trust them.&lt;br&gt;
Chris and I reconnected with &lt;a href="https://www.linkedin.com/in/jayshreevenkatesan/" rel="noopener noreferrer"&gt;Jayshree Venkatesan, Senior Vice President and Head of Partnership Development&lt;/a&gt; at &lt;a href="https://www.accion.org/" rel="noopener noreferrer"&gt;Accion&lt;/a&gt; and met &lt;a href="https://www.unopensource.org/speaker/andrea-duarte" rel="noopener noreferrer"&gt;Andrea Duarte&lt;/a&gt;, Advisor, Payment Systems Department, &lt;a href="https://www.banrep.gov.co/es" rel="noopener noreferrer"&gt;Central Bank of Colombia&lt;/a&gt;. We spoke about the work the Interledger Foundation is supporting in Colombia around digital payments, inclusion, and how open technologies can better support national priorities.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Lunch with the &lt;a href="https://www.digitalpublicgoods.net/" rel="noopener noreferrer"&gt;Digital Public Goods Alliance (DPGA)&lt;/a&gt; community&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For more than a year, the Interledger Foundation team has been speaking with the &lt;a href="https://www.digitalpublicgoods.net/" rel="noopener noreferrer"&gt;DPGA&lt;/a&gt; community about how Rafiki, our open-source payment software, could contribute to digital public goods. Lunch gave us a chance to continue those conversations in person.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Open Source Program Offices (OSPOs) for Good&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Governments, UN agencies and universities discussed how open source program offices could help them organise their open source work. It was good to hear conversations about contributing to projects and supporting their upkeep.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Community is the constant&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;My favourite part of the week was Friday’s community sessions, organised by RISE, OpenForum Europe, CURIOSS, and Red Hat at the IBM office. &lt;a href="https://newsroom.ibm.com/2026-06-25-ibm-debuts-worlds-first-sub-1-nanometer-chip-technology" rel="noopener noreferrer"&gt;IBM had announced its new chip technology&lt;/a&gt; just the day before. I found that fascinating.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mifos.org/blog/portfolio-item/edward-cable/" rel="noopener noreferrer"&gt;Ed Cable&lt;/a&gt;, CEO of &lt;a href="https://mifos.org/" rel="noopener noreferrer"&gt;Mifos Initiative&lt;/a&gt;, joined a session on how countries can build public digital systems that they can control and that work with other systems. The discussion covered how institutions choose technology and how communities contribute to it. These decisions affect whether local teams can adapt and maintain the systems they use.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://community.interledger.org/remoteimages/uploads/articles/39z7sus75nsxb97e0wc4.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://community.interledger.org/remoteimages/uploads/articles/39z7sus75nsxb97e0wc4.jpg" alt=" " width="4000" height="2252"&gt;&lt;/a&gt;&lt;br&gt;
Ed Cable, CEO of Mifos Initiative&lt;/p&gt;

&lt;p&gt;Friday’s sessions reminded me of the unconference events I attended years ago, where people discussed their work openly and learned from each other. That is what drew me to the community in the first place.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What this means for Interledger Foundation&lt;/strong&gt;&lt;br&gt;
At Interledger, we support open standards like Open Payments, open source projects such as Rafiki, and community-led initiatives around the world. The conversations during the week were closely connected to this work, including our discussions about payments in Colombia and Rafiki with the DPGA community.&lt;/p&gt;

&lt;p&gt;I think we need to keep asking how the communities we support are involved in decisions about the work. What are we learning from them, and how does that influence the support we provide?&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>un</category>
      <category>unitednations</category>
      <category>newyork</category>
    </item>
    <item>
      <title>Alabama A&amp;M: Shaping the Future of FinTech</title>
      <dc:creator>Jha'Mhyrin Johnson</dc:creator>
      <pubDate>Mon, 07 Sep 2026 00:48:08 +0000</pubDate>
      <link>https://community.interledger.org/jhamhyrinjohnso_513/shaping-the-future-of-fintech-3omd</link>
      <guid>https://community.interledger.org/jhamhyrinjohnso_513/shaping-the-future-of-fintech-3omd</guid>
      <description>&lt;p&gt;Selected for the &lt;strong&gt;Dollarcraft Program&lt;/strong&gt;, our initial cohort of 12 business scholars has entered an intensive 12-week interdisciplinary incubator. We are spending these early weeks bridging business strategy and the mechanics of the Interledger Protocol (ILP). In Week 3, four computer science and engineering students will join our group, merging technical execution with strategic design to build functional prototypes to be presented at our final hackathon.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://community.interledger.org/remoteimages/uploads/articles/lufreypiaar5x3fuaplk.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://community.interledger.org/remoteimages/uploads/articles/lufreypiaar5x3fuaplk.JPG" alt=" " width="360" height="640"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Weeks 1 &amp;amp; 2: From Core Concepts to Methodical Research. Entering the program, open payment rails were uncharted territory for most of our cohort. The trajectory shifted quickly when we hosted &lt;strong&gt;Bibi Souza&lt;/strong&gt;, Interledger’s Community Lead. Bibi delivered a masterclass on ILP’s architecture, demystifying cross-network settlement and grounding us in Interledger's broader mission of universal financial access. Her session transformed abstract payment theory into a clear operational roadmap for our group.&lt;/p&gt;

&lt;p&gt;Building on that momentum, Week 2 pushed us deep into discovery. Before writing code or finalizing product specs, we focused on rigorous data collection models. We established quantitative and qualitative research tools—mapping methodologies for user surveys, structured one-on-one interviews, focus groups, and observational field tests. Grounding our decision-making in empirical user data ensures that the financial solutions we build address genuine, documented friction points.&lt;/p&gt;

&lt;p&gt;Moving forward, the energy across these first two weeks has set a high standard for what is to come. &lt;strong&gt;As our engineering teammates join us next week&lt;/strong&gt;, we transition from strategic research to full-stack execution. The opportunity to build on open payment standards isn't just an academic exercise; it's a chance to influence how value moves across communities for years to come. We are heading into Week 3 focused, prepared, and ready to build tools that reflect the true potential of this technology.&lt;/p&gt;

&lt;p&gt;Coauthor: Jayveun Williams&lt;/p&gt;

</description>
      <category>interledgerfoundation</category>
    </item>
    <item>
      <title>Open Payments Curriculum: Empowering a New Generation of Fintech Entrepreneurs — ILF Grant Progress Report</title>
      <dc:creator>Jonathan Oluranti</dc:creator>
      <pubDate>Mon, 31 Aug 2026 19:17:00 +0000</pubDate>
      <link>https://community.interledger.org/covnenantuni/open-payments-curriculum-empowering-a-new-generation-of-fintech-entrepreneurs-ilf-grant-progress-4dh9</link>
      <guid>https://community.interledger.org/covnenantuni/open-payments-curriculum-empowering-a-new-generation-of-fintech-entrepreneurs-ilf-grant-progress-4dh9</guid>
      <description>&lt;h2&gt;
  
  
  Brief Project Description
&lt;/h2&gt;

&lt;p&gt;The Interledger Foundation NextGen Program at Covenant University is an innovative educational initiative designed to equip students with the knowledge, skills, and practical experience needed to build the next generation of inclusive digital financial systems. It aims to achieve this by integrating Interledger Protocol (ILP), Web Monetization, and open payments technologies into computing and business programs.&lt;/p&gt;

&lt;p&gt;The initiative introduces two new courses covering open payments, financial interoperability, fintech innovation, and entrepreneurship, supported by teaching and practical sessions as well as capstone projects. Students will gain hands-on experience by developing ILP-based applications, fintech prototypes, and interoperable payment solutions. Experiential learning activities include innovation bootcamps, hackathons, developer workshops, mentorship programs, and expert-led webinars.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://community.interledger.org/remoteimages/uploads/articles/p9rg01iepyi7k3t3tk6u.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://community.interledger.org/remoteimages/uploads/articles/p9rg01iepyi7k3t3tk6u.jpg" alt="Team Picture" width="2048" height="1057"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The project aligns with the Interledger Foundation’s mission of advancing open, interoperable financial systems and promoting digital inclusion across Africa. Ultimately, it seeks to nurture a new generation of fintech entrepreneurs capable of driving financial innovation and expanding adoption of open payment technologies.&lt;/p&gt;

&lt;h2&gt;
  
  
  Project Update
&lt;/h2&gt;

&lt;p&gt;The Interledger NextGen program at Covenant University has made significant progress since its commencement in March, 2026.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Curriculum Design, Development and Launch of Two Dedicated Open Payments Courses&lt;/strong&gt;&lt;br&gt;
We successfully designed, developed and launched two university-level Open Payments courses focusing on Open Payments, the Interledger Protocol (ILP), Web Monetization, and Financial Inclusion. The curriculum comprises four modules and sixty learning units, which we plan to integrate into Computing and Business programs. The period under review (March – August) has witnessed the focused application of the developed curriculum for hands-on training in open-payment technologies thereby preparing students for careers in open-source fintech, interoperable payment design, and digital financial inclusion.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Student Engagement and Capacity Building&lt;/strong&gt;&lt;br&gt;
As regards students’ engagement and capacity building, we initially had about 253 students who indicated interest to participate in the program when the first advert went out. However, 35 students from Computer Science, Information Systems, Accounting, Economics, and Entrepreneurship programs eventually made it and are actively participating in all aspects of the training.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://community.interledger.org/remoteimages/uploads/articles/zqfq6vzv2wduxkbqv9yg.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://community.interledger.org/remoteimages/uploads/articles/zqfq6vzv2wduxkbqv9yg.jpg" alt="A session on Open Payments &amp;amp; Web Monetization" width="4096" height="1838"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The interest shown by the students actually exceeded expectations which lead to the formation of interdisciplinary innovation teams focused on solving local financial inclusion challenges.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Open Payment Innovation Week and Demo Day Event&lt;/strong&gt;&lt;br&gt;
Some major activities held within the period under review were the Open Payments Innovation Week and Demo. The open payments innovation week was dedicated entirely to problem solving, building and prototyping. Students were divided into in teams to build payment solutions utilizing the Interledger Protocol and Rafiki. The demo day presented opportunity for the students to present as well as pitch their ideas following the week-long training them. We had judges from the industry while Bibi represented Interledger team. The feedbacks received were quite instructive and have helped the teams to improve on their initial idea. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Activation of Micro Grants for Student-Driven ILP Projects&lt;/strong&gt;&lt;br&gt;
In late July, we activated the micro grants to provide financial support to the six teams who pitched their project ideas on the demo day in order to achieve student driven ILPL projects. We are glad to report that five of the teams have completed functional prototypes of their solutions using the ILP and have deployed them accordingly. The next phase will be the real-life demonstration of these solutions with actual intended users. Here are the links to the prototypes:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://paylance-gmc1.onrender.com/" rel="noopener noreferrer"&gt;https://paylance-gmc1.onrender.com/&lt;/a&gt;&lt;br&gt;
&lt;a href="https://payzati.vercel.app/" rel="noopener noreferrer"&gt;https://payzati.vercel.app/&lt;/a&gt;&lt;br&gt;
&lt;a href="http://seamlyy.vercel.app" rel="noopener noreferrer"&gt;http://seamlyy.vercel.app&lt;/a&gt;&lt;br&gt;
&lt;a href="https://rheodemymvp.vercel.app/" rel="noopener noreferrer"&gt;https://rheodemymvp.vercel.app/&lt;/a&gt;&lt;br&gt;
&lt;a href="https://nexafund.vercel.app/" rel="noopener noreferrer"&gt;https://nexafund.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Our website for the entire program is nearing completion and will accommodate the complete course material, video recordings of various sessions and presentation slides.  &lt;/p&gt;

&lt;h2&gt;
  
  
  Project Impact &amp;amp; Target Audience(s)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Objective i: Design, Launch and Institutionalize an Interdisciplinary Open Payments Curriculum&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Significant progress has been made toward the development and institutionalization of the Open Payments Curriculum. Curriculum design activities were completed through consultations with faculty members from Computer Science, Information Systems, Finance, and Entrepreneurship disciplines. Two interdisciplinary course modules—Foundations of Open Payments and Financial Interoperability and Fintech Innovation and Open Payment Entrepreneurship—were developed and aligned with Covenant University's academic standards.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Objective ii: Technical Capacity &amp;amp; Infrastructure Development for 35 Participants&lt;/strong&gt;&lt;br&gt;
We recruited students and developers to participate the in the technical capacity-building activities that successfully commenced early April. A total of 35 participants were selected through a competitive application process. Foundational training sessions have been delivered, providing students with practical exposure to Open Payments technologies and the Interledger ecosystem.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Objective iii: Establish a Certification Program on Open Payments with at Least 80% Participant Completion Rate&lt;/strong&gt;&lt;br&gt;
The certification framework has been developed and integrated into the training program. Assessment instruments and competency evaluation criteria have been established to measure participant understanding and practical skills. Participants are progressing through the certification pathway, with completion rates currently tracking toward the targeted 80% benchmark.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Objective iv: Produce Five Pilot Projects&lt;/strong&gt;&lt;br&gt;
We successfully divided the students into seven (7) teams that comprised of a mix of science, engineering and business students. The teams have since commenced the ideation and development of pilot projects addressing real-world payment interoperability and digital inclusion challenges. At least four of the seven teams have completed their projects and deployed them. The other teams are not relenting also.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Objective v: Publish Open Educational Resources (OERs) and Policy Briefs&lt;/strong&gt;&lt;br&gt;
Development of openly accessible educational resources is underway. Initial teaching materials, practical guides, and workshop contents are being compiled for publication. Research work has also begun on policy briefs that highlight the role of interoperable payment systems in advancing digital inclusion and fintech innovation in Nigeria and Africa.&lt;/p&gt;

&lt;h2&gt;
  
  
  Communications and Marketing
&lt;/h2&gt;

&lt;p&gt;Since the launch of the Interledger Next Gen Program at Covenant University, we have actively shared project activities, milestones, and learning outcomes through multiple public channels to increase awareness of Open Payments, the Interledger Protocol (ILP), and fintech innovation among students, educators, and the broader technology community. Our public engagement efforts have included:&lt;/p&gt;

&lt;p&gt;• Publication of project updates and announcements through Covenant University communication channels and social media platforms.&lt;br&gt;
• Presentations and information sessions introducing the Interledger ecosystem, Open Payments, Web Monetization, and financial interoperability concepts to students and community innovators.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Use of Marketing and Outreach Funds&lt;/strong&gt;&lt;br&gt;
In respect of the marketing funds included in the project budget, they were utilized to support participant recruitment exercise, awareness creation, and community engagement activities. Expenditures included:&lt;br&gt;
• Design and production of digital promotional materials (flyers, banners, social media graphics, and event announcements).&lt;br&gt;
• Event branding materials used during training sessions and outreach activities.&lt;br&gt;
• Documentation and dissemination of project outcomes through digital media channels.&lt;br&gt;
• Production of communication materials highlighting participant achievements and project impact. Here is the link to most recent one carried out:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://1drv.ms/v/c/21d49bd80eaff14c/IQAYYxBNTe_zQLQBeOuTXSv3AUiMEhVndRC5VR9T4Jhw368?e=OSOqUj" rel="noopener noreferrer"&gt;https://1drv.ms/v/c/21d49bd80eaff14c/IQAYYxBNTe_zQLQBeOuTXSv3AUiMEhVndRC5VR9T4Jhw368?e=OSOqUj&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;These outreach efforts have contributed to increased visibility of the Interledger ecosystem within the university community, expanded participation in project activities, and strengthened awareness of Open Payments technologies among students, educators, and aspiring fintech entrepreneurs.&lt;/p&gt;

&lt;h2&gt;
  
  
  What’s Next?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Hackathons and Student Innovation&lt;/strong&gt;&lt;br&gt;
In next half of this project, we plan hosting a campus-wide Open Payments Hackathon that will attract more than 20 student teams. The Hackathon will cover the following solutions:&lt;br&gt;
• Cross-border student payment systems.&lt;br&gt;
• Scholarship and bursary disbursement platforms.&lt;br&gt;
• Digital marketplaces leveraging Web Monetization.&lt;br&gt;
• Micro-savings solutions for underserved communities.&lt;/p&gt;

&lt;p&gt;We will ensure that successful projects advance to the incubation stage for further development towards making them market ready fintech startups.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;First ever Open Payments Conference in Nigeria&lt;/strong&gt;&lt;br&gt;
In November this year, we plan hosting an Open Payments Conference, the first ever in Nigeria and possibly West Africa. This will bring together thought leaders, students, researchers, fintech professionals, and policymakers to discuss the future of open and inclusive financial systems.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Improved Public Dissemination and Community Engagement&lt;/strong&gt;&lt;br&gt;
We plan to improve on our public dissemination and community engagement activities by actively sharing project activities, milestones, and learning outcomes through multiple public channels to increase awareness of Open Payments, the Interledger Protocol (ILP), and fintech innovation among students, educators, and the broader technology community.&lt;br&gt;
 &lt;br&gt;
&lt;strong&gt;Our public engagement plans include:&lt;/strong&gt;&lt;br&gt;
• Publication of project updates and announcements through Covenant University communication channels and social media platforms.&lt;br&gt;
• Presentations and information sessions introducing the Interledger ecosystem, Open Payments, Web Monetization, and financial interoperability concepts to students and community innovators.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Finalize the development of Openly Accessible Educational Resource&lt;/strong&gt;&lt;br&gt;
We also plan to finalize the development of openly accessible educational resources. We shall conclude the compilation of all teaching materials, practical guides, and workshop contents for publication. We also endeavor to conclude the ongoing research work on policy briefs that highlight the role of interoperable payment systems in advancing digital inclusion and fintech innovation in Nigeria and Africa.&lt;/p&gt;

&lt;h2&gt;
  
  
  Community Support
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Public Relations Rollout across Nigeria, Africa and Global Media Channels&lt;/strong&gt;&lt;br&gt;
We aim to execute a strategic public relations campaign targeting top-tier media outlets across Nigeria and Africa. This will involve distributing tailored press releases, securing feature stories, and arranging interviews with key digital, and broadcast networks where necessary. We desire all forms of support from the ILF Marketing team in terms of deciding on the timeline and PR messaging. We are looking forward to ILF support by way of introduction to PR expert in South Africa.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Covenant University Next Gen Hackathon&lt;/strong&gt;&lt;br&gt;
During this Hackathon week by second week of November, we would be having technical and product office hour sessions to support students and the wider builder's community on campus to integrate Open Payments and Web Monetization. We would great appreciate the involvement of the engineering executive from the ILF. We desire 2 or 3 judges from the ILF team or community to evaluate our students’ projects&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Open Payments Conference and Hackathon Finale&lt;/strong&gt;&lt;br&gt;
The Open Payments Conference combines a high impact tech conference with the thrilling conclusion of the Covenant University Next Gen Hackathon. Industry leaders, developers, and Next Gen students will gather for expert keynotes and deep dives into Open Payments, financial inclusion and financial interoperability.&lt;/p&gt;

&lt;p&gt;The conference culminates in the hackathon finale, where top teams will pitch their innovative open payment solutions to a panel of judges. We would be glad to have 2 or 3 speakers from Interledger Foundation for Keynote and Spotlight Sessions in the Conference.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Open Payments Conference (Marketing and Branding)&lt;/strong&gt;&lt;br&gt;
We would like to have the support of the ILF teams with respect to the Marketing and Branding aspects of our forthcoming Open payments conference in November. We would like to sync appropriately with the Marketing team from ILF on Marketing efforts for the Open Payments Conference. This will include:&lt;br&gt;
• Design and Branding of Conference Materials (Stickers, Merch, Swag items)&lt;br&gt;
• Marketing support, timeline and alignment with the ILF Marketing team&lt;br&gt;
 &lt;br&gt;
&lt;strong&gt;Community Share-out Sessions&lt;/strong&gt;&lt;br&gt;
We also require the support of ILF team for a 5 - 10 minutes monthly slot starting from September on the Interledger Community Call for our students to conduct live product demonstrations to the Interledger Community, highlighting their product innovation and technical progress. This will serve as a platform for students to engage with industry experts, exchange ideas, and receive valuable, constructive feedback to further refine and advance their projects.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Final Public Demo Day&lt;/strong&gt;&lt;br&gt;
The Public Demo Day is a capstone event that marks the culmination of the Inaugural Covenant University Next Gen program, where participating students will showcase their completed open payments projects and innovative solutions to a wider audience especially industry experts, peers and the public. We desire at least two persons from the ILF team for this great event.&lt;/p&gt;

&lt;h2&gt;
  
  
  Additional Comments
&lt;/h2&gt;

&lt;h2&gt;
  
  
  Relevant Links/Resources  (optional)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://1drv.ms/v/c/21d49bd80eaff14c/IQAYYxBNTe_zQLQBeOuTXSv3AUiMEhVndRC5VR9T4Jhw368?e=OSOqUj" rel="noopener noreferrer"&gt;https://1drv.ms/v/c/21d49bd80eaff14c/IQAYYxBNTe_zQLQBeOuTXSv3AUiMEhVndRC5VR9T4Jhw368?e=OSOqUj&lt;/a&gt;&lt;/p&gt;

</description>
      <category>progressreports</category>
    </item>
  </channel>
</rss>
