Opening a URI like `bitcoin:bcrt1qu7nl0nxfqwhrrf6v0t60asvq3dympgqdhg03rn?amount=0.00010000` from Chrome on macOS still works as it should.

But opening it through the console, e.g. `/Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt bitcoin:bcrt1qu7nl0nxfqwhrrf6v0t60asvq3dympgqdhg03rn?amount=0.00010000` leads to a duplicate entry on the send screen.

So on macOS it's annoying when debugging the send screen, but otherwise harmless. But we should test the URI handler on different platforms.

Introduced by #16578.
{
    qDebug() << QString("%1: Payment server found an invalid certificate: ").arg(__func__) << cert.serialNumber() << cert.subjectInfo(QSslCertificate::CommonName) << cert.subjectInfo(QSslCertificate::DistinguishedNameQualifier) << cert.subjectInfo(QSslCertificate::OrganizationalUnitName);
}
void PaymentServer::LoadRootCAs(X509_STORE* _store)
{
    
    if (_store)
    {
        certStore.reset(_store);
        return;
    }
    
    certStore.reset(X509_STORE_new());
    
    
    QString certFile = QString::fromStdString(gArgs.GetArg("-rootcertificates", "-system-"));
    
    if (certFile.isEmpty()) {
        qDebug() << QString("PaymentServer::%1: Payment request authentication via X.509 certificates disabled.").arg(__func__);
        return;
    }
    QList<QSslCertificate> certList;
    if (certFile != "-system-") {
            qDebug() << QString("PaymentServer::%1: Using \"%2\" as trusted root certificate.").arg(__func__).arg(certFile);
        certList = QSslCertificate::fromPath(certFile);
        
        QSslConfiguration::defaultConfiguration().setCaCertificates(certList);
    } else
        certList = QSslConfiguration::systemCaCertificates();