#lowell_revetize - Statement Descriptors
1 messages · Page 1 of 1 (latest)
Hello! The short answer is yes. The longer answer is that it's a bit complicated in practice. What's your goal/issue? What prompted the question?
I want to set the descriptor to something dynamic - so our customer knows what the charge on their account is for.
If they use a bank account to fund the charge then using that statement_descriptor is all I need right? But if it's a card funding the charge then I need the statement_descriptor_suffix too?
That's correct, yep.
Well, for card charges you don't use both, you just use statement_descriptor_suffix.
Note that the statement descriptor length is quite limited, with 22 characters total.
Okay for card changes just the suffix
And yes it's limited...
Gotcha
Oh and for card charges is it looking at the prefix and suffix together is max 22 characters?
Correct.
So I have to put a shortened descriptor in my stripe account settings? It says it has to be a minimum of 2 characters. Or can I leave this field blank?
and just set the suffix?
You need to fill it in.
You may want to read through this page if you haven't yet: https://stripe.com/docs/account/statement-descriptors
Yeah I've been going through it - just trying to clarify what I'm reading haha
In a nutshell, card networks require a static prefix that identifies your business, and allow a dynamic suffix if you want to be more specific about things.
So if I had a store called Green Shoes, my prefix would probably be GS and I might do things like GS* GSHOES.COM for web orders and GS* GSHOES WA for in-store purchases in Washington, or something like that.
Okay another question then - are receipts created automatically when a charge is created? It seems like they are.
They are when the Charge succeeds, if you have the setting enabled in your Dashboard to send them.