Stripe Payments & SaaS Billing Systems · レッスン

強力な顧客認証（SCA）の実装

欧州の取引におけるSCA要件を統合し、セキュリティを強化しながらPSD2などの規制に準拠します。

「強力な顧客認証（SCA）の実装」はCoddyKit上の無料Stripe Payments & SaaS Billing Systemsレッスンです。これはレッスン2/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはStripe Payments & SaaS Billing Systems学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Stripe Payments & SaaS Billing Systemsコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

What is Strong Customer Authentication?

Strong Customer Authentication (SCA) is a regulatory requirement designed to make online payments more secure. It requires customers to verify their identity using at least two independent authentication factors.

Knowledge: Something only the user knows (e.g., password, PIN).
Possession: Something only the user possesses (e.g., phone, hardware token).
Inherence: Something the user is (e.g., fingerprint, facial recognition).

These factors must be independent, meaning compromising one doesn't compromise the others.

PSD2: The Driver for SCA

SCA is a key component of the Revised Payment Services Directive (PSD2), an EU regulation. PSD2 aims to enhance consumer protection, promote innovation, and improve the security of payment services across the European Economic Area (EEA).

For developers, this means ensuring your payment flows can handle dynamic authentication challenges when required, especially for transactions involving European customers and banks.

When is SCA Required?

SCA is generally required for customer-initiated online payments where both the payer's bank and the payee's bank are located in the EEA. Common scenarios include:

One-off card payments.
First payment of a recurring series.
Manually initiated payments (e.g., adding a new card).

It applies when a customer directly interacts with the payment process.

Understanding SCA Exemptions

While broad, SCA has several exemptions to improve user experience for certain transaction types. These include:

Low-value transactions: Payments under €30 (with limits).
Recurring transactions: Subsequent payments in a series initiated by the merchant (after the first one is authenticated).
Trusted beneficiaries: Customers can whitelist merchants.
Transaction Risk Analysis (TRA): Banks may waive SCA if the transaction is deemed low-risk.

Stripe automatically evaluates transactions for these exemptions.

Stripe Simplifies SCA Compliance

Stripe provides tools that automatically handle SCA requirements, making it easier for developers to comply without complex logic. Stripe's APIs are designed to dynamically trigger SCA when needed and manage the authentication flow.

This includes supporting 3D Secure 2, the primary method for card-based SCA, which offers a better user experience than its predecessor.

Payment Intents and SCA Handling

Stripe's Payment Intents API is central to handling SCA. A Payment Intent tracks the entire lifecycle of a payment, from creation to capture.

When a Payment Intent requires SCA, Stripe automatically:

Determines if 3D Secure 2 is needed.
Initiates the authentication flow (e.g., redirecting the user).
Confirms the payment once authentication is complete.

Your application listens for status changes via webhooks.

SCA User Experience: What Happens?

When SCA is required, the user experience typically involves a redirection or a modal dialog:

The customer is redirected to their bank's website or a pop-up.
They enter a one-time password (OTP), approve via banking app, or use biometrics.
After successful authentication, they are redirected back to your site.

This process is managed by Stripe and the card issuer, minimizing direct integration effort for you.

Confirming Payment Intent (Conceptual)

On your server, you'll confirm the Payment Intent after collecting payment method details from the client. Stripe handles the SCA challenge if required.

This Java snippet illustrates the server-side logic for confirming a Payment Intent. Remember, a real implementation requires a valid Stripe API key and handling client-side interactions.

public class SCAConfirmationExample {
  public static void main(String[] args) {
    // In a real application, you'd initialize Stripe with your secret key.
    // Stripe.apiKey = "sk_test_YOUR_SECRET_KEY";

    // Assume 'paymentIntentId' and 'paymentMethodId' are received from your client.
    String paymentIntentId = "pi_EXAMPLE_PAYMENT_INTENT_ID";
    String paymentMethodId = "pm_EXAMPLE_PAYMENT_METHOD_ID";

    System.out.println("Simulating confirmation for PaymentIntent: " + paymentIntentId);
    System.out.println("Using PaymentMethod: " + paymentMethodId);

    // In a live environment, you would call Stripe's API here:
    // try {
    //   PaymentIntent intent = PaymentIntent.retrieve(paymentIntentId);
    //   PaymentIntentConfirmParams params = PaymentIntentConfirmParams.builder()
    //       .setPaymentMethod(paymentMethodId)
    //       .build();
    //   PaymentIntent confirmedIntent = intent.confirm(params);
    //   System.out.println("PaymentIntent status: " + confirmedIntent.getStatus());
    // } catch (StripeException e) {
    //   System.err.println("Error confirming PaymentIntent: " + e.getMessage());
    // }

    System.out.println("If SCA is needed, Stripe automatically prompts the user.");
    System.out.println("Monitor webhooks for final payment status updates.");
  }
}

Testing SCA Flows in Development

It's crucial to test your SCA implementation. Stripe provides special test card numbers to simulate different SCA scenarios:

Use card_authentication_required (e.g., 4242...4242) to force an SCA challenge.
Use other test cards for successful payments or declines without SCA.

Always test with your application's full payment flow to ensure a smooth user experience, including redirects and webhook handling.

SCA Knowledge Check

Let's check your understanding of Strong Customer Authentication.

Which of the following statements about SCA are true?

Recap: SCA for Secure Payments

In this lesson, you've learned about Strong Customer Authentication (SCA), a vital security measure driven by PSD2 regulations in Europe.

SCA requires multi-factor authentication for many online payments.
Stripe's Payment Intents API simplifies compliance by dynamically handling authentication flows, including 3D Secure 2.
Understanding exemptions and testing SCA flows are crucial for a robust payment integration.

Implementing SCA ensures secure and compliant transactions for your European customers.

よくある質問

「強力な顧客認証（SCA）の実装」レッスンは無料ですか？

はい。「強力な顧客認証（SCA）の実装」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Stripe Payments & SaaS Billing Systemsコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Stripe Payments & SaaS Billing Systemsコースには全4レッスンが含まれています。

「強力な顧客認証（SCA）の実装」で何を学びますか？

欧州の取引におけるSCA要件を統合し、セキュリティを強化しながらPSD2などの規制に準拠します。ブラウザで直接実行するハンズオンコードでStripe Payments & SaaS Billing Systemsを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Stripe Payments & SaaS Billing Systemsを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのStripe Payments & SaaS Billing Systemsは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン2/4です。

「強力な顧客認証（SCA）の実装」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このStripe Payments & SaaS Billing Systemsレッスンでコードを書いて実行できますか？

はい。すべてのStripe Payments & SaaS Billing Systemsレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Stripe Payments & SaaS Billing Systemsに戻る