Menu

One merchant account, four side projects: how I keep the payment data from turning into a mess
📰

One merchant account, four side projects: how I keep the payment data from turning into a mess

DEV Community: api·Buhgalter·18 days ago
#dcpMfF7k
#devtoapi#devto#dev#project#store_id
Reading 0:00
15s threshold

Most indie developers I know do not run one product. They run a VPN bot, a paid Discord or Telegram community, a small template shop and maybe a script nobody remembers launching. Each of them takes money. Sooner or later someone asks a very boring question: how much did the template shop actually make in September, after refunds?

If all four projects share one payment account and one webhook handler, that question can eat an evening. This post is about structuring things so it takes a minute instead. I will use the Buhgalter payment API as the concrete example, because it has a notion of storefronts built in, but the design ideas apply to most providers.

Storefronts instead of string prefixes

The tempting shortcut is to put the project name into the order reference: vpn-10231 , shop-554 .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.