Recurring Payment Integration: Tokenization & Dunning Strategy

Recurring payment subscriptions make income predictable. But up to 30% of recurring transactions fail: expired cards, insufficient funds, bank blocks. Without automatic failure handling, you lose up to 15% of subscription revenue. For a monthly turnover, that's a tangible loss. Integrating recurring payments with tokenization and a dunning strategy recovers up to 80% of failed charges. We have implemented such systems for Stripe and CloudPayments on projects with thousands of subscribers. Experience: 10+ years in payment processing and over 50 subscription projects. Get a consultation on integration today.

How to implement recurring payment integration using tokenization?

Tokenization means storing payment data as a token at the gateway. The first payment requires user involvement; subsequent ones are server-initiated. Stripe uses SetupIntent for securely collecting card details, then creates a PaymentIntent with off_session: true to charge without 3DS. This is the standard approach in Stripe documentation.

Server — saving the payment method

\Stripe\Stripe::setApiKey(config('services.stripe.secret'));

$stripeCustomer = \Stripe\Customer::create([
    'email'    => $user->email,
    'metadata' => ['user_id' => $user->id],
]);
$user->update(['stripe_customer_id' => $stripeCustomer->id]);

$setupIntent = \Stripe\SetupIntent::create([
    'customer'               => $user->stripe_customer_id,
    'usage'                  => 'off_session',
    'automatic_payment_methods' => ['enabled' => true],
]);

return response()->json(['clientSecret' => $setupIntent->client_secret]);

Server — subsequent charges without user interaction

public function chargeRecurring(User $user, int $amountCents): void
{
    \Stripe\Stripe::setApiKey(config('services.stripe.secret'));

    $paymentMethod = $user->default_payment_method_id;

    try {
        $paymentIntent = \Stripe\PaymentIntent::create([
            'amount'               => $amountCents,
            'currency'             => 'usd',
            'customer'             => $user->stripe_customer_id,
            'payment_method'       => $paymentMethod,
            'confirm'              => true,
            'off_session'          => true,
            'description'          => "Subscription - {$user->id}",
        ]);

        if ($paymentIntent->status === 'succeeded') {
            $this->recordSuccessfulCharge($user, $paymentIntent);
        }
    } catch (\Stripe\Exception\CardException $e) {
        $this->handleFailedCharge($user, $e->getError()->decline_code);
    } catch (\Stripe\Exception\InvalidRequestException $e) {
        if ($e->getStripeCode() === 'authentication_required') {
            $this->sendAuthenticationEmail($user, $e->getError()->payment_intent->id);
        }
    }
}

Why do up to 30% of payments fail?

The main reasons: expired card, insufficient funds, bank fraud monitoring, technical errors. With manual handling, each failure is lost revenue. An automatic retry strategy (dunning) recovers most of these payments. For example, on our cloud service projects, after implementing dunning, the failure rate dropped from 25% to 8%.

Handling failed charges

Failures are normal for recurring payments. We apply dunning with exponential backoff: first retry after 1 day, second after 3 days, third after 7 days. If after three attempts the charge still fails, the subscription status changes to past_due, and the client receives an email to update their card. Additionally, a dunning process starts — a series of 3-5 reminders. Here is an example class:

class RecurringChargeJob implements ShouldQueue
{
    public int $tries = 3;

    public function backoff(): array
    {
        return [86400, 259200, 604800];
    }

    public function handle(): void
    {
        $subscription = Subscription::find($this->subscriptionId);

        if ($subscription->failed_attempts >= 3) {
            $subscription->update(['status' => 'past_due']);
            Mail::to($subscription->user)->send(new PaymentFailedMail($subscription));
            return;
        }

        try {
            app(RecurringPaymentService::class)->charge($subscription);
            $subscription->update([
                'failed_attempts' => 0,
                'status'          => 'active',
                'next_charge_at'  => now()->addMonth(),
            ]);
        } catch (PaymentFailedException $e) {
            $subscription->increment('failed_attempts');
            throw $e;
        }
    }
}

Stripe Billing — a ready-made solution

If you don't want to manage schedules yourself, Stripe Billing does it for you. Simply create a product and price, then a subscription. Webhooks handle all events: successful payments, failures, renewals. Stripe Billing is implemented 2x faster than custom tokenization and reduces server load.

\Stripe\Stripe::setApiKey(config('services.stripe.secret'));

$product = \Stripe\Product::create(['name' => 'Pro Plan']);
$price = \Stripe\Price::create([
    'unit_amount'  => 2900,
    'currency'     => 'usd',
    'recurring'    => ['interval' => 'month'],
    'product'      => $product->id,
]);

$subscription = \Stripe\Subscription::create([
    'customer' => $user->stripe_customer_id,
    'items'    => [['price' => $price->id]],
    'payment_behavior' => 'default_incomplete',
    'expand'   => ['latest_invoice.payment_intent'],
]);

The webhook handler should listen for invoice.payment_succeeded, invoice.payment_failed, and customer.subscription.updated events. Each event updates the subscription status in your local DB. It is important to handle duplicate notifications idempotently — check by Stripe Event ID. For testing, use Stripe CLI with stripe listen --forward-to localhost/webhook.

Which approach to choose: tokenization or Subscription API?

The choice between tokenization and Subscription API determines the level of control and development speed. Tokenization gives full control over scheduling and data but requires more code and testing. Subscription API simplifies subscription management by relying on the gateway but ties you to it and limits flexibility.

Comparison of tokenization and Subscription API

Get a consultation on choosing the right approach for your business.

What is included in the work

• Documentation: API specification of the integration, description of webhook events, subscription database schema.
• Access: environment setup (dev/staging/prod), creating gateway accounts, configuring webhook secrets.
• Training: knowledge transfer to your team, demonstration of the admin panel for subscription management.
• Support: 1 month warranty service after delivery, bug fixes via hotfix.

Process

1. Analysis — we study your business logic, charge frequency, and dunning requirements.
2. Design — we choose the stack (Stripe, CloudPayments), tokenization model or Subscription API.
3. Implementation — integrating the payment gateway, creating subscription tables, webhook handlers, jobs.
4. Testing — verifying payments, failures, grace periods, retry attempts.
5. Deployment and monitoring — setting up alerts, logging errors, updating documentation.

Contact us to discuss the details of your project.

Timelines and cost

Basic integration with one gateway takes from 3 to 6 weeks. If you need complex billing cycles, multiple gateways, or non-standard retry strategies, the timeline increases to 8–10 weeks. Cost is calculated individually.

Order a turnkey recurring payment integration — we guarantee reliability and transparency at every stage.

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.