Harmonizing API Specifications Between G2P-Connect and GovStack

[SobanNajam]

Hello everyone,

I'm looking to initiate a discussion on the harmonization of API specifications between two projects. The aim is to ensure smooth interoperability and enhance the efficacy of our implementations.

Our objectives are:

• Cater to situations where the "Source BB" or something similar to Scheme Management/Social Benefits Program Management is implemented in alignment with G2P-Connect Specifications.
• Ensure that this can interoperate seamlessly with the Payment Building Block from the GovStack specifications for processing payments or conducting disbursements.

This harmonization will not only standardize our approach but also help in catering to a wider array of use cases effectively.

Would love to hear your thoughts, suggestions, and potential challenges you foresee with this integration. Your insights will be invaluable in ensuring that the harmonization effort is both smooth and effective.

Thank you in advance for your input!
[
G2PConnect GovStack Harmonize 1.0.pptx.pdf
](url)

[pramodkvarma]

Thanks. Glad to see this harmonization effort. @vvujjini can help with details and I am happy to review once the teams are aligned.

[dasunhegoda]

Hello everyone,

This message is intended to bring forward certain aspects that require clarity and potential refinement (if applicable),

1. It is suggested that the wrapper layer be moved within the Payment Building Block. This reorganization is anticipated to achieve high cohesion and simplified maintainability.

2. Implementing an Adapter pattern might be more fitting than a Wrapper when resolving interface incompatibilities. The Adapter pattern is recognized for its efficacy in mitigating compatibility issues, whereas the Wrapper is commonly employed for extending functionalities.

3. About the interim database, clarification is sought on whether any other data are stored beyond the standard parameters mentioned (e.g., scheduled_timestamp, payer_name, payee_name, note, instruction, locale). Also, data governance for these parameters has to be taken into consideration.

4. In GovStack, a beneficiary's payment modality is determined during registration, while in G2P-Connect, this association is made per disbursement. In situations with multiple programs operating simultaneously, the necessity arises for a facility that enables beneficiaries to dictate their preferred payment modality (such as Mobile Money, Account, etc.). How might we go about introducing this mapping?

Insights and recommendations on these points would be highly valued.

[DavidH-1]

Hi all,

Thanks for the discussion so far. To continue the discussion and also have Soban walk through some of these slides we will schedule a call this Friday. 11:30-12:30 (Central European Time). We welcome anyone to join. The details are below. If you are unable to join we will record the call too so you can hear the discussion.

Kind Regards

David.
──────────
Mifos is inviting you to a scheduled Zoom meeting.

Join Zoom Meeting
https://us02web.zoom.us/j/83522875234

Meeting ID: 835 2287 5234

---

One tap mobile
+13017158592,,83522875234# US (Washington DC)
+13052241968,,83522875234# US

---

Dial by your location
• +1 301 715 8592 US (Washington DC)
• +1 305 224 1968 US
• +1 309 205 3325 US
• +1 312 626 6799 US (Chicago)
• +1 346 248 7799 US (Houston)
• +1 360 209 5623 US
• +1 386 347 5053 US
• +1 507 473 4847 US
• +1 564 217 2000 US
• +1 646 931 3860 US
• +1 669 444 9171 US
• +1 669 900 6833 US (San Jose)
• +1 689 278 1000 US
• +1 719 359 4580 US
• +1 929 205 6099 US (New York)
• +1 253 205 0468 US
• +1 253 215 8782 US (Tacoma)

Meeting ID: 835 2287 5234

Find your local number:https://us02web.zoom.us/u/kc8J6wndPT

──────────

[DavidH-1]

Thanks everyone for your time today on the call it was very productive and has given us some more bits to follow up on in the discussion thread over the next few weeks.

As promised here are the recordings of the call in case you couldn't attend we still welcome any feedback you may have.

Video. Audio.

[vvujjini]

@DavidH-1 @SobanNajam @Avik One possibility is for Mifos implementation to skip supporting synchronous endpoints. The g2p connect/dci specs list sync end points for those systems where additional time is required to migrate from sync to async over time.

Looking forward to hear from @Avik and Mifos team with points discussed during the last few calls on some of the design points and any integration use case to test this any of the available sandboxes.

[DavidH-1]

Please find attached a whitepaper @SobanNajam has created based on the inputs so far that extends what we previously presented into the design approach . We would welcome any comments from the community.
G2PConnect GovStack Harmonization White Paper 1_0.pdf