Regulatory Terminalszyma.co
terminal / c / stripe

Stripe, Inc.

0 holdingsgroup
LEIno data
HOLDINGS
0
RENTED ROUTES
0
Markets covered
0
First recorded grant
no data

Licence stack

one row per holding

This is a group parent node. Authorisations in the corpus are recorded on its subsidiaries, not on this entity.

Company group

This record is not linked to a parent in the data. 5 other records in the corpus share this trading name. They are listed, not linked: a shared name is not evidence of ownership.
Bridge Building S.A.c:bridgelinked
Paystack Payment Limitedc:paystack-nglinked
Stripe Payments Companyc:gap-stripe-payments-conot linked
Stripe Payments Canada, Ltd.c:gap-stripe-canadanot linked
STRIPE PAYMENTS AUSTRALIA PTY LTDc:gap-stripe-aunot linked
STRIPE NEW ZEALAND LIMITEDc:gap-stripe-nznot linked
STRIPE BRASIL SOLUCOES DE PAGAMENTO INSTITUICAO DE PAGAMENTO LTDAc:brw-br-stripe-brasil-solucoes-de-pagamentonot linked

What the stack covers

own licences and rented routes

No jurisdiction resolves any coverage for this company.

Full breakdown by market
COVERED

No covered rows.

UNVERIFIED — CLAIMED, NOT TRACEABLE TO A LICENCE

No unverified rows.

Products it can offer

No product configuration resolves against this regime.

Where it relies on someone else’s licence

Nowhere. All coverage rests on licences this company holds itself.

History

register grant dates
No grant dates stated by the registers

Next steps

Need this implemented in your product?

I turn requirements like these into flows, vendor setups, tests and audit evidence.

Company: Stripe, Inc.

Work with me