not-a-bank/open-banking-tracker-data

The open banking API directory

open-banking-tracker-data's Issues

Getting error when opening the PayPal page

• Bank's name: Paypal
• The accessed link: https://www.openbankingtracker.com/provider/paypal
• Screenshots:

Request permission to push changes to repo

Unsure if this is the correct process but we are trying to update our bank support list but we got the following error when trying to push some code changes:

remote: Permission to not-a-bank/open-banking-tracker-data.git denied to tl-fredwintan.
fatal: unable to access 'https://github.com/not-a-bank/open-banking-tracker-data.git/': The requested URL returned error: 403

Username:
tl-fredwintan
LizaShTrueLayer

If you need any other information please let me know

Model challenger bank licensing

Proposal

licensing: [
  {
    "status": "acquired",
    "countries": "AU",
    "date": "2018",
    "type": [
      "non-cash-payments-retail",
      "non-cash-payments-wholesale",
    ],
    "article": {}
  }
]

What are the different status options?

• acquired
• applied

Additional apiAuth attribute?

Hi there,

The schema (lovely that you have this) only allows 3 options for apiAuth:
"OAUTH2", "OPENID-CONNECT", "UNKNOWN"

Berlin Group spec allows for certificate based authentication which doesn't use OAuth2 or OpenID Connect. Would it be possible to add an options named "EIDAS" to indicate access based on PSD2 QWAC certificate?

Kind regards
Meint

[Abuse][Santander] [C178021] Cooperation to remove sensitive information posted on GitHub Inc

To the attention of the repository owner ,

Innotec Security manages the fraudulent actions against Santander and all issues related to security incidents against this company.

We have detected that your service is being used to publish leaked sensitive information without authorization, from the following URL(s):

https://github.com/fintecturegit/open-banking-tracker-data/blob/master/data/account-providers/santander-mx.json

• Corporate URLs used by interconnection APIs of apps and servers that have been leaked.

This information is not available publicly elsewhere, should have been kept confidential and whose public availability could pose a security risk to our client, as these URLs could be the target of attacks like DDoS, exploitation of vulnerability, etc.

In addition, according to the international ISO standard: ISO 27001:2013 A.18.1.3.: "Records shall be protected from loss, destruction, falsification, unauthorized access, and unauthorized release, in accordance with legislative, regulatory, contractual, and business requirements".

This unauthorized use of restricted information represents a security risk of Santander. We need your collaboration to stop this leaked information incident, by getting offline this content from the reported the URL(s). If you need more information regarding this incident, please contact our CSIRT 24/7 by replying to this email.

Thank you very much for your attention. Looking forward to your reply.

Regards,

Update apiAggregators data

Hi!

I noticed that the data regarding apiAggregators supporting a bank is not up-to-date / correct - how the include the up-to-date connectors bankingsdk is supporting?

See my other issue regarding missing BIC ... would be easier to connect my bankingsdk data with yours when both would identify the bank also with the BIC -- or like in the "Linked Open Data" style with sameAs / seeAlso attributes ...

Thanks.

Add BIC to data

Hi!

Please include the BIC of the banks - else it's hard to link / use this data in combination with other sources or identify the bank reliable.

Thanks & have a nice day,
Rene