Two-stage Payment: Implementing Payment Hold on Website

Implementing Payment Hold on Your Website

Imagine a customer ordering construction materials with delivery. The delivery cost depends on the weight, which is only known after packing. If you capture the full amount upfront, any cancellation or price adjustment requires a refund. This increases operational costs by 25-40% and degrades user experience. Refunds and chargebacks cost businesses 2-3% of turnover. We solve this with two-stage payments—payment hold. It blocks funds on the card but does not capture them until confirmation. As a result, chargebacks are cut in half, and customers get a transparent process.

Payment hold is authorization without immediate capture. The money is blocked on the buyer's card but remains with the bank. The merchant can capture only the actual amount or cancel the hold if the deal falls through. In practice, this reduces chargebacks by 30-40% and eliminates overpayment refunds. For businesses, it means a faster fulfillment cycle—on average 1.5 times faster.

Two-stage payment is especially relevant for services with variable costs, pre-orders, and deferred capture. It gives flexibility to the business and security to the customer.

What Problems Does Hold Solve?

• Order cancellation. Funds are not transferred to the seller until confirmation—on cancellation, the hold is released automatically or on request. This eliminates lengthy refunds.
• Variable cost. Delivery, weight, configuration—the final price is unknown upfront. Hold allows authorizing the maximum amount and capturing the actual one using partial capture.
• Quality confirmation. Service provided, customer satisfied—only then capture funds. This reduces risk for service companies.

How Does Two-Stage Payment Work?

The process involves two operations: authorize (block) and capture (capture). Between them, minutes to 7–30 days pass depending on the bank. We configure the payment gateway, handle statuses, and ensure correct hold release.

Stripe

In Stripe, hold is enabled via capture_method: manual:

$paymentIntent = \Stripe\PaymentIntent::create([
    'amount'         => $order->total_cents,
    'currency'       => 'eur',
    'capture_method' => 'manual',
    'payment_method_types' => ['card'],
    'metadata'       => ['order_id' => $order->id],
]);

After 3DS confirmation, status is requires_capture. Funds are blocked. For capture:

\Stripe\PaymentIntent::capture($order->stripe_payment_intent_id, [
    'amount_to_capture' => $finalAmountCents, // less than or equal to original amount
]);

Stripe supports partial capture—you can capture less, and the remainder is automatically released. Useful when the final cost is lower.

YooKassa

Similarly in YooKassa:

$payment = $client->createPayment([
    'amount'   => ['value' => '1500.00', 'currency' => 'RUB'],
    'capture'  => false,
    'payment_method_data' => ['type' => 'bank_card'],
    'confirmation' => ['type' => 'redirect', 'return_url' => $returnUrl],
    'description' => 'Order #' . $order->id,
], uniqid('', true));

Capture:

$client->capturePayment(
    ['amount' => ['value' => '1500.00', 'currency' => 'RUB']],
    $order->yookassa_payment_id,
    uniqid('', true)
);

Canceling a Hold

If the order is canceled before capture—cancel the authorization, otherwise funds remain blocked until expiry. In Stripe:

\Stripe\PaymentIntent::cancel($order->stripe_payment_intent_id, [
    'cancellation_reason' => 'abandoned',
]);

In YooKassa—$client->cancelPayment(...).

Payment System Comparison

Typical Hold Scenarios

Why Hold Is Better Than One-Stage Payment?

One-stage payment captures immediately. On cancellation, a refund is required, taking 3–10 days. With hold, no refund—just cancel authorization. This saves time and money. According to our data, switching to two-stage payment reduces operational costs on refunds by 50% and increases repeat purchase conversion by 10-15%.

Monitoring Expiring Holds

We configure background tasks that notify managers 1–2 days before expiry—you have time to capture or extend authorization. We use cron scripts or queues (Redis/Beanstalkd). We guarantee no hold goes unnoticed.

What's Included in the Work

1. Analysis of business logic and gateway selection.
2. Integration of payment system API (authorization, capture, cancel).
3. Development of status handlers and error scenarios.
4. Testing on sandbox and production.
5. Documentation for use and support during release.

Our Experience and Guarantees

We have implemented hold for 15+ projects: marketplaces, food delivery, fitness clubs. Experience with payment gateways—5 years. We guarantee correct handling of all cases: cancellation, partial capture, expiry. Code undergoes code review and is covered by tests. Your customers will see a transparent payment process with no hidden charges.

Timelines and Cost

Integration timeline—from 3 to 10 business days depending on CMS complexity and gateway specifics. Cost is calculated individually. Contact us for a preliminary assessment of your project. Get a consultation on implementing hold in your business.

Payment System Integration: YooKassa, Stripe, PayPal, Apple Pay, Google Pay

