lfrefatti-ACH

[rocky hornet]

Hi there!

Good question

What payment_behavior are you using?

[raw beacon]

I'm not using that parameter

But I tested with allow_incomplete and nothing changed

[rocky hornet]

Gotcha.

I think you would need to create a new Sub here, but can you share a Subscription ID that you tested with so I can double check?

[raw beacon]

Sure, here it is
sub_1LIcvZFnn9huPxukaZQqa0PZ

[rocky hornet]

Wait

You tested with allow_incomplete?

Or default_incomplete

allow_incomplete is the default behavior

Have you tested with default_incomplete?

I think that is what you want actually

[raw beacon]

I'll check that

[rocky hornet]

Let me know

I haven't tested this flow myself recently so can't quite remember

[raw beacon]

I tested with allow incomplete on this sub_1LIIdOFnn9huPxuk6B8wQwfB

[rocky hornet]

Yes allow_incomplete should not work

But default_incomplete I believe should do it

[raw beacon]

I'll try default_incomplete now

[rocky hornet]

Let me know!

[raw beacon]

with default_incomplete the same happened

sub_1LIdK1Fnn9huPxukAoMCrmQY

[rocky hornet]

Thanks for testing

Looking

Is there a reason you are using collection_method: 'send_invoice' here?

[raw beacon]

yes, it's part of our payment workflow

we need to calculate application_fee on every invoice

[rocky hornet]

Ah okay

Hmmm okay yeah. I think this is expected since these are asynch payment methods that oftentimes won't fail within 24 hours (if they do fail).

So in these cases you would need to create a new Sub for the Customer as opposed to attempting the invoice again.