#mbouri-sepa-cy

1 messages · Page 1 of 1 (latest)

drifting sail
#

hi! SEPA CT is not a public payment method so most likely the Stripe account you're trying to do this on doesn't have access.

brisk nimbus
#

Thx for responding. I am using test mode, how to check if my stripe account has acces or could use SEPA ?

drifting sail
#

generally, if you're getting that error it means you don't have access.

can you share the request ID req_xxx from the error? https://support.stripe.com/questions/finding-the-id-for-an-api-request

Also what guide are you following? Sources are mostly deprecated.

brisk nimbus
drifting sail
#

ah right

brisk nimbus
#

my request ID is req_dFMNeo1s6GVo3R

drifting sail
#

cool cool. I'd suggest using one of the other docs I linked, that Sources-based one is legacy I believe and we should get rid of it

brisk nimbus
#

yes but bank transfer feature does not respond to my usecase

#

I would like to generate virtual bank type 'sepa' linked to my stripe account,

#

and then I would like to show the IBAN number of my virtual bank to my customer on the website

#

and let the customer do the sepa transfert manually

#

the problem is that it work perfectlty when I use ach_credit_transfe

#

but when using 'sepa_credit_transfer' it returns error :/

drifting sail
#

yep because sepa_credit_transfer Sources are a private feature as I mentioned

#

ach_credit_transfer Sources are public

#

but we're not going to release sepa_credit_transfer Soruces, instead we launched the BankTransfer payment method I linked above publicly

#

and we will replace ach_credit_transfer Sources with that API as well when it's ready

brisk nimbus
#

I must contact stripe to activate sepa_credit_transfer or what should I do ?

drifting sail
#

it works for your use case (generating a virtual number and showing it to the Customer), that's not a problem. Basically you should ideally start using that new API (and contact our support team to get access to the ACH CT beta on the new API) and move away from Sources

drifting sail
#

For ACH CT you can keep your existing code on Sources or get access to the beta of ACH CT on the new API and migrate that code to it

brisk nimbus
#

thank you karllekko but my customers are europeans so I need to use SEPA CT because ACH CT is not supported in europe

drifting sail
#

I never said you couldn't use SEPA ??

#

to be clear on the state :
legacy Source API

  • ACH CT — public option today, but will be launching on the new API soon and has a beta
  • SEPA CT — private beta today, will not ever launch since we built this as the new API instead

new BankTransfer API

  • ACH CT — private beta today, will launch publicly as our official permanently supported option
  • SEPA CT — public option today
  • also supports UK/JP/MX bank transfers on that same API and in general is the future option, Sources are legacy