bounties
bounties copied to clipboard
non-USD membership payments: evaluate alternative payment providers
current arrangement lasts only thru Apr 23
see also: non-USD membership payments: p2p wallet #512
context: https://github.com/rchain/bounties/issues/446#issuecomment-373931669
BTC Payment Processing possibilities:
-
BitPay - already implemented on Co-op registration site (private repo), but BitPay account has been disabled (they mistakenly thought we were selling tokens instead of memberships). @evanjensen can we please resurrect the account so that we won't have to teach our code to speak to another Payment Processor?
-
CoinBase Merchant Services - has BTC payment processing through API. USA based and licensed in states.
@ian-bloom aims to re-activate bitpay
Co-op General Manager Lilia (LiliaR: on Discord) is attempting to sort out BitPay merchant account reactivation. This would be the easiest option, requiring far less coding of the registration webapp.
Hey @kitblake
I know there are a lot of great initial verification options out there that could help us expedite the process but when it came to formally approving someone to the discord channel we could then use the appear.in video chat to verify the person. I agree with you that an initial automated process could help us 1) organize the information more efficiently 2) ensure security by using existing measures set by the API 3) allow us a smoother transition for the new member from sign up to the first impression 'welcome' appear.in video.
To your point I had all of those issues as well when signing up for KuCoin, gatehub, and also Changelly.
Again, here is the boiled down list of companies that I felt would be suite our needs: Jumio.com - look at their use cases, they work with Coinbase/Gdax Yodlee.com - money transfer/payment and verification Synapsefi.com - money transfer/payment and verification
I did make a new issue for scalable KYC: #553, eventually. But I had it confused with this one for so long that I won't blame others for doing likewise.
Ok, I transposed my comment to #553 and deleted it here, @AyAyRon-P maybe you can 're-answer' me and do the same. Then we can delete these thread correction posts and keep it all clean.
I thought the point of bitcoin is that we do not need a payment provider. Can't we just post a bitcoin address where to send bitcoin to us and then post the transaction id of the transaction to be applied to membership.
Automating this requires showing the QR code of where to send bitcoin etc. Any verification necessary can be done in the normal KYC process.
RChain not accepting bitcoin suggests a dysfunction of RChain that is not acceptable and needs to be corrected immediately in my view.
I thought the point of bitcoin is that we do not need a payment provider.
We devoted a separate issue to that option: non-USD membership payments: p2p wallet #512