-
Notifications
You must be signed in to change notification settings - Fork 663
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
Move PaymentSheet example to /checkout endpoint. #3633
Conversation
example/src/main/java/com/stripe/example/activity/BasePaymentSheetActivity.kt
Show resolved
Hide resolved
cc678d7
to
3418587
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will wait until example backend implements a /checkout
endpoint like the Glitch example, so the example app uses a single backend.
example/src/main/java/com/stripe/example/activity/BasePaymentSheetActivity.kt
Show resolved
Hide resolved
/checkout
endpoint.
/checkout
endpoint.
example/src/main/java/com/stripe/example/activity/BasePaymentSheetActivity.kt
Show resolved
Hide resolved
Let's just add a second property for the moment until we decide how/if we want to split the example app. This will allow us to close out this PR, start moving off of heroku, and take advantage of returning/new customers - woohoo! |
This is not great, but it's the simplest way if we want to merge this. We should refactor ASAP. |
Merging this into |
Summary
Use
/checkout
endpoint for PaymentSheet example, as implemented in Glitch example.Motivation
Simpler integration, use same endpoint as iOS.
Testing