Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Donation account cannot currently make live charges, transaction has not been processed
Wanted to make a donation via the donate button but upon click on "Pay" an error message occured: "Your account cannot make live charges. If you are the site owner, please activate your account at https://dashboard.stripe.com/account/onboarding to remove this limitation. If you are a customer trying to make a purchase, please contact the owner of this site. Your transaction has not been processed."
I would like to successfully make a donation.
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
According to this comment there is an issue with invalid birth dates stored with the Stripe service that cannot be resolved easily. It's known and there is ongoing communication to try to fix that but currently donation through this channel is not possible. Sponsoring Codidact on Github might be a viable alternative currently.
0 comment threads
Update: Stripe has now unblocked us and I just successfully made a donation (from a different community where I didn't turn the button off last night). I'll restore the button here on Meta. Again, I apologize to everybody who was trying to support us and hit this roadblock.
The issue was that our payment processor was having trouble getting their scanning automation to recognize one of our identity documents as valid. We were waiting for either human verification or for them to process a better copy. We thought this would be sorted out more quickly than turned out to be the case (they didn't give us a lot of notice).
I temporarily unfeatured the announcement about donations and turned off the button here on Meta. The latter is a site setting that has to be done on every community separately, so before I made the rounds I wanted to ask the team if there's a more expedient way to do that. I also hoped that we'd be turning it back on in short order, and didn't want to change manual settings in 18 places twice.
I apologize for this disruption. It's frustrating for you, and it's embarrassing for us.
1 comment thread