-
-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Collective name to credit card statements #2975
Comments
For an added data point, our host name is already 22 characters in itself so the proposed solution wouldn't leave us with anything better than the current situation. I would probably prefer to allow hosts to change this on a per-collective basis for the collectives they host. Our own Stripe account already is set to use " |
@flaki thanks for the additional info. Then what I'd suggest is for us to add a setting inside |
This issue has been automatically marked as stale because it has not had recent activity. We haven't had the time to address it yet, but we want to keep it open. This message is just a reminder for us to help triage issues. |
@Betree could you assign it to me? |
@Deep1Shikha This issue lacks some comprehensive specs, and I would like us to think a bit more about it since we recently introduced #3689 which is kind of related. |
Note: PayPal has a |
Stripe also has this option on a payment intent basis:
|
User story
As a financial contributor, I can see the collective name I'm contributing to on my credit card statement.
Today only the host name is displayed, but most users contribute to only one collective and probably don't know what the Open Source Collective is.
Today
![image](https://user-images.githubusercontent.com/1556356/76296249-37ebed80-62b6-11ea-9cc4-0574b6e87562.png)
Expected
![image](https://user-images.githubusercontent.com/1556356/76296661-cceee680-62b6-11ea-8782-1e00cb61d77f.png)
Best solution for this problem
This can be achieved thanks to the
statement_descriptor
parameter. Note that the following rules apply:< > \ ' " *
.So my suggestion would be:
We also need to write a test to make sure that no matter what the host & collective names are (special characters, very short length...etc) this always meet the rules mentioned above (we may have to add some tweaks to achieve that).
Context
Requested in https://opencollective.freshdesk.com/a/tickets/4969
Should be re-thinked when implementing #1916
The text was updated successfully, but these errors were encountered: