#kitkat-docusign-support

1 messages · Page 1 of 1 (latest)

pulsar jasperBOT
lost olive
#

Hi, can you share the specific integration document you followed? I'd like to make sure that we are both looking at the same thing.

shadow prairie
#

What is returned to me via a Docusign webhook is meta information that gives me a Stripe customer id and Stripe Payment Source, in this case it's a ba_* id

#

for bank account

lost olive
#

I see, with this question I recommend that you reach out to docusign as they own this. This server is dedicated for developers who need Stripe integration help.

shadow prairie
#

That's fine but I'm not really asking about what docusign is doing, I'm more asking about what occurs on Stripe's side when a customer has an ACH debit Payment Method attached to them

lost olive
#

Since we do not own this docusign integration, I won't be able to say what exactly they are doing. However, if you're interested in learning how ACH debit Payment Method works on Stripe, you can start here: https://stripe.com/docs/payments/ach-debit

shadow prairie
#

I can see the wehook logs and I can see the DocuSign application making a POST to /v1/customers/cus_######/sources with a { "source": "btok_####" }

#

Which results in a new bank_account object

lost olive
#

You'd want to talk to Doucsign, I'm afraid

shadow prairie
#

Disappointing, okay.

wet bough
#

kitkat-docusign-support

#

Stripe wouldn't send any email not any Event for this. They are using an old integration path from multiple years ago. I would assume Docusign handles all of this, tracking micro-deposits verification, handling emails, etc. But really it's a question for them as they built the whole integration, we don't really have context on how it works

shadow prairie
#

Thanks for that, I'll bring this up with them.