Case study · checkout and payments

A headless checkout on VTEX

A high-volume headless checkout on VTEX, for an e-commerce operation that has transacted more than R$3 billion on the platform. My work was feature-level, and most of it sat on the customer-facing side: evolving the flow, guiding the customer through it, and evolving or adding the endpoints the flow needed.

Context

A headless checkout on VTEX. The storefront is built by the team, the cart and the order live in VTEX's orderForm and are reached through the Checkout API, and around that core sit the parts the platform owns: conversion flows, payments, orders and authentication for several merchants and storefronts.

That split puts a large part of the outcome in the front end. The cart's business rules belong to VTEX; how a customer is guided through them, what a screen says when something fails, and how many steps and how much noise stand between a full cart and a paid order are ours. In a checkout, that difference is revenue.

Problem

My responsibility

Evolving existing features and endpoints, creating new endpoints when the feature required it (following the architectural patterns already established by the team), consuming those APIs in the front end, and writing tests. Most of what I did lived on the customer-facing side: guiding the customer through the flow, removing steps and noise, and keeping the payment and authentication screens usable for everyone.

What I worked on

How I approached it

Before writing anything I read the other endpoints in the same service and followed their conventions (naming, error shape, validation) because consistency is what makes an API learnable. For changes to contracts, I treated existing consumers as constraints: extend rather than redefine, and keep the previous behaviour valid. Because the same change usually spans back end and front end, I worked on both sides of the contract instead of handing off a shape nobody had validated. And for anything touching money or order state, tests came before the change shipped.

Challenges

Decisions and trade-offs

Result

Features delivered on a revenue-critical path, most of them on the checkout's experience layer. The scale around it: over R$3 billion transacted on the platform.

What I learned