Integración de la API Payment Intents
Aprenda a utilizar la API Payment Intents para flujos de pago dinámicos y gestionar transacciones de forma segura y sólida en distintos escenarios.
Integración de la API Payment Intents es una lección gratuita de Stripe Payments & SaaS Billing Systems en CoddyKit. Esta es la lección 1 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Stripe Payments & SaaS Billing Systems, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Stripe Payments & SaaS Billing Systems incluye 4 lecciones en total.
Partes de esta lección aún no han sido traducidas y se muestran en inglés.
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 theclient_secretand 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_secreton your backend. - Pass securely: Send the
client_secretto 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_actionhelp you handle dynamic flows like 3D Secure.
This API is essential for building robust and compliant payment experiences. Keep practicing!
Aprende Stripe Payments & SaaS Billing Systems con un tutor de IA — gratis
Escribe y ejecuta código real en tu navegador, obtén ayuda instantánea de un tutor de IA disponible 24/7 y continúa donde lo dejaste en la web o en la aplicación.
- Cursos
- 12
- Lecciones
- 48
Preguntas frecuentes
¿La lección «Integración de la API Payment Intents» es gratis?
Sí — el texto completo de «Integración de la API Payment Intents» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Stripe Payments & SaaS Billing Systems, actualiza a CoddyKit PRO. El curso de Stripe Payments & SaaS Billing Systems incluye 4 lecciones en total.
¿Qué aprenderé en «Integración de la API Payment Intents»?
Aprenda a utilizar la API Payment Intents para flujos de pago dinámicos y gestionar transacciones de forma segura y sólida en distintos escenarios. Practicas Stripe Payments & SaaS Billing Systems con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.
¿Necesito experiencia previa para empezar Stripe Payments & SaaS Billing Systems?
No se requiere experiencia previa. Stripe Payments & SaaS Billing Systems en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 1 de 4.
¿Cuánto tiempo toma la lección «Integración de la API Payment Intents»?
La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.
¿Puedo escribir y ejecutar código en esta lección de Stripe Payments & SaaS Billing Systems?
Sí. Cada lección de Stripe Payments & SaaS Billing Systems incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.
Todas las lecciones de este curso
- Integración de la API Payment Intents
- Gestión de webhooks para eventos asíncronos
- Gestión eficaz de reembolsos y disputas
- Implementación de idempotencia para API de pagos fiables