redpill Payments Platform

In September 2024, I was tasked with creating a bespoke client portal for redpill - a brand marketing agency based in London. Our goal was to create a middle-man between the main redpill website and the third-party service that they used for client payments. Although this was possible before by using their payment provider's own website, we wanted to keep it all under one roof and also implement redpill's brand identity.

The payment provider had the ability to embed an iframe into a webpage which contained customer payment details, invoices and payment history. To achieve this, I create a simple SPA React app with authentication via AWS Cognito.

Backend wise, I created a simple API using AWS API Gateway which I used for generating a hash key needed to authenticate the active user with the iframe element. It also had a Webhook listener endpoint to listen out for new users - the redpill team would create a new user in the third-party service, the user data would be sent to the Webhook listener and the user's details would be created / updated in AWS Cognito. It also sent an email invite for the redpill client portal to the user via AWS SES, and likewise we customised the email template to align with the redpill brand.

I chose to deploy the app using AWS Amplify. Looking back, I don't think this was the right call since it was a bit overkill for our use case - the app didn't use SSR so we could've simply deployed a static site to an S3 bucket or used a free service like Netlify. Also it was quite finicky to customise the CSS of the stock Amplify login React form. Since working on this project, I have gained a lot more confidence with CI / CD, but at the time it seemed like a straightforward enough solution.

In February 2026, redpill restructured the services they offer which means that the redpill Payments Platform is no longer needed, but during its course it had 60+ of their clients actively using it.