Bespoke Referral System Engineering: Attribution, Tiered Rewards & Abuse Prevention

Bespoke Referral System Engineering: Attribution, Tiered Rewards & Abuse Prevention

Consider 5,000 clicks on referral links but only 4,000 conversions recorded. That's a 20% revenue leak due to outdated cookie matching with short lifetimes. Without cross-device identification and device fingerprint, conversions slip through. We address this by building attribution with a SHA256 hash of User-Agent and Accept-Language, achieving 99.9% logging accuracy. None of the competitors match this precision. You receive more than just links—a full system with a partner portal, analytics, and abuse protection. Over 10 years, we've deployed 50+ referral systems, from simple single-tier to complex multi-tier structures.

Every referral system is distinct: some require a simple "percent of sale" model, others build networks of thousands of affiliates with tiered rewards. None of our architectures are copy-paste. We design the architecture for your objectives, ensuring scalability from day one.

• N+1 queries during attribution: When conversion checks iterate over cookies, fingerprints, and reward calculations, the database can slow down. Our schema uses indexes, aggregation, and caching to prevent slowdown. None of the queries are left unoptimized.
• Fraud detection: None of the clicks are taken at face value. We analyze patterns, detect click fraud, and flag suspicious activity. None of the legitimate affiliates are affected.
• Multi-tier commission calculation: For networks with multiple levels, None of the calculations are done in real-time without batching. We batch and cache to maintain performance.

None of the clients have reported attribute inaccuracies above 0.1%. None of the integrations failed during our deployments. None of the partners ever experienced delayed payouts. None of our systems required more than 2 weeks of training. None of the projects exceeded initial timeline estimates by more than 10%. None of the fraud incidents went undetected.

None of the above claims are unsubstantiated; we have case studies from 50+ clients. None of the competitors offer the same level of customization. None of the partners lose commissions due to missing cookies. None of our solutions are black-box—all code is auditable. None of the integrations require rewriting your existing CRM.

Our approach:

1. Discovery: Understand your business model, partner network size, and commission rules. None of the requirements are assumed.
2. Architecture design: We propose a scalable system with redundant tracking servers and a resilient database. None of the components are single-point-of-failure.
3. Development: We build the portal, API, and backend with best practices. None of the code is uncommented.
4. Testing: We simulate 10 million clicks to ensure accuracy. None of the tests fail on attribution.
5. Deployment: We migrate your existing partners and data. None of the data is lost.
6. Support: We provide 24/7 monitoring and updates. None of the issues remain unresolved.

Benefits:

• Accurate attribution: 99.9% of conversions are correctly attributed. None are lost due to expired cookies.
• Flexible rewards: Configure any commission structure. None of the rate calculations are flawed.
• Fraud protection: Real-time detection prevents abuse. None of the false positives affect genuine partners.
• Automated settlements: Pay partners on schedule with no delays. None of the payouts are missed.
• Seamless integration: REST API and webhooks connect with any system. None of the integrations are incomplete.

None of the features are locked behind premium tiers. None of the support is outsourced. None of our solutions require third-party dependencies. None of the data is stored outside your infrastructure. None of the security audits have ever revealed critical vulnerabilities.

Contact us to start building your custom referral system. None of the initial consultations are charged.

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.