#_nerder

1 messages · Page 1 of 1 (latest)

ashen yarrowBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

slender maple
prime olive
#

yes one sec

#

this might be one: req_yKALAsq41ezhmu

#

please also take into account that this purchase is in GBP (so sepa will not work if used), but in this case the customer is using a card

#

so i'm a bit confused

slender maple
#

I think for Standard accounts and SEPA the connected account needs to activate or accept terms, but honestly I'm not 100% sure. I recommend you contact support for assistance, as they'll be able to help with account-specific issues like this better than we can: https://support.stripe.com/contact/email

prime olive
#

Okok, but i don't think is the actual problem here

#

there is probably something i'm not understanding clearly in my integration

#
    const stripeSub: Stripe.Subscription = await this.stripe.subscriptions.create(
      {
        customer: customerId,
        items: [
          {
            price: subscriptionPlan.code,
          },
        ],
        default_payment_method: paymentMethodId, //This is a card
        payment_behavior: 'default_incomplete',
        off_session: true,
        payment_settings: {
          payment_method_types: ['card', 'sepa_debit'],
        },
...other stuff
      },
      {
        stripeAccount: acccount,
      },
    );
#

this is the code i'm using right now to create a subscription

#

what i'm try to accomplish is basically to use the payment method the customer has requested to be used in the frontend

#

and for now since we only support 2 payment methods (cards and sepa) i'm specifying also that

#

but i'm not sure if payment_settings.payment_method_types is for here

slender maple
#

Yep, that makes sense. The error you're getting indicates there's an issue with SEPA not being available for use on the connected account though.

#

It's not an integration error, it's an issue with the connected account.

prime olive
#

ok, but since the paymentMethodId is not SEPA that's why i'm confused

#

i mean, the API fails just in case you might use sepa?

#

what happen if I remove payment_settings.payment_method_types then?

slender maple
#

If you're specifying SEPA then yeah, it will fail, because it's possible that current Payment Method gets detached and a SEPA one gets attached later.

prime olive
#

Ok! that make sense

#

so I guess i should simply avoid specifing that and that's it

slender maple
#

If you don't set payment_method_types then we try to determine the types to use by looking at the default Payment Methods set on the Subscription, Invoice, Customer, and your Invoice template settings in the Dashboard.

prime olive
#

okok, that's what I should do in my scenario

#

i think that i've added that to be extra pedantic, but I didn't know it will cause this issue

#

but then can you clarify to me one thing, I was under the impression that from the platform account you will be able to mandate the payment methods available in the conencted account right?

#

why this is not the case here?

#

because the account being UK is not eligible or something like that?

slender maple
#

No, SEPA is available in the UK. The issue is that Standard accounts have full Dashboard access and more control over what's going on it when it comes to things like payment method options.

prime olive
#

Ok I see

ashen yarrowBOT
prime olive
#

btw, I guess that issue is part of the same: req_ZxKJ55ZeWnrTfH

#

The payment method type sepa_debit does not support the currency gbp.

placid crystal
#

Hmmm, that seems like it might be a mistake on our end. Either the error message is wrong or something else is going on

prime olive
#

but i guess it should be correct

#

UK is outside SEPA no?

placid crystal
#

We call out in our docs that GB is a valid country, so I'm a bit confused

prime olive
#

i'm always confused with this too

#

i thought that for UK and GPB purhcases I should use bacs_debit

#

by the way, this shouldn't be an issue as well since the payment method used is a card as well

placid crystal
#

Let me dig a bit and circle back

prime olive
#

easy, there is no rush

#

i'm also checking with customers if SEPA is indeed active in their account

#

becuase it's a bit sus

placid crystal
#

Oh, duh. It's because the currency has to be EUR. You can still use it in the UK, but the currency would have to be EUR

prime olive
#

ok!

#

As the same is for bacs_debit but on the other way around!

#

which triggers this error if you attempt to purchase in eur

#

ok this make sense

#

but anyway it should never happen in my integration so it's fine for me to fallback to automatic payment methods

#

the sus thing for me is this

#

SEPA DD is active by default, in the configuration I create for my connected accounts

#

so it should be active

#

I think that the error message for creating a sub might be wrong IMO

placid crystal
#

Which error message?

prime olive
#

when creating a sub i receive this: The payment method type sepa_debit is invalid. Please ensure the provided type is activated in your dashboard

#

check this reqid: req_yKALAsq41ezhmu

#

but this is ALSO a charge in GBP, with the same config

#

so even if the error is saying that SEPA is inactive (and i suspect is not), the subscription creation simply is failing because sepa is not supported for non eur purchases

placid crystal
#

Right, so you're saying a better error message would call out the currency as the reason, yes?

prime olive
#

Yes, I guess that the error is a bit misleading here

placid crystal
#

Got it. Happy to raise that as feedback. I definitely agree

prime olive
#

you can check for me if SEPA is active in an account?

#

so that we are 100% sure?

placid crystal
#

This is for one of your Connect accounts, yes?

prime olive
#

yes

placid crystal
#

What type of account? Express? Standard?

prime olive
#

Standard: acct_1NwVgmJ4383ARj8v

placid crystal
#

What's your platform account ID?

prime olive
#

this: acct_1G1MYJHTyY8xD8aG

placid crystal
prime olive
#

no yes it is

#

pmc_1LbMQdHTyY8xD8aG8zTO2HFJ

#

if you see here is On by default

placid crystal
#

Sorry, I think I mangled my words a bit. It doesn't seem to be on for that account and the configuration object indicates that it's not requested which means that the owner of the account has not turned on SEPA

#

They have to manually go in and turn it on themselves if I'm understanding correctly

prime olive
#

ok, even IF i stated it in my configuration from the platform?

#

than what is the purpose of this page:

#

my understanding here is:

From the platform I decide which payment methods are active in my connected accounts

#

Ok wait!

#

It was a misunderstanding from my end

#

if you check this request: req_ZxKJ55ZeWnrTfH

#

even when creating a subscription the error is correct: The payment method type sepa_debit does not support the currency gbp.

#

So indeed in the other connected account is not active brecuase the customer manually turned it off 😅

#

sorry for the confusion

#

I had 2 UK accounts with similar issues, and i thought they were the same problem

ashen yarrowBOT