WARP

WARP guide

On-Net Transfers and Port-Out PINs

How on-net transfers work, how transfer PINs differ from carrier port-ins, and how to protect numbers with a port-out PIN.

An on-net transfer moves a number from one WARP customer account to another WARP customer account. It is different from an industry port-in. There is no losing outside carrier, no Letter of Authorization, and no Firm Order Commitment date. The security control is a per-number transfer PIN from the current holder.

Use an on-net transfer only when the number is already on WARP under another customer account. If the number is with another carrier, use the port-in wizard instead.

How an On-Net Transfer Works

The current holder of the number sets or shares the transfer PIN for that number. The receiving customer enters the number and PIN in the transfer workflow. WARP checks that the number is transferable and that the PIN is valid. If the check passes, the transfer moves the number to the receiving account.

Because both sides are already on WARP, the transfer can complete without carrier review. You still need to coordinate timing with the current holder, because moving the number may affect their routing, messaging, billing, and users.

Before You Transfer

Confirm these details before starting:

  • The number is already on WARP under another customer account.
  • The current holder intentionally wants to transfer the number.
  • You have the correct transfer PIN.
  • You know how the number should be routed after it lands in your account.
  • If the number carries SMS, you know which campaign it should use after transfer.

Do not start an on-net transfer if you are unsure who controls the number. Ask the current holder or support to confirm ownership.

Transfer PINs and Port-Out PINs

The same customer-facing control protects numbers from unauthorized movement. A port-out PIN is set on the number by its current holder. Someone attempting to move the number must know the correct PIN.

Set a PIN on important numbers before sharing them externally or preparing a transfer. Treat the PIN like a password. Share it only with authorized people and only for the time needed to complete the transfer.

WARP protects against guessing. After 10 failed PIN attempts, the transfer path locks out for 15 minutes before more attempts are allowed.

After the Transfer

Once a number lands in your account, review it like any newly acquired number:

  1. Confirm the number appears in your Numbers list.
  2. Configure voice routing to the correct trunk.
  3. Confirm E911 and CNAM settings if the number is used for voice.
  4. Confirm SMS enablement and campaign assignment if the number is used for messaging.
  5. Place a test call and, if applicable, send a test message.

An on-net transfer moves the number. It does not automatically recreate every business rule you may want on the receiving account.

Scopes and API Reference

The transfer workflow uses porting scopes:

  • porting:read for transfer preview.
  • porting:write for executing the transfer, with step-up verification.

Endpoints:

  • POST /v1/porting/transfer/preview
  • POST /v1/porting/transfer

Port-out PIN management uses number scopes:

  • numbers:read to check whether a PIN is set.
  • numbers:write to set or clear a PIN, with step-up verification.

Endpoints:

  • GET /v1/numbers/:tn/port-out-pin
  • PUT /v1/numbers/:tn/port-out-pin
  • DELETE /v1/numbers/:tn/port-out-pin