Conversion dropped by 12% immediately after the redesign. The team pushed a new SPA checkout on Vue 3, forgetting to handle fallback scenarios. Sentry logged a flurry of errors: Payment method not available, 3DS2 challenge flow failed, webhook signature verification failed. Users abandoned carts at the payment method selection stage. Inspection revealed Stripe Elements wasn't receiving the correct clientSecret after redirect, and the webhook endpoint responded with 500 due to lack of idempotency. After replacing the checkout form with a custom integration storing event IDs in Redis, errors disappeared and conversion recovered within two days. The goal isn't just to "connect an SDK"—payment processing requires synchronization with bank requirements, SCA in Europe, and Federal Law 54-FZ in Russia. Our experience: 7 years of integrations for 50+ projects, from e-commerce stores to SaaS platforms with million-dollar turnovers.

What's Included in Turnkey Work

• Audit of current payment flow and requirements (currencies, fiscalization, subscriptions).
• Provider selection based on geography and business model.
• Backend integration (Laravel/Node.js/Go) with webhook handling, idempotency, and retries.
• Frontend widget (Stripe Elements / YooKassa SDK) with Apple Pay and Google Pay support.
• Testing all scenarios: success, decline, 3DS, refunds, correction receipts.
• Monitoring of first transactions and documentation.

We will evaluate your project within 1 day—contact us via chat for a consultation.

Provider Comparison: Which to Choose

Stripe wins on flexibility: 135+ currencies vs. YooKassa's single currency. But for Russia with 54-FZ and SBP, YooKassa is 3x faster to integrate—no external OFD needed. For subscriptions, Stripe Billing is a ready-made engine with trials and email notifications in 2 clicks.

How to Choose the Right Provider?

Three key points. Where do your clients live? Only Russia → YooKassa; globally → Stripe. Do you need 54-FZ fiscalization? Yes → YooKassa; otherwise Stripe + cloud OFD. Do you plan subscriptions? Yes → Stripe Billing as the benchmark; YooKassa requires custom logic with auto-payments. Saving on commissions by choosing the right provider can amount to up to 1.5% of turnover. For a project with 2 million RUB per month, that's 360,000 RUB per year.

Where the Real Difficulties Lie

Setting up a test mode takes an hour. Properly handling all scenarios takes weeks.

Webhook reliability. A webhook may not arrive—server unavailable, timeout, network issues. The provider retries with exponential backoff (Stripe up to 3 days). The handler must be idempotent: if payment.succeeded arrives twice with the same payment_id, the order is updated only once. This is implemented by storing event IDs in Redis with a TTL.

3DS2 and redirect flow. When paying with a card with 3DS2, the user goes to the bank's page and then returns via return_url. During this time, the session may expire or the cart may be cleared. The status is verified not by query parameters but by a direct API request to the provider upon return.

Partial refunds and receipts. A client returns part of the goods—this requires a correction receipt (Federal Tax Service) and a partial refund in YooKassa. Stripe natively supports partial_refund. In both cases, synchronizing statuses between the payment system, database, and warehouse is a separate task.

Currency limitations. YooKassa only handles rubles. If a client from Russia pays in euros via Stripe, conversion goes through their bank, and you don't control the exchange rate.

Why Do Webhooks Require Idempotency?

A webhook may be delivered twice due to network timeouts or provider retries. Without idempotency, the second call would duplicate the order or cause erroneous charges. The solution is to store a unique event ID (e.g., Stripe event id + timestamp) in Redis with a 24-hour TTL and check before processing. If the ID already exists, return 200 without executing business logic. Typical webhook integration mistakes: not verifying the HMAC signature (anyone could send a fake payment.succeeded), not using a queue (the handler blocks the response—provider considers it a failure and resends), not storing event ID (duplicates desynchronize statuses).

How We Build the Integration

Architecture. We never store card data—only tokens from the provider. Flow: Order in DB → Payment Intent → redirect/widget → webhook confirms → update status. The source of truth is the status in the payment system.

For Laravel we use stripe/stripe-php or yookassa-sdk. Webhook—a separate controller with VerifyCsrfToken exception, signature verification first line, Queue job for business logic.

For Next.js/React—@stripe/stripe-js + @stripe/react-stripe-js. PaymentElement includes Apple/Google Pay automatically. Example:

const stripe = await stripePromise;
const { error } = await stripe.confirmPayment({
  elements,
  confirmParams: { return_url: 'https://example.com/order/thank-you' },
});

Testing. Stripe CLI: stripe listen --forward-to localhost:8000/webhook. Test cards for all scenarios (3DS, decline, insufficient funds). Cypress checkout flow test in CI—mandatory stability guarantee.

We debugged Stripe Billing integration for a SaaS with 50,000 subscribers. The issue was handling invoice.payment_succeeded: the frontend updated the subscription immediately after redirect, but the webhook could be delayed by 10 seconds, and the status would be overwritten to incomplete. Solution—add polling API to check invoice status before showing the success page. This reduced erroneous cancellations by 18%.

Process and Timeline

Audit → provider selection → backend → frontend → tests → deploy → monitoring.

Pricing is custom. Order integration and your checkout won't crash on the next update.

Links:

• PCI DSS — Payment Card Industry Data Security Standard
• 3-D Secure — authentication protocol
• Webhook — callback mechanism

We guarantee: 7 years of experience, 50+ successful integrations. Contact us for an audit of your checkout—we will evaluate your project and choose the optimal provider.