Open castormaster opened 4 years ago
@castormaster It was developed to work with bitpay - we could look into supporting BTCPay if you think it should be possible - can you contact us via https://www.mjwconsult.co.uk/en/contact-us/ if you are interested?
@castormaster It was developed to work with bitpay - we could look into supporting BTCPay if you think it should be possible - can you contact us via https://www.mjwconsult.co.uk/en/contact-us/ if you are interested?
sure, but because btcpay and bitpay uses the same API i think it might be as easy as replacing any hardcoded bitpay urls with a variable so users can point it to their self hosted btcpay server.
There is now a BTCPay extension of CiviCRM.
BTCPay implements the same API as Bitpay for creating and managing invoices, so I feel like I should be able to use this extension to accept bitcoin via my self hosted totally under my control btcpay server insetence. But it does not seem to be working.
https://docs.btcpayserver.org/CustomIntegration/#accessing-the-api-manually
I think the issue is that when I try to run CiviCRM API Bitpay.createkeys with parameters: payment_processor_id={id} and then Run CiviCRM API Bitpay.pair with parameters: payment_processor_id={id} pairingkey={pairing key you created at bitpay earlier}
that bitpay is hardcoded into the api or something, even though when I setup processor details for live payments I made sure it was pointed to the right domain.