Two-device approvals (channels)

Use channels when one device drives the UI and another device approves.

Use channels when one device drives the UI and a second device approves.

Typical cases:

• Checkout terminals.

• NFC-only passkeys (approve on a phone).

Channel setup

Create a channel

Create a channel on the “driver” device. Then show url as a QR code or deep link.

Create a channel

import { RevibaseProvider } from "@revibase/lite";

const provider = new RevibaseProvider();
const { channelId, url } = await provider.createChannel();
// Show `url` as a QR code or deep link.

Use the channel

Pass channelId to signIn and any follow-up calls.

Sign in / transact via channel

import { signIn, transferTokens } from "@revibase/lite";

const { user } = await signIn(provider, { channelId });

const { txSig } = await transferTokens(
  provider,
  { amount: 1_000_000n, destination: "DESTINATION_WALLET_ADDRESS", signer: user },
  { channelId },
);

Track status

Subscribe to channel status changes. Use this to drive UX (waiting screen, reconnect button, etc).

subscribeToChannelStatus

import { ChannelStatus } from "@revibase/lite";

provider.subscribeToChannelStatus((id, entry) => {
  switch (entry.status) {
    case ChannelStatus.AWAITING_RECIPIENT:
      break;
    case ChannelStatus.RECIPIENT_CONNECTED:
      break;
    case ChannelStatus.CONNECTION_LOST:
      break; // call provider.reconnectChannel(id)
    case ChannelStatus.CHANNEL_CLOSED:
      break;
  }
});

Reconnect / close

provider.reconnectChannel(channelId);
await provider.closeChannel(channelId);

Close channels when you’re done. Treat channelId like a short-lived session identifier.