Browser Fingerprinting
Uses userAgent, screen size, language & SHA-256 hashing for a device binding identifier.
Verify your users securely using Device & Browser Binding Fingerprinting — without sending costly SMS.
Uses userAgent, screen size, language & SHA-256 hashing for a device binding identifier.
Helps ensure users access the system from their registered device and browser session.
API Key authentication with CORS support for controlled integrations.
Reliable database storage for clients, credits, bindings and verification logs.
No telecom SMS charge is required by the device-binding workflow.
BDOTPFire.verifyDevice({ phone }) on button click.<script
src="https://your-worker.workers.dev/bd-otp-fire.js"
data-api-key="YOUR_PUBLIC_CLIENT_KEY"
data-endpoint="https://your-worker.workers.dev/v1/verify"
></script>
<script>
BDOTPFire.verifyDevice({
phone: "+8801XXXXXXXXX"
}).then(console.log)
.catch(console.error);
</script>A lightweight integration layer for modern websites that need fast, device-bound verification.
Submit a phone number and SHA-256 device identifier.
Receive verification status and the client's remaining credits.
Keep privileged database credentials on the Worker only.
Build and test your integration before expanding verification capacity.
Use the SDK, connect your Worker endpoint, and start building with BD OTP Fire.