-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[API Design][No Orders API] Review from a first test #4
Comments
Also using callbacks does not allow you to enforce function signatures in the on method either. |
@raveesh-me We'll be adding support for Orders API soon. |
@raveesh-me We've added support for Orders in v1.1.0-alpha. |
Thank you, will check out in the next project. |
@raveesh-me Did you get a chance to try it out? |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! I reviewed the plugin live, as I was trying to implement a client project,
Here are my key findings:
-> PaymentSuccessResponse has only payment_id, not the best way to deal with this
I have archived the video, but if interested can make it available.
At the same time, am open to discuss a better API surface.
Bests,
Raveesh.
The text was updated successfully, but these errors were encountered: