High-level architecture guidance for a multi-country wallet

Hi,

We are a Colombian team building a multi-country shared investment tool (including savings) that is fed majorly through remittances, retail buying roundups and contributions.

Our objective is that the resources of the shared accounts are used in a bidirectional way: for example, students abroad helped by their families and friends and in the other way remittances added to multi-country and local roundups and contributions for payments, essential goods and others.

We are super excited because we think this would be a huge step forward for our region (majorly unbanked) and because we consider Interledger as the perfect fit and the community awesome.

Through the documentation and forum, we have defined a high-level architecture that we included below, can you please point us in the right direction If our assumptions are accurate (or at least makes any sense) and the things that we are missing or misunderstanding. Thank you very much.

Diagram’s additional context:
• We consider we should host a connector because we think there is not an effective (FX cost and time) path for inter Latam payments /transfers.
• We are using XRP as an exchange tool given that, as in fiat market, we assume will be difficult to have efficient offers between Latam currencies (TRM of Latam currencies is based on USD).
• We are using the Hyperledger Java Connector implementation, but it has a beta disclaimer. Do you know if we still can use it and fix / duscuss the beta elements with the team?
Disclaimer: even though we have engineers aboard we are not expert developers. Our engineers have been in the banking sector until now.

Good morning,
Can you develop an small crypto exchange based on interledger xrp? How much will that cost.

Hi,
I’m not sure I fully understood you. Do you mean if we can develop it for a third party?

This looks like a good architecture for your use case.

@sappenin is the right person to speak to regarding the Java connector implementation.

Thank you very much Adrian. Great to hear this feedback.

We are using the Hyperledger Java Connector implementation, but it has a beta disclaimer. Do you know if we still can use it and fix / duscuss the beta elements with the team?

Hi @JorgeGuiarTree - thanks for posting about your project, it looks very interesting.

We’re currently working on a roadmap for the Java Connector (I’m hoping to have more completed this week - the roadmap will be here). In the meantime, if you know of some features you’d like to see in the Java Connector, feel free to suggest them here.

Thank you very much @sappenin! These are great news. We will be following the roadmap and will include features as we identify them.