Skip to content

Write-A-Thon Challenge: Enhanced Documentation for Chimoney Multi-Currency Wallet Transfer API#7

Open
Brijeshthummar02 wants to merge 1 commit intoWriteTech-Hub:mainfrom
Brijeshthummar02:challenge
Open

Write-A-Thon Challenge: Enhanced Documentation for Chimoney Multi-Currency Wallet Transfer API#7
Brijeshthummar02 wants to merge 1 commit intoWriteTech-Hub:mainfrom
Brijeshthummar02:challenge

Conversation

@Brijeshthummar02
Copy link

Overview

This PR provides comprehensive documentation for Chimoney's Multi-Currency Wallet Transfer API, focusing exclusively on the sandbox environment. The documentation spans three files that guide users from understanding use cases to complete implementation.

API Being Documented

Chimoney's Multi-Currency Wallet Transfer API - A solution that allows developers to build applications that can transfer money between different currencies (USD, CAD, NGN).

Key Features Documented

  • Creating and managing multi-currency wallets
  • Getting real-time exchange rate quotes with transparent fees
  • Executing cross-currency transfers between wallets
  • Sending money to recipients via email or phone number (even without a Chimoney account)
  • Implementing webhooks for real-time transaction notifications
  • Error handling and idempotency for reliable financial transactions

Documentation Structure

1. use-case.md: Real-world business applications and value proposition

2. setup.md: Step-by-step configuration guide

3. tutorial.md: Comprehensive implementation walkthrough

Author:
~ https://github.com/Brijeshthummar02

…fer API

Signed-off-by: Brijeshthummar02 <brijeshthummar02@gmail.com>
@Brijeshthummar02 Brijeshthummar02 requested a review from a team as a code owner July 26, 2025 05:19
@Brijeshthummar02
Copy link
Author

@phyleria good to go?

@phyleria
Copy link
Collaborator

Hi @Brijeshthummar02,

The format looks great. We’ll review it after the submission deadline. Thanks for your submission!

Copy link
Contributor

Choose a reason for hiding this comment

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

Hello, @Brijeshthummar02. Thanks for this tutorial! It’s really informative, but I have a couple of suggestions:

  • Right now, the error handling section only has code blocks with the error and the solution. It would be clearer if you included this information as text before the code block so it's understood easier. Also, you should include the error numbers or codes so readers know exactly which error is which.
  • The random code blocks labelled “developer insights” or "developer journey" don’t add much to the flow of the tutorial. It might be better to remove them.

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 @Brijeshthummar02, thank you for putting this guide together! You did a really good job covering all the key steps for setting up Chimoney’s API, and I like how you included real examples with both Node.js and Python. The “Achievement unlocked” notes and developer insights also make the tutorial more engaging.

That said, I have some suggestions that will help polish it further:

Structure and Flow
• The guide is very detailed, but at times it feels long and heavy to read. You can make it easier to follow by breaking long explanations into shorter sentences or paragraphs.
• Try adding short transition sentences between steps. For example, at the end of Step 3 (Generate API Key), you could briefly remind the reader that they’ll need this key for the next step on authentication. This helps the tutorial feel more connected.

Clarity
• Some terms, like “webhook,” “environment variables,” or “idempotency,” may not be familiar to beginners. A quick definition or link to an external resource would make the tutorial more beginner-friendly.
• In a few places, you mix explanation with storytelling (like the developer insights). This is engaging, but make sure it doesn’t interrupt the flow of instructions. A good way is to keep the instructions clear and concise first, then add the insight as a side note.

Grammar and Style
• A few sentences are a bit long and could be simplified for readability. For example:
“Think of it as creating a solid foundation for your payment architecture – proper organization now will save you countless headaches as your application scales.”
This could be split into two sentences so it’s easier to digest.
• Watch out for small inconsistencies in formatting (like spacing around bullet points and code examples). Consistent formatting helps readers skim and follow along smoothly.

Writing Best Practices
• You did well providing sample code, but consider briefly explaining what each snippet does before or after showing it. For instance, before the curl commands, you could add a line like: “This command will create your wallet and return its details, including the wallet ID you’ll need later.”
• Where you introduce errors and solutions, that’s excellent. You could go one step further by explaining why the error happens in simple words, not just what the fix is. That gives the reader more confidence.

Overall, this is a solid tutorial with clear effort put into it. With a bit more smoothing in the flow, simpler explanations for complex terms, and consistent formatting, it could easily go from good to excellent.

Great job, and thank you for contributing!

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