Skip to content

Add Submission for Multi-currency wallet transfer API (dmystical-coder)#18

Open
dmystical-coder wants to merge 3 commits intoWriteTech-Hub:mainfrom
dmystical-coder:multi_currency_wallet_transfer-dmystical-coder
Open

Add Submission for Multi-currency wallet transfer API (dmystical-coder)#18
dmystical-coder wants to merge 3 commits intoWriteTech-Hub:mainfrom
dmystical-coder:multi_currency_wallet_transfer-dmystical-coder

Conversation

@dmystical-coder
Copy link

This PR adds a comprehensive setup guide, tutorial guide and use case article. The article details how Chimoney’s multicurrency wallet transfer API addresses the challenges of paying international contractors, using a real-world scenario (TechFlow Solutions).

@phyleria, @adebayoileri

@dmystical-coder dmystical-coder requested a review from a team as a code owner July 31, 2025 21:07
@phyleria
Copy link
Collaborator

Hi @dmystical-coder,

Thank you for your submission! Everything looks good 🙌🏾

Copy link
Contributor

@Teebarh Teebarh left a comment

Choose a reason for hiding this comment

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

Hi @dmystical-coder, thank you so much for working on this! The structure and formatting of your tutorial are nice, but I have a few suggestions to help improve it.

The tutorial feels a bit rushed in some parts. Some steps are just listed without enough explanation, which makes it harder to follow. You should work on these:

  • Add short, clear explanations before or after each step so readers know why they are doing something, not just what to do.
  • Make the transition between steps smoother by briefly connecting what was done in the previous step to what’s coming next.
  • Explain any terms a beginner might not know, or link to helpful resources.
  • Read through your tutorial as if you were new to the topic and see where more detail is needed.

Let me know if you have any questions!

Copy link

@OfficialJhimmy OfficialJhimmy left a comment

Choose a reason for hiding this comment

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

Hi @dmystical-coder, thanks a lot for working on this guide! You’ve done a great job laying out the prerequisites, setup steps, and even including troubleshooting tips at the end; that’s a very helpful touch. I also like that you showed both the request code and an example of a success response, which gives readers a clear picture of what to expect. That said, there are a few areas where you can improve to make this guide much easier to follow, especially for beginners:

  1. Structure and Flow
    • The steps are clear, but the transitions between them feel a little abrupt. For example, after authentication, you jump straight into environment setup without tying it back to why authentication matters. A short explanation like, “Now that you have your API key, let’s set up your project so you can use it in requests,” would help guide the reader more smoothly.
    • The “What Success Looks Like” section could be shortened to highlight just the key fields. Right now, the huge JSON response can overwhelm readers. Instead, you could show a trimmed-down version and explain the important parts (like rate, amount, and currencies).

  2. Clarity and Explanations
    • Some instructions assume the reader knows what’s happening. For example, when you introduce .env, it would help to briefly explain why environment variables are used (to avoid hardcoding sensitive information).
    • In the API call section, you could explain what each field in the request body means (like originCurrency, destinationCurrency, and narration). This helps readers understand rather than just copy-paste.

  3. Grammar and Wording
    • Some phrases could be simplified for better readability. For example:
    • “Generate a Sandbox API key from the Chimoney dashboard” could become “Go to the Chimoney dashboard and generate a Sandbox API key.”
    • “To authorize requests, you have to include your API key in the header” could be “You’ll need to add your API key in the request header to authorize calls.”
    • Keeping sentences short and active makes the tutorial more engaging and easier to read.

  4. Writing Best Practices
    • Be consistent with formatting. For example, you sometimes write API-KEY and other times API key. Pick one style and use it throughout.
    • When linking external resources (like the Loom video), give a little context instead of just dropping the link. For example: “If you’re not sure how to generate your key, here’s a short video tutorial.”
    • For the troubleshooting table, it’s good, but you could add one or two more common errors (like network errors or invalid endpoints).

Overall, you’ve got the main structure in place and included a lot of useful details, but the guide could be more beginner-friendly with smoother explanations, trimmed responses, and clearer wording. Think of it like teaching. The goal is not just to show steps, but to make sure the reader understands why they’re doing each one. Keep going, you’re definitely on the right track! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants