Activities / Who the operator is / Provides financial services
Is a payment provider
is_payment_provider
The company behind your app is a payment or e-money institution, a money transmitter or a crypto-asset service provider, or supplies software to one.
- scope role
- in the registry since 1.1
- 7 laws in 6 jurisdictions name it
What triggers it
The lint's definition. It is a payment or e-money institution, a money transmitter or a crypto-asset service provider, or supplies software to one. A merchant taking payment for its own goods is not this.
This covers a payment institution, an e-money issuer, a money transmitter or remittance service, and a crypto-asset exchange or custodian.
It implies Provides financial services.
What does not
A merchant that takes payment for its own goods, through a processor it does not run, does not count.
Often confused with Is a bank and Provides financial services.
The law it brings into scope
The kinds of law that name this activity in the LexLint law library, with the number of laws and jurisdictions in each, as of . The examples are chosen by rule, laws in force first and the widest jurisdiction first; each section's page lists every law.
| Area of law | Laws | Jurisdictions |
|---|---|---|
|
Cybersecurity law
Build software securely, handle reported flaws, and report incidents on a deadline.
|
6 | 6 |
|
Communications law
Get consent before marketing, calling, recording or storing data on a device, and honor an opt-out. |
1 | 1 |
This activity implies Provides financial services, so every law that names that activity reaches it too. These areas of law reach it only that way:
- AI law:
16 laws in
8 jurisdictions,
through Provides financial services
Tell people when they are dealing with an AI system or its output, and control the uses the law calls high-risk.
- Privacy law:
15 laws in
8 jurisdictions,
through Provides financial services
Have a legal basis for personal data, honor people's rights over it, and report a breach.
In a declaration
A role says who operates a product, so it is declared in the product's
own lexlint.yml and never in a component's
ACTIVITIES.md: a library cannot make the product that uses
it a regulated party.
In lexlint.yml
History
In the registry since version 1.1, .
Added for Payment Services Technical Standards on Strong Customer Authentication, Personalized Security Credentials and Common and Secure Open Standards of Communication (European Union), the law that turns on it.
In the glossary: Is a payment provider.
The activity registry is LexLint's open list; this page's text is licensed under Creative Commons Attribution 4.0.