การผสานรวม Payment Intents API

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.

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.

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):

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.

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.

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.

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.

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.

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.

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

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!