Bliss AbhademereProduct engineerLet’s talk
← The CredPal work03 / CREDPAL · CONTRIBUTION

A plan becomes a purchase.

Connect a purchase with the product it unlocks.

Where this work fits

Opening checkout does not mean a customer has paid. Confirmation arrives separately, and a subscription can later renew, fail, expire, or be cancelled. Each change needs to leave the account with the right access.

MY CONTRIBUTION

I integrated payment checkout with account and subscription records. Keeping a purchase attempt connected to its later payment updates helped the product distinguish starting checkout from actually earning access.

THE IDEA, ILLUSTRATED

Connect a purchase with its confirmation

A TRANSACTION STARTS WITH A SHARED REFERENCE
9:41•••
MEMBERSHIP

A little structure.
A healthier week.

PREMIUMYour personal plan

Meal planning
Nutritionist guidance
A calendar that’s yours

Choose a plan

APPLICATION RECORDNot created yetA reference will connect both sidesAccess remains closed
A purchase starts with a plan and a payment reference.
THE ENGINEERING DECISION

Different purchase channels, consistent access.

A card-payment event and an in-app purchase receipt arrive differently and require their own checks. I used signature and receipt verification before updating account access, then handled the subscription states beyond the initial purchase.

The skills behind the work

Payment APIs
Connect purchase attempts and payment-service updates with application records.
Data modeling
Give different product concepts clear records and relationships so updates have predictable meaning.
TypeORM
Work with relational records through typed queries and repository operations.
THE WIDER RESULT

The billing work supported subscription growth and improved transaction success. Customers could move from a verified purchase into the membership features, with access tied to the subscription lifecycle.

Transaction success rate
+40%Improvement following card-payment and transaction-management integrations.
READ THIS IN CONTEXTI connected payment updates to the customer’s subscription. →
Related contributionsPayment events become product accessI implemented payment-event verification and handling for subscription changes. Different updates have different consequences, so the work connected trustworthy payment signals with the appropriate account behavior.An iOS receipt joins the same access modelI connected server-side purchase-receipt verification with subscription access. The work helped another purchase channel fit into the account experience without treating an unverified client claim as a completed purchase.Access follows the subscription clockI connected membership state with access to protected product features and worked on lifecycle maintenance. The backend needed to enforce what an account could use as trials and paid periods changed.