Features
Release Notes
Generation Source
Pick how cards are generated. Full options live in Card Profiles.
BIN mode uses your saved primary BIN.
Statistics & Supported Gateways
Default rules ship with Asheo and are always available. Custom rules are ones you add or import — they can be edited, exported and removed.
Basic Setup
Click 🌐 to use current tab's domain, 📋 to paste a URL/curl. Examples: api.stripe.com, /payments, .*stripe.*.
Card Fields
Map a card part to where this gateway puts it in the request. Example: Stripe uses card[number], card[cvc], card[exp_month]. Cardholder name comes from your saved identity.
Rules
Add only the rules you need. Keep it simple to start.
Required Fields
Request must contain these fields.
Update Request
One row per field. Use ${now}, ${rand(6)}, ${host} as the whole value to inject a live timestamp, random string, or request host.
Remove Fields
These fields will be removed before sending the request.
Advanced Settings
Tools
Results
No rule test yet.
Built-in encrypted gateways work for free. Add a custom-origin Adyen checkout here and Asheo real-proxies it through the Worker — swapping the card server-side and returning the live Adyen response.
Use saved BIN input.
BIN mode uses your saved BIN input.
Only your saved primary BIN is used.
BIN mode uses your primary saved BIN only.
Auth credentials
SOCKS auth not supported by Chrome. Incognito scope needs "Allow in incognito" enabled.
Saved locally on this device only. Card fields stay separate from the Identity Filler (billing/shipping details).
Saved locally on this device only. Auto-fills billing/shipping identity fields on Stripe (Address Element / Link) and most standard checkout forms. Card fields stay with the card filler.
Current build: —
Custom update feed
License & update checks send only a random install ID (not a fingerprint) and, if you enter one, your license key — never your cards, BINs, gateway URLs, or page data.
Advanced controlsFine-tune every runtime setting individually — for power users Optional
Gateway Engine v3
How Asheo reads & adjusts payment requests. On error, the engine leaves your request untouched and logs a plain-language note.
- No activity yet — the log fills in as payment requests are handled.
Runtime Safeguards
Core runtime controls for safe request handling and fail-open behavior.
Filler & Recovery
Card filler behavior and recovery flow controls for testing stability.
Visibility & Diagnostics
Tune logs, overlays, notifications, and runtime telemetry detail level.
Authoring + Diagnostics
Advanced rule authoring, simulation, conflict checks, and safe bulk operations.
Authoring Assist
Simulation & Validation
Recovery & Bulk Ops
Profile Vault
Encrypt sensitive card-profile fields with a passphrase.
Secure profile storage is locked.
Backup & Recovery
Export a backup before recovery actions, then restore safely when needed.
Backup Snapshot
RecommendedExport your current rules, profiles, and preferences. Import from trusted backup files only.
Reset Tools
Use With CareThese actions clear local data and cannot be undone. Export a backup first.
Recovery tip: export after major changes so rollback is quick and clean.
Interactive Tests
Fire feedback signals to confirm sounds and notifications work — nothing here changes live behavior.