-
Notifications
You must be signed in to change notification settings - Fork 170
Fixed application fee for PaymentIntent #155
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
Fixed application fee for PaymentIntent #155
Conversation
…-application-fee Added support for Connect Application Fees endpoint
Allow configuring `Stripe-Version` at the gateway level
Support for expanding Stripe objects in the response
Adds methods for required settings to do token based payments
Support for card present track data
Support for level 3 data
Hi! According Stripe official documentation and Core Resource section, the Charge object may consist both |
Setup Intent implementation & off_session payments for Payment Intent
* Update Create plan request * Remove BC and add deprecated
Whereas my comment #172 (comment) is not totally true for @gmoreira can you rebase the PR, please? This one should definitely be merged. |
…ub.com/fotomerchant/omnipay-stripe into feature/payment-intent-application-fee * 'feature/payment-intent-application-fee' of https://github.com/fotomerchant/omnipay-stripe: Fixed application fee request parameter when creating a PaymentIntent. # Conflicts: # tests/Message/PaymentIntents/AuthorizeRequestTest.php
As per https://stripe.com/docs/api/payment_intents/create, the request parameter for Payment Intent
application_fee_amount
when specifying the application fee for Stripe Connect scenarios.