#jabza

1 messages Β· Page 1 of 1 (latest)

wintry thornBOT
carmine harbor
#

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)

glass furnace
#

Hi there! You're right, this exact parameter doesn't exist for Subscriptions.

carmine harbor
#

Ahh I see. Hmm, maybe i'm misunderstanding how this should work πŸ€”

glass furnace
carmine harbor
#

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

glass furnace
#

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

carmine harbor
#
            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

glass furnace
#

Ah, yep, that's right. Wallets should automatically appear if the card payment method type is allowed for the invoice

carmine harbor
#

thats good to know

glass furnace
#

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

carmine harbor
#

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

glass furnace
#

Can you share the PaymentIntent ID associated with the PaymentElement screenshot above?

wintry thornBOT
carmine harbor
#

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

tender ledge
#

Hi @carmine harbor I'm taking over, give me a sec to catch up

carmine harbor
#

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

tender ledge
carmine harbor
#

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.

tender ledge
#

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?

carmine harbor
carmine harbor
#

I think i've setup the payment methods correctly for the connected account

tender ledge
#

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)

#

And currently this connected account has only card and wechat pay enabled for invoice template settings.

carmine harbor
#

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?

tender ledge
#

What kind of warning? can you take a screenshot?

carmine harbor
#

want to enable 'BACS' - Not seeing that payment method in the PaymentElement πŸ€”

tender ledge
#

It looks like an upgrade option for me. Anyway you won't be charged for transactions in test mode.

carmine harbor
#

Seems like to enable Bank Transfer for Subscriptions i should go for the method of supplying the payment_settings.payment_method_types?

tender ledge
#

From the screenshot it looks like these payment methods are not yet activated.

carmine harbor
#

Hmm I can’t enable or activate via invoice settings

#

Thanks for the support, Ive got a better understanding now! Will keep trying