The problem BaseStack solves

BaseStack

The Ultimate Payment Stack for Base – Transforming "Manual Push" into "Auto-Debit" for the Global-Local Economy.

Project Description
BaseStack is a recurring payment infrastructure designed to bridge the gap between local economies and global crypto payments. By leveraging the low fees of the Base network, we transform the friction of manual crypto transfers into a seamless "Auto-Debit" experience.

We empower merchants to price their services in local currency (e.g., IDRX) for domestic users while simultaneously accepting global stablecoins (USDC) from international users. All payments are settled automatically via a trustless Keeper network, creating a true "Set & Forget" subscription model onchain.

The Problem it solves

Most crypto payments are still stuck in the "Manual Push" era. If users want to subscribe to a newsletter, a community, or a SaaS product, they must remember the due date, log in to their wallet, and perform a manual transfer every single month. This creates high friction and "subscription fatigue." If they forget, the service is cut off.

In the Web2 world, this is solved by expensive intermediaries. Creators and merchants rely on payment gateways (like Stripe or PayPal) that charge high fees (2-5% + fixed costs) and impose strict geographic restrictions. For merchants in emerging markets (like Indonesia), accepting global payments often means losing significant value to FX fees or being rejected entirely due to lack of business entity registration.

Simultaneously, the "Global vs. Local" disconnect hinders adoption. Onchain payments are borderless, but pricing is not. A merchant wants to charge locals in their native currency (e.g., IDRX) and global users in stablecoins (e.g., USDC). Currently, no simple infrastructure exists on Base to handle this dual-currency subscription model automatically without complex manual management.

How BaseStack Solves This

BaseStack transforms the payment experience from "Manual Push" to a "Set & Forget" automated protocol.

Changing the Model to "Set & Forget"
BaseStack eliminates the need for users to be the admin of their own finances every month.

1. One-Time Approval: Users sign a single approval transaction at the start.

2. Automated Execution: Our Smart Contract & Keeper Bot work in the background to renew subscriptions precisely on the due date.

3. Result: Zero seconds wasted on service renewal. Users enjoy a Netflix-like experience onchain.

Bridging the "Glocal" (Global-Local) Gap
BaseStack introduces a smart multi-currency architecture that adapts to the user.

1. Context-Aware Pricing: Merchants can set a plan that accepts DRX from Indonesian IPs and USDC from the rest of the world.

2. Unified Revenue: Regardless of what currency the user pays with, the merchant receives the funds directly. This empowers local creators to monetize a global audience without banking barriers.

Transparent and Trustless Direct Payments
Unlike Web2 gateways that hold funds, BaseStack facilitates a direct Peer-to-Peer flow.

1. No Middlemen: Money flows 100% from User to Creator.

2. Safety & Control: The smart contract limits the maximum withdrawal amount per month. Merchants cannot withdraw more than agreed.

3. Easy Exit: Users can cancel anytime by revoking allowance onchain, ensuring no party can withhold their right to stop paying.

Challenges we ran into

Challenges We Ran Into

Fighting the Nature of Blockchain (Push vs. Pull) The biggest obstacle we encountered was the underlying architecture of Ethereum/Base, which is Push-Payment (User must actively send). We wanted to create a Pull-Payment experience, but Smart Contracts cannot auto-execute based on time.

How we solved it: We implemented a Keeper Network design pattern. We built a lightweight Off-chain Bot (using Node.js/TypeScript) that monitors the Smart Contract. This Bot acts as a trigger, calling the chargeSubscription() function only for users who have passed the grace period (block.timestamp > nextPayment). To ensure security, the Smart Contract logic immediately increments the payment due date upon success, causing any subsequent charge attempts to revert, thus protecting user funds.

Handling Transaction Failures Without Stopping the Bot During mass billing tests, we found a critical issue: When one user failed to pay (due to insufficient balance), our Bot would crash or the batch transaction would revert, stopping the billing process for all other users in the queue.

How we solved it: We changed the iteration logic on our Keeper Bot to use a Try-Catch mechanism per user. On the Smart Contract side, we added Error Handling that returns a bool success status instead of reverting the entire transaction block. If a user has insufficient balance, the system does not error; instead, it automatically changes the user's status to "Grace Period" and triggers a notification via Telegram so the user can top up.

UX Friction: The "Infinite Approval" Fear From a UX perspective, asking users to "Approve Unlimited Tokens" looks high-risk and scary for non-crypto natives. However, if users only approve the exact amount, the transaction fails the following month. We were trapped between Security vs. Convenience.

How we solved it: We utilized Coinbase Smart Wallet combined with UI transparency. In the frontend, we offer clear options: "Approve for 1 Year" or "Approve Forever." By using Coinbase Smart Wallet, the approval process feels like a standard app login (Passkey/Biometric) rather than a complex crypto operation. This lowers the mental barrier while keeping the user informed about exactly what permissions they are granting.