Harshit VarshneyBackend & DevOps
000Loading
Harshit.
← All work
NFC product2024Backend and infrastructure

Easetap

Backend for an NFC smart-card platform: card provisioning, tap analytics, and campaign messaging through AWS Pinpoint.

+25%

User engagement after Pinpoint campaigns

99.95%

Uptime on the shared platform infrastructure

The problem

A tap has to resolve to the right profile in the time it takes someone to hold a card against a phone. Every card also needs provisioning, revocation, and a record of where it has been tapped, without a person in the loop.

What I built

  • Provisioning service that mints card identities and binds them to a profile, with revocation handled as a first-class state rather than a delete.
  • Tap ingestion endpoint that writes the event and returns the profile in one round trip, so the card feels instant.
  • Campaign messaging through AWS Pinpoint, triggered off tap activity instead of manual sends.
  • Containerised deploys behind Nginx, with the same image promoted from staging to production.

How it is wired

Easetap, as deployedSimplified. Every box is something I either built or operate.
DEPLOYMETRICSNFC TAPcard or phoneCLOUDFLAREDNS, TLS, cacheNGINXreverse proxyNODE.JS APIDocker on AWSMYSQLprofiles, tapsS3media, assetsAWS PINPOINTcampaignsCI/CDbuild, test, shipCLOUDWATCHlogs, alarms

What it moved

  • Engagement rose about 25% once messaging was driven by tap behaviour.
  • Card issuance moved from a manual step to a self-serve API call.

Stack

  • Node.js
  • Express
  • MySQL
  • AWS Pinpoint
  • Docker
  • Nginx