rafael.delunan - ACH | Stripe Developers | Page 1

stark saddle Mar 15, 2022, 3:42 PM

#

What APIs are you using to perform this action?

halcyon ingot Mar 15, 2022, 3:53 PM

#

The Dashboard direclty.

stark saddle Mar 15, 2022, 3:57 PM

#

So there is no interaction with the APIs directly at all during this process?

halcyon ingot Mar 15, 2022, 4:02 PM

#

No, in this case, we are not using Plaid yet, nor collecting the Account info using the API, just manually on the dashboard. The Stripe support said there is no log/event/state that tells the microtransaction went through. I'm hoping using any API to identify this payment method got blocked and cannot be verified as didn't receive any microtransaction.

stark saddle Mar 15, 2022, 4:04 PM

#

If you use the API directly to confirm these accounts with microdeposits you can get a response that indicates if they went through or not.

https://stripe.com/docs/api/payment_intents/verify_microdeposits - Payment Intents
https://stripe.com/docs/api/setup_intents/verify_microdeposits - Setup Intents

halcyon ingot Mar 15, 2022, 4:53 PM

#

Thank you Snufkin, so, it seems in this case if I send the request without the optional param I would at least know a state that tells me the payment method was blocked and not charged microtransactions?

stark saddle Mar 15, 2022, 4:58 PM

#

if I send the request without the optional param
I'm not exactly clear what you mean by this. Could you specifically reference one or the other of the APIs I listed above and describe what you mean?

halcyon ingot Mar 15, 2022, 5:00 PM

#

Looks like a micro-transaction ever went from Stripe to Bank, so I don't have the amounts parameters here:
https://stripe.com/docs/api/payment_intents/verify_microdeposits
The answer I got is the payment method were block before Stripe be able to send the deposits.

Stripe API reference – Verify microdeposits on a PaymentIntent – cu...

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

stark saddle Mar 15, 2022, 5:02 PM

#

Ah, okay. That's something different then. Can you share the request ID?

halcyon ingot Mar 15, 2022, 5:34 PM

#

Yes, just a sec. Those 2 for the same customer: req_YmOc6KnuTO34cl
req_4dz6pmYWBBklBK

#

The first request was on Feb 24, more than enough time for receiving a microtransaction but never did.

#

On the other hand, this customer from the same "Group" and bank, attached the bank_account at the same day and proper received the microtransactions: req_wK5kbkMSu9pzcw

surreal lynx Mar 15, 2022, 5:38 PM

#

👋 I'm hopping in since @stark saddle has to head out soon - give me a minute to catch up

halcyon ingot Mar 15, 2022, 5:39 PM

#

Thanks Karbi!

surreal lynx Mar 15, 2022, 5:45 PM

#

To confirm - the issue you're having is that the microdeposits we send to verify a bank account never actually reached the customer, so you're unable to actually confirm the bank account, correct? And your goal is to be able to confirm that the microdeposit did actually reach the customer through the API?

halcyon ingot Mar 15, 2022, 5:47 PM

#

Yes, exactly. It's been happening for some customers from of the same group, which added the bank_account on the same day and only a few received it.

surreal lynx Mar 15, 2022, 6:05 PM

#

I believe if microdeposits fail you should get a customer.source.updated event that changes status of the source object to verification_failed (we mention this here https://stripe.com/docs/ach#ach-specific-webhook-notifications)

ACH guide

Stripe supports accepting ACH payments—directly from bank accounts—alongside credit cards. We currently only support ACH for Stripe businesses based in the US.

halcyon ingot Mar 15, 2022, 6:08 PM

#

Do you think the verification fails only after receiving the microtransactions and calling the verification endpoint or typing it on the Dashboard? If the microtransaction never went to the bank account, would we be able to see it as verification_failed as well?

surreal lynx Mar 15, 2022, 6:09 PM

#

You should still get verification_failed if the microdeposits themselves failed to reach the bank account

halcyon ingot Mar 15, 2022, 6:09 PM

#

Sorry, I got it, yes, I'll try that: If the bank account couldn’t be verified because either of the two small deposits failed, you receive a customer.source.updated notification. The bank account’s status is set to verification_failed.

#

For the customer above that failed, I can't find such an event yet. I'll try all the others that apparently failed.

halcyon ingot Mar 15, 2022, 6:50 PM

#

Do you think the meaning of either of the two small deposits failed is the value is different from the expected, instead of the microtransaction not being executed?

faint notch Mar 15, 2022, 6:53 PM

#

Can you rephrase your question? These would be referring to the same thing but I may be misunderstanding.

halcyon ingot Mar 15, 2022, 7:04 PM

#

Is the customer.source.updatedevent triggered if for some reason Stripe fails to communicate to the bank and make the 2 microtransaction charges?

#

Or will be triggered later when I try to validate and type 2 values which not match?

surreal lynx Mar 15, 2022, 7:12 PM

#

I'm not sure why a customer.source.updated event isn't being triggered when we don't send the microdeposit - I had assumed that our documentation covered the edge case of the actual microdeposits to the bank failing, but I may have been mistaken

halcyon ingot Mar 15, 2022, 7:14 PM

#

The documentation description suggests we would be able to see this type of event but I can't find it indeed.

surreal lynx Mar 15, 2022, 7:25 PM

#

Yeah, I think this may just be how it works (there are a number of rough edges with the microdeposit flow)

halcyon ingot Mar 15, 2022, 7:26 PM

#

Sounds good, thanks so much for the help.

#rafael.delunan - ACH