Payment Method Authentication Service

Overview

The Payment Method Authentication Service manages 3D Secure (3DS) authentication flows using the Python SDK. 3DS adds an extra layer of security for online card payments by verifying the cardholder's identity with their bank.

Business Use Cases:

• Fraud prevention - Shift liability to issuers for authenticated transactions
• Regulatory compliance - Meet Strong Customer Authentication (SCA) requirements
• Risk-based - Request 3DS for high-risk transactions
• Global payments - Required for many European and international transactions

Operations

Operation	Description	Use When
pre_authenticate	Initiate 3DS flow before payment. Collects device data for authentication.	Starting 3D Secure flow
authenticate	Execute 3DS challenge or frictionless verification. Performs bank authentication.	After pre_authenticate, complete the 3DS flow
post_authenticate	Validate authentication results with issuer. Confirms authentication decision.	After customer completes 3DS challenge

SDK Setup

from orchestratorx_prism import PaymentMethodAuthenticationClient

auth_client = PaymentMethodAuthenticationClient(
    connector='stripe',
    api_key='YOUR_API_KEY',
    environment='SANDBOX'
)

Common Patterns

3DS Flow

sequenceDiagram
    participant C as Customer
    participant App as Your App
    participant CS as Prism
    participant Bank as Issuer Bank

    Note over C: Ready to pay
    App->>CS: 1. pre_authenticate
    CS->>Bank: Check device data
    Bank-->>CS: Return: frictionless or challenge
    CS-->>App: Return authentication URL
    alt Challenge Required
        App->>C: Redirect to bank challenge
        C->>Bank: Enter password/SMS code
        Bank-->>App: Return to return_url
    end
    App->>CS: 2. post_authenticate
    CS->>Bank: Validate result
    Bank-->>CS: Authentication result
    CS-->>App: Return 3DS result
    App->>CS: 3. authorize payment
    CS-->>App: Payment complete

Flow Explanation:

1. Pre-authenticate - Start 3DS flow, collect device data, determine frictionless vs challenge.

2. Challenge (if needed) - Customer completes bank challenge (password, SMS, etc.).

3. Post-authenticate - Validate the authentication result with the bank.

4. Authorize - Proceed with payment authorization using 3DS data.

Frictionless vs Challenge

Flow	User Experience	When It Happens
Frictionless	No interruption	Low risk, returning customer, device recognized
Challenge	Customer enters code	High risk, new device, large amount

Next Steps

• Payment Service - Complete payment after 3DS
• authorize - Use 3DS result for authorization

Additional Resources

• Understanding 3D Secure 2.0
• SCA compliance guide
• Risk-based authentication