Skip to content
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

[sec] Email fields at /tipsy.txt #90

Open
rht opened this issue Jan 2, 2017 · 3 comments
Open

[sec] Email fields at /tipsy.txt #90

rht opened this issue Jan 2, 2017 · 3 comments

Comments

@rht
Copy link
Contributor

rht commented Jan 2, 2017

The email fields at /tipsy.txt are crawlable by bots. Either encode it (a bit cumbersome for end-users) or ...

@da2x
Copy link
Contributor

da2x commented Feb 15, 2017

This isn't really much of a problem. Just be sure to ask publishers to use dedicated email addresses. PayPal requires business accounts to receive service payments anyway, so websits should already be using addresses like [email protected] for this purpose (and bookkeeping).

The only bug here is that the documentation should be improved.

@da2x
Copy link
Contributor

da2x commented Feb 15, 2017

You can also use your merchant account ID instead of an email address.

Note that a merchant account is required when you receive payment for business purposes as per PayPal’s terms of stuff. Forms and documentation should be updated. The generator script should have it's valid email formatting requirement removed, etc.

@rht
Copy link
Contributor Author

rht commented Feb 15, 2017

Right, I see -- it looks like the merchant account ID (in the context of paypal's protocol, and possibly there is an equivalent in dwolla's as well) was devised to replace email address for the button code. This is a breaking change, and could be coordinated with the priv key migration to fix #101.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants