search

cla-bit / PayStackEase

This is a Paystack API wrapper using Asynchronous and Synchronous request to interact with Paystack endpoints for various financial services.
https://pypi.org/project/paystackease/
MIT License
1 stars 0 forks source link

plan for the project #16

Open Allaye opened 1 month ago

Allaye commented 1 month ago

@cla-bit, thanks for the good, i just want to know what are your plan for the project? as i am currently working on something where i will need to integrate some African Payment platform, i cant really find anythink concrete, most that i have seen are not actively maintain.

Regards.

cla-bit commented 1 month ago

@cla-bit, thanks for the good, i just want to know what are your plan for the project? as i am currently working on something where i will need to integrate some African Payment platform, i cant really find anythink concrete, most that i have seen are not actively maintain.

Regards.

I do appreciate you looking into this project. As for my future plans, well, most of the things in this paystackease library are already implemented: webhooks, event, and various paystack api endpoints (via their documentation), what i would love to do from time to time will be to:

Check here for the documentation: https://paystackease.readthedocs.io/en/latest/index.html

Allaye commented 1 month ago

Oh, okay, nice. I was considering whether you'd be open to integrating other African or local Nigerian payment processors, making it a one-stop shop for these services. This could be a future consideration. However, for the present, I'm thinking of implementing this as a Django app since I have an urgent need for it. What are your thoughts?

On Wed, Jul 31, 2024 at 3:33 PM claver @.***> wrote:

@cla-bit https://github.com/cla-bit, thanks for the good, i just want to know what are your plan for the project? as i am currently working on something where i will need to integrate some African Payment platform, i cant really find anythink concrete, most that i have seen are not actively maintain.

Regards.

I do appreciate you looking into this project. As for my future plans, well, most of the things in this paystackease library are already implemented: webhooks, event, and various paystack api endpoints (via their documentation), what i would love to do from time to time will be to:

  • improve the security around the webhooks, events, restricting only to allowed whitelist iPs.
  • see how to implement either pydantic or dataclasses to give developers hints on what kind of data type can be passed when using any of the endpoints.
  • follow up on Paystack on current events implementation.
  • follow best practices for optimization, and security
  • Improve the documentation to make it easier for developers to understand and use paystackease.

Check here for the documentation: https://paystackease.readthedocs.io/en/latest/index.html

— Reply to this email directly, view it on GitHub https://github.com/cla-bit/PayStackEase/issues/16#issuecomment-2260667936, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEEPRYSMVUO6LW25ZVUGMT3ZPDYSDAVCNFSM6AAAAABLYKTVC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGY3DOOJTGY . You are receiving this because you authored the thread.Message ID: @.***>

cla-bit commented 1 month ago

Oh, okay, nice. I was considering whether you'd be open to integrating other African or local Nigerian payment processors, making it a one-stop shop for these services. This could be a future consideration. However, for the present, I'm thinking of implementing this as a Django app since I have an urgent need for it. What are your thoughts? … On Wed, Jul 31, 2024 at 3:33 PM claver @.> wrote: @cla-bit https://github.com/cla-bit, thanks for the good, i just want to know what are your plan for the project? as i am currently working on something where i will need to integrate some African Payment platform, i cant really find anythink concrete, most that i have seen are not actively maintain. Regards. I do appreciate you looking into this project. As for my future plans, well, most of the things in this paystackease library are already implemented: webhooks, event, and various paystack api endpoints (via their documentation), what i would love to do from time to time will be to: - improve the security around the webhooks, events, restricting only to allowed whitelist iPs. - see how to implement either pydantic or dataclasses to give developers hints on what kind of data type can be passed when using any of the endpoints. - follow up on Paystack on current events implementation. - follow best practices for optimization, and security - Improve the documentation to make it easier for developers to understand and use paystackease. Check here for the documentation: https://paystackease.readthedocs.io/en/latest/index.html — Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEEPRYSMVUO6LW25ZVUGMT3ZPDYSDAVCNFSM6AAAAABLYKTVC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGY3DOOJTGY . You are receiving this because you authored the thread.Message ID: @.>

Yes, i am open for such project.

If i get you right, you want to integrate various Nigerian payment processors(Opay, Moniepoint, PalmPay, Paystack etc) into one for example as an application (web)?

Allaye commented 1 month ago

Yes, let's say PayStackEase will offer similar APIs for Nigerian payment processors such as Opay, Moniepoint, PalmPay, and Paystack, as well as for Mobile Money. This could serve as a standalone library or as a plugin/extension/app for web frameworks like Flask, Django, FastAPI, etc.

cla-bit commented 1 month ago

Yes, but then to integrate all into one as a plugin/library, each gateway(Paystack, Opay etc) needs to have a uniqueness because their authentication, endpoints are different.

For example, paystack uses api secret keys, it's url is different from that of moniepoint.

How do you propose that can be done? @Allaye

Allaye commented 1 month ago

@cla-bit Based on my experience with payment platforms, the majority, if not all, utilize an API secret key flow. Therefore, we can definitely create a single interface for most of them, I suppose, and for those that are different, we will treat them accordingly.

cla-bit commented 1 month ago

Ok... @Allaye