No validation — or only local validation on a device — leaves your app open to patching and manipulation. Verifying receipts on our servers takes that surface away.
Anything stored on a phone can be edited on that phone. Patcher apps do exactly this for a living: they intercept the store response, hand your app a "purchase succeeded" that never happened, and walk away with the content.
IAPGUARD moves the decision off the device. Your app asks our servers whether a receipt is real, and our servers ask the store. Nothing in between is worth attacking, because nothing in between decides anything.
Purchase data keeps its shape. Users can't reach into an inventory file on their device and add what they never bought.
No dependency on the state of one phone. Corruption, a wiped install or a hand-set clock stops being your problem.
Patcher apps work by rewriting what's on the device. With IAPGUARD as the single source of truth, there's nothing there to rewrite.
Every transaction becomes globally unique and can only be assigned to one user, or to the group of users you decide on. Receipt sharing between accounts stops working.
We track the consumption state of every purchase. Once a consumable has been used it's gone for good, and nobody else can claim it afterwards.
Initial purchase and every renewal after it — verified server-side and kept current without asking the device.
The secure, current state of every subscription is available to you at any time. You never have to rely on information stored on a user's device, which may be compromised or simply stale.
We integrate with App Store notification servers, so renewals and cancellations reach you in real time — whether or not the user has your app open. Incoming events update that user's inventory without interruption.
Setting a device clock forward is the oldest way to extend a subscription for free. Reading the state from our servers instead of the device prevents that from happening.
Show an upcoming expiration or an outstanding billing issue inside your app, while the user can still fix it. Suggesting the action beats having a dissatisfied customer a month later.
We handle validation across platforms, so a purchase isn't tied to the handset it was made on. Users switch phones and reinstall apps constantly — with cross-platform authentication they can restore what they own without a support ticket.
The purchase flow stays exactly as it was — no extra tap, no extra screen, nothing to log into. Median wall time for a validation request, from the device to the App Store response and back, is 800 ms.
Requests are routed to the nearest of our globally distributed servers, so that number holds up wherever your players are. There is more on availability and server load in the FAQ.
Your dashboard records valid and blocked transactions from the first day.