#votsircp-payment-methods
1 messages · Page 1 of 1 (latest)
From business point of view, it is a great idea to enable as many payment methods as possible to increase the conversions. you customer will be more likely to pay if you offer them more payment options like apple pay google pay, bank transfer, wallet etc.
regarding the complexity
on technical integrations, it really depends on how you integrate with Stripe, if you are using Checkout, it might be one line of code change https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_method_types
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
even if you are integrating with Stripe element, it will not be that terrible as the code path will be more or less the same using PaymentIntent etc.
right now we're using Stripe element
In that case, the server side change
- accept more payment_method types by modifying https://stripe.com/docs/api/payment_intents/create#create_payment_intent-payment_method_types
- The frontend might need a bit of work of rendering the UI, but depends on the payment methods that are available, you can
(1) create new element types https://stripe.com/docs/js/elements_object/create_element?type=card#elements_create-type
(2) mount to a new dom element
(3) calling their respective confirmation call https://stripe.com/docs/js/payment_intents/payment_method
Complete reference documentation for the Stripe JavaScript SDK.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Complete reference documentation for the Stripe JavaScript SDK.
np
ah, we're not using payment intents
we use stripe.charges.create for single payments and stripe.subscriptions.create for recurring
I see, you are using the legacy charge API which will be difficult as quite a number of payment_methods support Payment_Intent and Payment_method API only
and you cannot use payment_method with charge APi
you might need to upgrade it to use PaymentIntent instead
nowhere did i see that these were legacy functions
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
You can take a look at this https://stripe.com/docs/payments/payment-intents/migration
if we were to use Checkout, could we have two different Checkout? one for one time payments and another one for subscriptions? i know some payment methods do not support subscriptions