You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On previous version of the Edge Wallet, the Payment Protocol was supported for a number of coins.
Currently, after Edge re-implemented the Payment Protocol, now only these 4 coins are supported:
BTC
BCH
LTC
DOGE
A Dash user attempting a payment with the Edge Wallet paying an Anypay merchant saw this error message:
He confusedly reached out to me asking what was wrong. I explained that it appears Edge does not currently support the Payment Protocol with the Dash blockchain.
Since it was possible in the past, I believe it is possible for Edge to re-implement support for Dash with the Payment Protocol.
Here is an Anypay QR code that includes Dash as a payment option that anyone can use for testing purposes:
Alternatively, your own invoices can be generated independently for testing purposes at:
On previous version of the Edge Wallet, the Payment Protocol was supported for a number of coins.
Currently, after Edge re-implemented the Payment Protocol, now only these 4 coins are supported:
A Dash user attempting a payment with the Edge Wallet paying an Anypay merchant saw this error message:
He confusedly reached out to me asking what was wrong. I explained that it appears Edge does not currently support the Payment Protocol with the Dash blockchain.
Since it was possible in the past, I believe it is possible for Edge to re-implement support for Dash with the Payment Protocol.
Here is an Anypay QR code that includes Dash as a payment option that anyone can use for testing purposes:
Alternatively, your own invoices can be generated independently for testing purposes at:
https://anypayx.com > Get Started > Collect Payment
It seems like this line may hold the key to a good starting place for this issue:
edge-react-gui/src/constants/WalletAndCurrencyConstants.ts
Line 532 in 8916a6c
The text was updated successfully, but these errors were encountered: