I tried Google Wallet's new allowance feature, and my kid's already ditched their debit card

Google Wallet introduces a virtual allowance model that ties a child’s balance directly to a parent-controlled profile rather than a standalone card. The backend must maintain a linked ledger that can be frozen on demand, and it pushes transaction events to the parent’s device for immediate visibility. This shift removes the card-issuance workflow but adds a dependency on NFC-enabled hardware for any spend.

From an integration standpoint, the service requires the child to be under 18 and enrolled in Family Link, meaning developers must call the Family Link API to verify eligibility before provisioning a balance. The provisioning flow also checks that the child’s device supports NFC and has the Wallet app installed, which adds a hardware capability check to the onboarding process. No separate account number is generated, so existing card-number handling logic is bypassed.

Operationally, the allowance can only be used at merchants that accept tap-to-pay, excluding many large retailers that still rely on magnetic stripe or chip-and-pin. This limitation means any point-of-sale integration that expects fallback payment methods must gracefully reject the transaction rather than attempting a fallback. Additionally, the service does not support online checkout, so any e-commerce platform cannot accept this payment method for child accounts.

The real-time lock feature demonstrated in the test, where a purchase attempted seconds after a lock was placed was declined, shows that the backend can enforce balance freezes instantly. Engineers building monitoring or fraud-prevention tools can rely on these immediate state changes, but they must also handle the edge case where a lock is issued while a transaction is already in flight, ensuring consistency across distributed components. Logging and audit trails will need to capture both the lock event and the rejected transaction for compliance.

Overall, adopting the allowance feature requires minimal changes to existing payment flows for in-store NFC transactions but adds new verification steps and a reliance on Google’s Family Link ecosystem. Systems that previously managed separate prepaid cards can retire card-related provisioning code, yet they must accommodate the narrower merchant coverage and the inability to process online orders for child accounts.