How One Startup Uses Rate Limiting to Stop API Abuse

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

How One Startup Uses Rate Limiting to Stop API Abuse

Listen for free

View show details

In this episode, Lucas and Luna explore how a fintech startup called PayShield implemented rate limiting to prevent API abuse after a credential-stuffing attack compromised 2,000 accounts in one weekend. They break down the technical architecture — token bucket vs. sliding window, per-user vs. per-endpoint limits — and the business tradeoff: too aggressive and you block legitimate users, too loose and you invite fraud. PayShield's CTO shares how they reduced abuse by 95 percent while keeping false positives under 0.1 percent. Lucas and Luna discuss how this approach scales from a single Redis instance to a distributed cluster, and why rate limiting is a first-class feature, not an afterthought. #RateLimiting #APIAbuse #PayShield #TokenBucket #SlidingWindow #Redis #Fintech #Security #Engineering #Startup #TechnicalCoFounder #Fexingo #BusinessPodcast #SoftwareEngineering #AbusePrevention #DevOps #API #Scalability Keep every episode free: buymeacoffee.com/fexingo

No reviews yet