#evan_best-practices

1 messages · Page 1 of 1 (latest)

tiny merlinBOT
#

👋 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/1280649405648867358

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

quiet oyster
#

Hi there

narrow loom
#

Hey! how's it going

quiet oyster
#

Just to make sure we're on the same page, are these retries customer initiated? in other words, is a single customer (or set of customers) trying to pay multiple times within the course of the week using the same card, and those attempts are being declined?

narrow loom
#

I'm not sure if all of them are customer initiated after the first attempt. I'm guessing most attempt 2 - 5 would be from our automation trying to capture payment on the same card.

If there is a field in the logging events that tells who initiatied, I have a few PIs up now and can look.

Churn Buster—Customer Retention Software for eCommerce / Shopify / ...

Reliably boost subscriber LTV, reducing churn with a process used by top subscription eCommerce brands.

quiet oyster
#

Yes, a PI ID would help

narrow loom
#

Newbie question -- should I send it here or via DM or email?

quiet oyster
#

You can send it here. PI IDs on their own are not sensitive, nor are request IDs

narrow loom
quiet oyster
#

So for pi_3PqitdAoyUxvLRDY1hWn9Ywv

The first two payment attempts were initiated by Stripe. The second attempt was due to smart retries.
The third payment attempt was a manual call to /invoice/id/pay via Churnbuster
The fourth payment attempt was initiated by Stripe, due to smart retries
The fifth was a manual call to /invoice/id/pay via Churnbuster
The sixth (last) was initiated by Stripe, due to smart retries

narrow loom
#

Ah so we likely need to pick either Stripe Smart Retries or Churnbuster so they don't end up clobbering the attempts together yea?

quiet oyster
#

For pi_3PqpTnAoyUxvLRDY0KAY8lW1

The first two payment attempts were initiated by Stripe. The second attempt was due to smart retries.
The third and fourth payment attempts were manual calls to /invoice/id/pay via Churnbuster
The fifth and sixth were initated by Stripe, due to smart retries

quiet oyster
narrow loom
#

Thanks for your help!