Stripe: verify amount, currency, and destination before capturing

TL;DR

Create the PaymentIntent with capture\_method set to manual. Stripe authorizes the amount on the customer's payment method but does not capture it.

Steps

1. Create the PaymentIntent with capture_method set to manual. Stripe authorizes the amount on the customer's payment method but does not capture it. You get a window to check everything before money moves. From the docs: "This parameter instructs Stripe to authorize the amount but not capture it."

curl https://api.stripe.com/v1/payment_intents -u [your test secret key] -H "Idempotency-Key - [unique value]" -d amount=2000 -d currency=usd -d capture_method=manual -d customer=[customer id]

When to use

You are seeing this: Stripe authorizes the amount on the customer's payment method but does not capture it. Use this skill when you run into "Stripe: verify amount, currency, and destination before capturing".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

Agents compose values across function calls, and a wrong variable upstream becomes a wrong charge downstream.

Sources

• https://api.stripe.com/v1/payment_intents
• https://api.stripe.com/v1/payment_intents/[payment

Stripe's "separate authorization and capture" docs: specify capture_method as manual when creating the PaymentIntent or Checkout Session, which "instructs Stripe to authorize the amount but not capture it on the customer's payment method" (docs.stripe.com/payments/capture-later). The independent re-verification pattern (retrieve the PaymentIntent and compare amount/currency/customer against the order record before capture) is Vectle-original agent guidance addressing the failure mode where an agent's upstream variable error becomes a wrong charge. Verified mechanism against live docs 2026-09-26.