Stripe Payments & SaaS Billing Systems · 강의

Payment Intents API 통합

다양한 상황에서 안전하고 견고하게 거래를 처리할 수 있도록 동적인 결제 흐름에 Payment Intents API를 사용하는 방법을 배웁니다.

Payment Intents API 통합은(는) CoddyKit의 무료 Stripe Payments & SaaS Billing Systems 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Stripe Payments & SaaS Billing Systems 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Stripe Payments & SaaS Billing Systems 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

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!

자주 묻는 질문

“Payment Intents API 통합” 강의는 무료인가요?

네 — “Payment Intents API 통합” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Stripe Payments & SaaS Billing Systems 강의 전체를 잠금 해제할 수 있습니다. Stripe Payments & SaaS Billing Systems 강의에는 총 4개의 강의가 포함되어 있습니다.

“Payment Intents API 통합”에서 뭘 배우나요?

다양한 상황에서 안전하고 견고하게 거래를 처리할 수 있도록 동적인 결제 흐름에 Payment Intents API를 사용하는 방법을 배웁니다. 브라우저에서 직접 실행하는 실습 코드로 Stripe Payments & SaaS Billing Systems을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Stripe Payments & SaaS Billing Systems을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Stripe Payments & SaaS Billing Systems은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 1번째 강의입니다.

“Payment Intents API 통합” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Stripe Payments & SaaS Billing Systems 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Stripe Payments & SaaS Billing Systems 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

← Stripe Payments & SaaS Billing Systems(으)로 돌아가기