#saber-issuing-useragent
1 messages · Page 1 of 1 (latest)
saber-issuing-useragent
It's a common concept in web developer. We don't expect you to say "Chrome" or "Firefox", we expect you to pass the exact User-Agent value that is associated with your customer as they are signing up for this service if that makes sense
sure thing!
What is the difference between "settings.payments.statement_descriptor
string
The default text that appears on credit card statements when a charge is made. This field prefixes any dynamic statement_descriptor specified on the charge" and "settings.card_payments.statement_descriptor_prefix
string
The default text that appears on credit card statements when a charge is made. This field prefixes any dynamic statement_descriptor specified on the charge. statement_descriptor_prefix is useful for maximizing descriptor space for the dynamic portion." Confusing !
Will you please explain, what is the difference between "settings.card_payments" and "settings.payments" w.r.t account creation. I read it but it looks like both of them serve the same purpose. If that is the case why we have two different fields?
the card payments one works only for card payments, the other one for all payment method types and we recommend setting both
Make sence. Thank you again.
it's definitely a bit confusing at first because card networks have really strict requirements around this