#jabza
1 messages Β· Page 1 of 1 (latest)
Currently using Stripe Elements with PaymentElement, and only seeing the 'Card' based payment method. I've enabled various payment methods via the Connect dashboard. (Was expecting Apple & Google pay on phone)
Hi there! You're right, this exact parameter doesn't exist for Subscriptions.
Ahh I see. Hmm, maybe i'm misunderstanding how this should work π€
You can set payment_settings.payment_method_types when creating the Subscription: https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_settings-payment_method_types
Or omit this and update your invoice template settings in the Dashboard: https://dashboard.stripe.com/settings/billing/invoice
So there isn't a way to get the functionality of 'auto payment methods' when dealing with subscriptions?
(This is a Standard Connect based application) if that helps
oh I think Apple Pay isn't showing because I haven't added the domain to the payment method - so I guess i just won't see it in development
The way to do this is to update the invoice template settings in the dashboard and omit payment_settings.payment_method_types when creating the Subscription
customer: customerId,
items: [{
price: req.query.pid
}],
payment_behavior: "default_incomplete",
payment_settings: { save_default_payment_method: "on_subscription" },
expand: ["latest_invoice.payment_intent"]
});```
^ my call - not touching the payment_method_types atm
Ah, yep, that's right. Wallets should automatically appear if the card payment method type is allowed for the invoice
thats good to know
Though, as you mentioned, ApplePay requires the domain to be registered and the customer to access the payment page from Safari and have an ApplePay card configured
Gotchya. So that explains the wallets - but I'm still a bit lost with regards to all the other payment methods I've enabled. Like direct debit - I've checked the invoice page
Would my platform's Connect Standard user's need to do the same steps?
my test Connect Standard account has these payment capabilities, but when checking the PaymentElement I see
Can you share the PaymentIntent ID associated with the PaymentElement screenshot above?
Let me try, one second
pi_3MoF6BQx9KekOZhI07DLyprq
I'm making the subscription via a Stripe object that was created like this:
apiVersion: "2022-11-15",
stripeAccount: req.query.aid
});```
I assume when I am making direct charges like this (via a subscription) - I do not need to set the on_behalf_of flag
Hi @carmine harbor I'm taking over, give me a sec to catch up
Ty @tender ledge
For context - I am making a platform with Connect, using Standard accounts
I want to facilitate subscriptions between End Customers and Connect Standard accounts on this platform
Currently the React PaymentElement is only showing Card method
OK. I guess you are using the custom code integration (https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements) where you pass the invoice's paymentIntent's client_secret to frontend to render your own PaymentElement.
That's right yeah, backend is using Stripe object (with Connect's account Id) to create a Subscriptions, grab the PaymentIntent and sends the client_secret to front end, which is passed to <PaymentElement/>
apiVersion: "2022-11-15",
stripeAccount: req.query.aid
});```
customer: customerId,
items: [{
price: req.query.pid
}],
payment_behavior: "default_incomplete",
payment_settings: { save_default_payment_method: "on_subscription" },
});```
Do i need on_behalf_of - since i already put the Connect account in Stripe constructor? I want Connected Accounts to be merchant of record ect.
No I don't think you need to add this. since you are creating a subscription on the connected account.
Can you share with me the ID of the connected account?
acct_1MnB6oQx9KekOZhI
Good to know. That makes sense π
I think i've setup the payment methods correctly for the connected account
OK, I know the problem
Since you didn't specify the payment_method_types (https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_settings-payment_method_types ) when creating a subscription, Stripe will use the payment methods from your invoice template settings (https://dashboard.stripe.com/settings/billing/invoice)
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
And currently this connected account has only card and wechat pay enabled for invoice template settings.
Ahhh - so the Connected Account's invoice setting - not the platforms?
I seem unable to modify the Invoice settings for Connect Account when logged in
as them
- ah that's only from the Preview. Logging in directly has worked π
I'm getting warnings about charges to enable these methods (depsite being in Test mode) - for instance Β£50 per month for BACS method
Am i right to assume I can enable this method in test mode without charge?
What kind of warning? can you take a screenshot?
want to enable 'BACS' - Not seeing that payment method in the PaymentElement π€
It looks like an upgrade option for me. Anyway you won't be charged for transactions in test mode.
Hmm
Seems like to enable Bank Transfer for Subscriptions i should go for the method of supplying the payment_settings.payment_method_types?
From the screenshot it looks like these payment methods are not yet activated.