Payment compliance scope
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
reduce PCI DSS scope with tokenization and hosted payment pages.
Planned topics
- PCI DSS applies to systems that store, process, or transmit card data, plus systems connected to them.
- A hosted payment page or fields means card data goes from the customer to the provider, not through Larkspur.
- Tokens let Larkspur keep a reference for refunds and repeat payments without card numbers.
- Fewer systems in scope means less cost, less audit effort, less risk. The exact requirements and version change: verify before recording.
Draft outline details
Demonstration
two diagrams: card data flowing through the web app (large scope) versus straight from the browser to the provider (small scope).
Check your understanding
What does Larkspur store after a hosted payment?
Show answer
A token, last four digits, and the payment status, never the full card number.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.