OmniStudioAdvancedpaymentspcisecurity
Integrate OmniScript with payment gateways and PCI compliance
Real World Scenario
OmniScript collects credit card for premium payment; PCI audit requires no card data touches Salesforce database.
Expected Answer
• Tokenization via payment provider iframe or JS SDK in OmniScript custom LWC step
• Integration Procedure sends token only to payment API never PAN
• Load DR stores payment confirmation reference not card number
• PCI SAQ scope reduction using provider-hosted fields
• HTTPS TLS 1.2+ Experience Cloud site mandatory
• Audit IP logs scrubbing sensitive payload fields
• Failed payment retry with idempotency key
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Tokenization via payment provider iframe or JS SDK in OmniScript custom LWC step Also consider: Integration Procedure sends token only to payment API never PAN In practice: Load DR stores payment confirmation reference not card number Optimize for scale and operational observability.
Architect Perspective
PCI in OmniScript means token-only IP—any PAN in DR Load is audit failure.