Who is responsible for what?
| Party | Responsible for |
|---|---|
| Processor and gateway partners | Processing payments, storing and tokenizing card data, and the PCI-scoped environments in which that happens |
| Lumino | The platform merchants and partners sign in to: accounts, access, onboarding, reporting and the views of risk and disputes |
| The merchant | Its 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?
- A customer enters a card on a hosted payment page, in hosted fields or on a terminal.
- 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.
- The partner returns a token, a stand-in for the card that is of no use anywhere else.
- 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.