Skip to content
B4bit Docs

Devices

A device represents a point of sale (physical or virtual) within your merchant. Each device has its own credentials and configuration.

Automatic creation

Section titled “Automatic creation”

When you create a merchant, B4bit Pay automatically generates a device with the same name. This lets you start accepting payments immediately without additional configuration.

Multiple devices

Section titled “Multiple devices”

You can create as many devices as your operation requires: one device per register, per branch, per salesperson, per website. There is no technical limit.

Device credentials

Section titled “Device credentials”

Each device exposes two keys that you will find in the dashboard (Settings → Merchant → Devices):

  • API Key (X-Device-Id) — UUID4 that identifies the device to the REST API. Use it in the X-Device-Id header of every request.
  • Secret Key — hexadecimal key used exclusively to verify the HMAC-SHA256 signature of webhooks. Never expose it on the frontend or in logs.

Per-device configuration

Section titled “Per-device configuration”

Each device has its own configuration:

  • Default fiat currency (fiat_default): currency used for charging when the order does not specify another (MXN by default).
  • Notification URL (notification_url): endpoint on your server where B4bit Pay will send webhooks. It must be HTTPS and respond with HTTP 200 quickly.
  • Alias URL for the unique QR: customize the public payment URL of the device (see Unique QR).

User association

Section titled “User association”

You can associate operators and read-only administrators with specific devices. An operator assigned to “register 3” will only be able to request payments against that device, not against others.

Next steps

Section titled “Next steps”