#michal-prc_best-practices

1 messages · Page 1 of 1 (latest)

normal yewBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1300433524079202375

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

buoyant lava
#

Hi

#

The guide you were sharing is a very good starting point

dull obsidian
#

So this will retry the payment using the same direct debit mandate however may times I set it to?

#

I can't see an option for BASC direct debit there

buoyant lava
#

That's applied for all PaymentMethods

#

There is just a restriction in ACH AFAIK. that's why you have a separate option for it.

dull obsidian
#

Is there a way to test it in a sandbox?

#

I haven't seen a test data for direct debit that will accept first payment and fail a subsequent one

buoyant lava
#

No Smart retreis are only available in live mode I think.

#

You can simulate a failure

#

but you can't make a test that initially succeed and then fails

dull obsidian
#

also there is this clause about direct debit in the docs "Bank debit methods
To avoid bank fees, Stripe ​doesn’t retry invoice payments that customers made with bank debit methods including: BECS direct debit, Bacs direct debit, or SEPA direct debit."

buoyant lava
#

Ah sorry, I know this for SEPA... I didn't knew this for BECS

#

in that case yes it's applied to all Bank Debit

#

so you'll need to implement retries using your own integration.

dull obsidian
#

I want to make sure that the subscription and the invoice wont be cancelled after a failed payment, where do I configure that?

buoyant lava
#

indefinitely?

dull obsidian
#

up to two retries

buoyant lava
#

The only tow options are under Invoice status

dull obsidian
#

So let's say I've created a subscription now using this data: sort code - 108800 account number - 00012345, which will evaluate to success. How do I simulate the failure of the next payment?

buoyant lava
#

what you can do is to use Stripe test clock

#

you update the payment method with a failure one

#

108800 92222227

#

then advance the time

#

Ah nope this is not valid...

#

I think there is no test data for BACS

#

You can simulate failure, using this card 4000000000000341

dull obsidian
#

unfortunatley I am only interested in BACS

normal yewBOT
dull obsidian
#

Hello

#

Is there a way to simulate a scenario where first BACS direct debit payment is a succes and the second one is a failure?

buoyant lava
#

I think I already answered this question.

dull obsidian
#

Thanks