Skip to content
Lumino

Trust · Security

Security at Lumino

Lumino’s approach to security starts with keeping card data out of places it does not need to be. Card details are captured and tokenized within the secure environments of Lumino’s processor and gateway partners, and are not stored directly by Lumino. Lumino, its partners and each merchant then have distinct responsibilities, set out below.

Summarize with

Who is responsible for what?

PartyResponsible for
Processor and gateway partnersProcessing payments, storing and tokenizing card data, and the PCI-scoped environments in which that happens
LuminoThe platform merchants and partners sign in to: accounts, access, onboarding, reporting and the views of risk and disputes
The merchantIts own devices, logins and staff, how it collects card details, and its own PCI self-assessment

Lumino is not itself a payment processor or card network. Payment processing, cardholder data handling, tokenization and PCI scope are provided through Lumino’s processor, gateway and infrastructure partners. A merchant’s own obligations vary with the processor, payment method, business model and integration type.

What happens to a card number, step by step?

  1. A customer enters a card on a hosted payment page, in hosted fields or on a terminal.
  2. The details go to the payment environment of a processor or gateway partner. With hosted capture they do not pass through the merchant’s website.
  3. The partner returns a token, a stand-in for the card that is of no use anywhere else.
  4. Systems downstream work with that token, not the card number, for refunds, repeat charges and reporting.

This is why the way you collect a card matters more than any single control. A card typed into a hosted page stays in the payment environment; a card number written on paper or sent by email does not.

How is card data protected?

  • Tokenization at capture. Card details are exchanged for a token where they are entered. Systems downstream work with the token, not the card number.
  • Hosted capture. Hosted payment pages and hosted fields send card details straight to the payment environment, so they do not pass through a merchant’s website.
  • Partner-controlled storage. Stored cards live in partner vaults. See card-on-file.

What should a merchant do?

  • Give each person their own login, and limit who can issue refunds.
  • Never take card numbers by email, chat or on paper.
  • Keep terminals in sight and check them for tampering.
  • Complete your PCI self-assessment each year. See PCI.
  • Tell us at once if you suspect an account has been accessed by someone else.

What can a security reviewer request?

If your company reviews its suppliers, tell us what the review requires. The usual requests are below.

  • A completed security questionnaire, for enterprise reviews.
  • Partner attestation documents for the payment environments. See PCI.
  • A description of which systems and partners handle which data. See data protection.
  • Details of the partners involved in delivering the service to you.

How do you report a security concern?

Write to partner.support@golumino.com with “Security” in the subject line, or call 1-866-488-4168. Please include what you saw, when, and how we can reach you. Do not include card numbers or passwords in the message.

What this page does not claim

This page describes Lumino’s model and does not list certifications or technical specifications. For security questionnaires and partner documentation, contact us and say what your review requires.

FAQ

Security: questions, answered

Does Lumino store card numbers?

Card data is tokenized at capture and handled within partner-controlled secure environments. It is not stored directly by Lumino.

Can Lumino complete a security questionnaire?

Yes, for enterprise reviews. Contact us with the questionnaire and your timeline.

Who do I tell about a suspected breach?

Email partner.support@golumino.com or call 1-866-488-4168 straight away.

What is tokenization?

Tokenization replaces a card number with a token at the moment the card is entered. The token can be used to refund or charge that card again through the same payment environment, and is of no use outside it.

What does shared responsibility mean?

It means security is divided between the parties involved. Processor and gateway partners are responsible for the environments that handle card data, Lumino for its platform, and each merchant for its own devices, logins, staff and the way it collects cards.

Does Lumino hold a security certification of its own?

None is claimed on this page. PCI DSS compliance for the payment environments is maintained by Lumino’s processor and gateway partners, and their attestation documents can be requested for a review. See PCI.

Is it safe to take a card number over the phone?

It puts the card number in your hands, which widens what you are responsible for. Sending a payment link lets the customer enter the card themselves on a hosted page.

Summarize with