Structured by design
Different card types ask for different fields. The workflow adapts to the selected card so users can see the relevant path without sorting through unrelated inputs.
About Veld Verify
Veld Verify exists to make card evaluation easier to understand. The interface guides each submission without presenting itself as an issuer, retailer, or official balance service.
Why it exists
Different card types ask for different fields. The workflow adapts to the selected card so users can see the relevant path without sorting through unrelated inputs.
The experience distinguishes an informational evaluation from an official issuer response. It does not promise a guaranteed balance, activation state, or redemption outcome.
The current build runs locally and is prepared for a future Supabase connection. Public data access remains locked until a real project and operating policy are configured.
Product principles
Language and results should explain what the system can determine without implying affiliation or certainty it does not have.
Stored validation records are designed around operational metadata. Full card codes, PINs, and CVV values are excluded from persistent records.
For authoritative balances, card status, disputes, or redemption help, users should contact the retailer or issuer through its official website or phone number.