This guide explains how to configure the 3-layer decision engine that controls when the SDK should call the external device identification provider.
When POST /api/devices is called, the engine evaluates 3 layers in order. The first layer that produces a definitive answer wins:
The Device Identification system determines whether a device registration event should trigger an external fingerprint analysis via FingerprintJS (FPJS). Every FPJS call has a cost, so the system is designed to minimize unnecessary calls through a multi-layered decision pipeline that evaluates rules, limits, and feature flags before committing to an external request.
The decision is made at the POST /api/devices endpoint (device registration) and returns a shouldIdentifyDevice: true|false flag to the mobile client, which then decides whether to call FPJS.
PR: h4b-dev/payments-backend#413 · Paquete:
PayWayInstallmentsv2.0.0 · Actualizado: Febrero 2026
Si tu integración ya procesa cargos con nuestra plataforma, solo necesitás incorporar dos llamadas para habilitar el programa de millas PayWay en tu checkout. No hay endpoints nuevos ni cambios en el flujo existente.
