I would like some help with the Contribution.MD file, I am not sure how to write a contribution guideline.

I will be grateful if you can help me with this.

I need help implementing examples of the API client in the /example folder.

As I build the API client and write tests; it will be nice to have examples of logic that can be done with the crate.

Some examples off the top of my head:

• A CLI app to create a transaction in your Paystack integration, the app can return the payment link generated, and you can also check the status of the transaction on the CLI using the transaction reference.
• A CLI to give the number of transactions in your integration, it can further group the transactions based on status or any other criteria you like.

These are just examples, feel free to be creative with your examples. The goal is to show what can be built with the crate.

If you create an example, please name the file after your example, this will make it intuitive for other users. It will also be nice if you comment on the code.

This is a non-ending issue, so it is opened to as many contributors as possible.

The goal is to write a series of these for the transaction splits endpoint.

The goal is to write tests to check that the proper behavior happens when the right data is sent to the endpoint and when the wrong data is sent to the endpoint.

An endpoint to send an event from your application to the Paystack Terminal

At the moment, the test in the test/api/charge.rs file has hard-coded values. These values are directly retired from my Paystack integration. This is not an ideal solution because if someone uses their own API key, the tests will fail.

To fix this issue, you would need to figure out a way to retrieve those values from the integration so that they will not be hard coded.

If you are interested in fixing this, please indicate and take a short at it.

The HTTP client agnostic crate allows the user to have flexibility in their application. The user can use their own HTTP client as long as it implements the crate's base HTTP trait.

To make this as convenient as possible, I propose an implementation of the reqwest client as the default, and then other clients can be added as the project continues.

The goal of this issue is to focus on the first two items, namely:

• create the base HTTP trait
• implement the reqwest HTTP client for the crate

This issue revolves around implementing the complete Paystack customer API for the crate. Some API parts have already been implemented, mostly the data model. This will ensure that this new customer API route does not conflict with the existing one.