VoidhashDocs
DocumentationAPI reference
Dashboard
Get started
Introduction
Quickstart
Setup
Setup overview
Create a project
Products and perks
Paywall locations
CLI
Paywall components
Components
Develop a component
Editor panels
Component definition
Publishing
Installing and capabilities
SDKs
Swift
Kotlin
React Native
Web
Store setup
Connect the App Store
Connect Google Play
Connect Stripe
Record payments from other sources
API libraries
Node.js
PHP
Rust
Go
Resources
MCP server
Ad measurement
Meta ads
Migrate in observer mode
Delete a person's data
Kotlin SDK
Kotlin quickstart
Display a paywall
Make and restore purchases
Check access
Identify customers
Evaluate feature flags
Capture analytics
Track screens
Development purchase mode
Errors

Development purchase mode

Test purchases and subscription lifecycle changes without Google Play setup.

Development purchase mode lets a debug build buy from a fake store while Voidhash processes the purchases for real. Use it to test your purchase flow, entitlement checks, and subscription lifecycle handling before you connect Google Play Console.

Everything the fake store creates is tagged as development: purchases, subscriptions, grants, and revenue events. Tagged records never appear in production customer state or revenue unless you explicitly ask for development data.

Enable it

Start in Studio. Create a product and attach its perks. Subscription products need a billing duration, because the duration controls their simulated renewal and expiry dates. You do not need to connect Google Play Console.

Then set the dev option when you configure the SDK.

App.kt
val voidhash = Voidhash.configure(
    context = this,
    publishableKey = "vh_pk_...",
    options = VoidhashOptions(dev = BuildConfig.DEBUG),
)

With the option on, a purchase shows a confirmation sheet instead of the Google Play sheet. The SDK waits briefly to simulate processing. Once the backend accepts the purchase, the SDK refreshes the person snapshot, so your entitlement checks see the new grant.

The option is only honored in a debug build. Release builds always use the real Play Billing adapter. Set dev = false if you want a debug build to use the real store.

Development purchases start from purchase(...) or a paywall like any other purchase, so they need the default owner mode. In observer mode they fail with READ_ONLY_PURCHASE_NOT_ALLOWED.

Fixed test prices

Development purchases use fixed USD prices, so you do not need store pricing to test.

ProductUSD price
Weekly subscription$4.99
Monthly subscription$9.99
Quarterly subscription$24.99
Six-month subscription$39.99
Annual subscription$49.99
Non-consumable$19.99
Consumable$4.99

Legacy subscriptions without a duration are simulated as monthly and return a warning.

Simulate lifecycle events

Open a person in Studio to move a development subscription through its lifecycle. You can renew, expire, revoke, or refund it, or place it into a three-day grace period. Each action is idempotent: applying it twice has the same effect as applying it once.

Test data stays easy to tell apart. Development badges mark every test row, and the dashboard's environment switcher next to the project name shows Development data on its own.

Project settings let you disable new development purchases. They also let you reset all development purchases, subscriptions, grants, transactions, and purchase-ledger records. A reset never touches production or sandbox data.

PreviousTrack screensNextErrors

On this page

Enable itFixed test pricesSimulate lifecycle events