0Pricing
Stripe Payments & SaaS Billing Systems · Leçon

Intégration de l’API Payment Intents

Apprendre à utiliser l’API Payment Intents pour des flux de paiement dynamiques, en garantissant un traitement sécurisé et robuste des transactions dans divers scénarios.

Intégration de l’API Payment Intents est une leçon Stripe Payments & SaaS Billing Systems gratuite sur CoddyKit. Ceci est la leçon 1 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Stripe Payments & SaaS Billing Systems, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Stripe Payments & SaaS Billing Systems comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

Why Payment Intents?

Welcome! Today, we're diving into Stripe's Payment Intents API. This is a powerful tool for managing complex payment flows.

Before Payment Intents, simple charges worked for basic payments. But what about payments that need extra steps, like 3D Secure authentication?

Payment Intents solve this by representing your intention to collect a payment, allowing for dynamic, multi-step processes.

The Payment Intent Object

A Payment Intent is an object that tracks the lifecycle of a customer's payment attempt. It guides you through the necessary steps to complete a payment.

  • Created: The intent is ready to start.
  • Requires Action: Customer needs to authenticate (e.g., 3D Secure).
  • Succeeded: Payment is complete.
  • Canceled: The payment attempt was abandoned.

This object helps manage everything from initial creation to final confirmation.

Server-Side: Creating an Intent

The first step is always to create a Payment Intent on your server. This ensures sensitive details like the amount and currency are controlled server-side.

You specify the amount, currency, and payment method types you'll accept (e.g., 'card'). Stripe then returns a PaymentIntent object, which includes a client_secret.

Try running this simplified server-side example (Java):

import java.util.List;
import java.util.Map;

// This is a simplified example to illustrate server-side intent creation.
// In a real application, this would involve calling Stripe's API.
public class Main {
  public static void main(String[] args) {
    long amount = 1000L; // Example: $10.00 in cents
    String currency = "usd";
    String paymentMethodType = "card";

    System.out.println("--- Server-Side Payment Intent Creation ---");
    System.out.println("Creating Payment Intent for: " + amount + " " + currency);
    System.out.println("Payment method type: " + paymentMethodType);
    System.out.println("\nStripe API call (conceptual, using Java client library):\n");
    System.out.println("  PaymentIntent.create(Map.of(");
    System.out.println("    \"amount\", " + amount + "L,");
    System.out.println("    \"currency\", \"" + currency + "\",");
    System.out.println("    \"payment_method_types\", List.of(\"" + paymentMethodType + "\")");
    System.out.println("  ));");
    System.out.println("\nStripe would return an object including:\n");
    System.out.println("  \"id\": \"pi_mockPaymentIntent123\",");
    System.out.println("  \"client_secret\": \"pi_mockPaymentIntent123_secret_mockSecretString\"");
    System.out.println("\nThe client_secret is then sent securely to the client-side.");
  }
}

Client-Side: Confirming the Payment

Once your server sends the client_secret to your frontend, you use Stripe.js to confirm the Payment Intent. This is where the customer interacts with the payment form.

Stripe.js handles the collection of payment details and any required authentication (like 3D Secure) automatically, using the client_secret to link to the server-created intent.

  • 1. Collect details: Customer enters card info.
  • 2. Call stripe.confirmCardPayment(): Pass the client_secret and card details.
  • 3. Handle result: Stripe returns the final status.

Understanding Payment Statuses

The status field of a Payment Intent is crucial for understanding its state. Here are the common ones:

  • requires_payment_method: Needs payment details.
  • requires_confirmation: Ready to be confirmed.
  • requires_action: Customer needs to complete an action (e.g., 3D Secure).
  • processing: Payment is being processed.
  • succeeded: Payment was successful!
  • canceled: Payment was canceled.

Your application logic should react to these statuses.

Handling 3D Secure & SCA

Strong Customer Authentication (SCA), often involving 3D Secure, is a regulatory requirement in Europe for many online card payments. Payment Intents are designed to handle this seamlessly.

If a payment requires SCA, the Payment Intent's status will change to requires_action. Stripe.js will then automatically prompt the customer to complete the authentication step (e.g., redirect to their bank's page).

Your client-side confirmation call will then complete once authentication is done.

Securing the client_secret

The client_secret is a unique key that ties a client-side action to a specific Payment Intent on your server. It's safe to expose on the client, but only for a limited time.

  • Generate on server: Always create the Payment Intent and its client_secret on your backend.
  • Pass securely: Send the client_secret to your frontend (e.g., via a secure API endpoint).
  • Use promptly: Use it immediately on the client to confirm the payment.

Never generate or store the client_secret directly on the client side.

Retrieving & Updating Intents

You can retrieve a Payment Intent at any time using its ID from your server-side code. This is useful for checking its current status or details.

You can also update a Payment Intent (e.g., change the amount or currency) as long as it hasn't been confirmed yet. This offers flexibility for dynamic pricing or order changes before final payment.

However, once confirmed, a Payment Intent cannot be modified.

Payment Method Attachment

When a Payment Intent succeeds, Stripe can optionally save the customer's payment method for future use. This is done by attaching the payment method to a Customer object.

This is useful for recurring payments or one-click checkouts. You'd set the setup_future_usage parameter when creating the Payment Intent, or explicitly create a Setup Intent (a topic for another lesson!).

Always ensure you have customer consent to save payment details.

Quick Check: Payment Intents

You've learned about the Payment Intents API. Let's test your understanding!

Recap: Mastering Payment Intents

Great job! You've learned the fundamentals of Stripe's Payment Intents API.

  • Payment Intents manage payment lifecycles, especially for multi-step or authenticated payments.
  • You create them server-side, get a client_secret, and confirm them client-side with Stripe.js.
  • Statuses like requires_action help you handle dynamic flows like 3D Secure.

This API is essential for building robust and compliant payment experiences. Keep practicing!

Questions Fréquemment Posées

La leçon « Intégration de l’API Payment Intents » est-elle gratuite ?

Oui — le texte complet de « Intégration de l’API Payment Intents » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Stripe Payments & SaaS Billing Systems, passe à CoddyKit PRO. Le cours Stripe Payments & SaaS Billing Systems comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Intégration de l’API Payment Intents » ?

Apprendre à utiliser l’API Payment Intents pour des flux de paiement dynamiques, en garantissant un traitement sécurisé et robuste des transactions dans divers scénarios. Tu pratiques Stripe Payments & SaaS Billing Systems avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer Stripe Payments & SaaS Billing Systems ?

Aucune expérience préalable n'est requise. Stripe Payments & SaaS Billing Systems sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 1 sur 4.

Combien de temps prend la leçon « Intégration de l’API Payment Intents » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon Stripe Payments & SaaS Billing Systems ?

Oui. Chaque leçon Stripe Payments & SaaS Billing Systems inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

  1. Intégration de l’API Payment Intents
  2. Gestion des webhooks pour les événements asynchrones
  3. Gestion efficace des remboursements et des litiges
  4. Mettre en œuvre l’idempotence pour des API de paiement fiables
← Retour à Stripe Payments & SaaS Billing Systems