#Jkas

1 messages · Page 1 of 1 (latest)

mint phoenixBOT
fierce delta
#

Hi there

#

If ACH_credit_transfer is one of the payment_method_types and the Customer doesn't already have an ACH CT Source, then yes, one will be automatically created.

night tulip
#

Why is it a source and not a payment method? I thought sources were a thing of the past.

fierce delta
#

Because our ACH Credit Transfers is still on Sources

#

And hasn't been built on PaymentMethods yet

night tulip
#

I'm seeing some of these ACH sources filled with dummy data and some actually have what looks like real data - customer email and bank names in them. I'm curious how those are getting created and the difference between them?

fierce delta
#

None of them should have dummy data if you are in live mode.

#

Do you have an example that I can look at?

night tulip
#

How would it not be dummy data if it's automatically getting generated with no data provided from a client?

#

It looks like the generation of the Subscription is causing it to be created. Maybe we're passing in payment information through the Sub payload? I'd need to check.

fierce delta
#

I don't know what you mean by "dummy" data.

#

ACH Credit Transfers works via a push from the customer to VBAN (virtual bank account number)

night tulip
#

It's possible that I saw this data in test mode, I'm not sure.

fierce delta
#

Gotcha. Yes this is likely a testmode thing

#

If you provide an example I'd be happy to take a look

night tulip
#

Ok, that makes sense. I'm just not seeing how we're pushing any ACH data to Stripe, which is why I was imagining that Stripe automatically creates this account for a customer internally.

#

Let me see if I can find an example.

fierce delta
#

Yes you would not send us this data

#

This is ACH Credit Transfer, not ACH Debit

#

They are vastly different

night tulip
#

Ok

#

What ID would you need

#

I can send you a live example

fierce delta
#

Customer or Source ID

night tulip
#

src_1LhGuzEkTO8kaKcKJujVSQZm

fierce delta
#

Okay can you clarify what you mean by dummy data here or what is unexpected? The owner email on the Source is generated due to the Customer object which the Source is attached to.

#

This is necessary for the refund process for ACH CT

night tulip
#

Ok, but where is this account information coming from? I'm not seeing how we're sending that to Stripe.

fierce delta
#

The account number/routing are a VBAN that Stripe generates

#

It is an account that Stripe controls

night tulip
#

Every since one of these is a Wells Fargo account - is that expected?

#

So the Wells Fargo account is Stripe.

fierce delta
#

Yes it is our account

night tulip
#

So this source was automatically generated by Stripe?

fierce delta
#

Correct

night tulip
#

When does that happen during the process of Customer/Subscription creation?

#

We don't need this account. We are importing them into our local system, however. But we are never using them.

fierce delta
#

This happens when you create a send_invoice Subscription and have ach_credit_transfer as a payment_method_type that can be used to pay the invoice(s)

#

So if you don't want this

#

Then you can turn this off in your invoice settings

night tulip
#

Do these automatically generated accounts need to be created for a customer with a "send_invoice" collection method? Is there another payment_method_type to use for these type of Subscriptions that wouldn't generate a source?

fierce delta
#

Let me link the page

#

Yeah any other payment method type won't generate a Source since this is the only push-based (customer initiated) payment method type (in USD).

#

And turn off ACH Credit Transfer from the Default payment terms section

night tulip
#

I'm not seeing that we're indicating ach_credit_transfer anywhere in our codebase. Is that the default?

fierce delta
#

Then you won't see this Source created and your customers won't be able to pay you with ACH CT

night tulip
#

I'm not seeing And turn off ACH Credit Transfer from the Default payment terms section

#

Is that permissions based?

#

Oh, I see the icon for it.

fierce delta
#

Yep the "Manage" button

night tulip
#

If we turn off ACH Credit Transfer as a payment option, are we still able to create Subscriptions with a "send_invoice" collection method?

fierce delta
#

Yep

#

It is not required by any means

#

Just an option that you can offer if you want

night tulip
#

And the customer will simply not have any payment sources/methods at all in Stripe?

fierce delta
#

Correct. They would use the Hosted Invoice Page to pay with a Card or one of the other payment method options you have selected on the page above.

#

You can test this out by creating a Customer in testmode with the owner email of your Stripe account and then creating a send_invoice Subscription for that Customer

night tulip
#

Can I safely detach these ACH Credit Transfer accounts from existing customers with "send_invoice" only Subscriptions?

#

These are all subscriptions paid outside of stripe. We're just using Stripe in this case for subscription/invoice management.

fierce delta
#

Yep you can detach them if you want

night tulip
#

Does detaching them put these customers at risk at all in the future if they create a new Subscription with "send_invoice"? Or will another new ACH Credit Transfer account get generated by Stripe at that point?

#

I'm trying to get these customers that switch between collection methods only have a single default payment ID associated with them. Some of these customers have both a default_source as well as a default_payment_method attached to their customer record, which gets confusing and potentially buggy.

fierce delta
#

If you have ACH CT enabled, and the Customer doesn't have an ACH CT Source attached, then a new one will be created when a Sub is created.