Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Overview
Versioning
Changelog
    Overview
    Basil
    Acacia
    Previous versions
Upgrade your API version
Upgrade your SDK version
Developer tools
SDKs
API
Testing
Workbench
Event Destinations
Workflows
Stripe CLI
Stripe Shell
Developers Dashboard
Agent toolkit
Stripe health alertsBuild with LLMsStripe for Visual Studio CodeFile uploads
Security
Security
Extend Stripe
Stripe Apps
Stripe Connectors
Partners
Partner ecosystem
Partner certification
HomeDeveloper toolsChangelogAcacia2024-11-20.acacia

Use configurable capture methods and set up future usage for South Korean payment methods

What’s new

The following South Korean payment methods now support setting the capture_method to manual, which overrides the configuration for the Session:

  • South Korean cards
  • Naver Pay
  • Kakao Pay
  • Samsung Pay
  • PAYCO

The following South Korean payment methods now support setup_future_usage, which you set when you create a Session:

  • South Korean cards
  • Naver Pay
  • Kakao Pay

Impact

You can now override the default automatic capture of a payment transaction using South Korean payment methods when you create a Checkout Session. Set capture_method to manual on the payment_method_options parameter for the specific payment method to place a hold on the payment method.

  • South Korean cards
  • Naver Pay
  • Kakao Pay
  • Samsung Pay
  • PAYCO

You can now specify whether to save South Korean payment method details during payment when you create a Checkout Session. For example, set setup_future_usage to off_session in the payment_method_options parameter for the specific payment method to enable charging the customer at a later time, such as for a cancellation fee.

  • South Korean cards
  • Naver Pay
  • Kakao Pay

Changes

ParameterChangeResources or endpoints
capture_methodAdded
Checkout.Session#create.payment_method_options.kakao_payCheckout.Session#create.payment_method_options.kr_cardCheckout.Session#create.payment_method_options.naver_pay
 + 2 more
Checkout.Session#create.payment_method_options.paycoCheckout.Session#create.payment_method_options.samsung_pay

Upgrade

  1. View your current API version in Workbench.
  2. If you use an SDK, upgrade to the corresponding SDK version for this API version.
    • If you don’t use an SDK, update your API requests to include Stripe-Version: 2024-11-20.acacia
  3. Upgrade the API version used for webhook endpoints.
  4. Test your integration against the new version.
  5. If you use Connect, test your Connect integration.
  6. In Workbench, perform the upgrade. You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Related changes

  • Adds network decline code field for Swish and BLIK refunds
  • Adds support for SEPA Direct Debit and Bacs Direct Debit mandate reference prefixes in Checkout Sessions
  • Specifying an originating payment method for Inbound Transfers is now optional
Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access program.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc