Update Customer Phone Number

Migrates a customer’s identity to a new phone number while preserving their exact SCW address, on-chain USDC balance, and full transaction history. Use when a customer loses their SIM or changes their number. Only the phone lookup index is updated — the wallet address is immutable.

POST /v1/users/update-phone

Update Customer Phone Number

cURL

curl --request POST \
  --url https://api.rach.finance/caas/api/v1/users/update-phone \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "new_phone_number": "<string>",
  "old_phone_number": "<string>"
}
'

200

{
  "blind_index": "<string>",
  "created_at": "<string>",
  "status": "PROVISIONED",
  "wallet_address": "<string>"
}

Authorizations

X-API-Key · string · header · required

Your Rach B2B API key. Use rach_sk_live_* for production (on-chain) or rach_sk_test_* for sandbox (no-chain simulation).

Body

application/json

Phone Update Payload

new_phone_number · string · required

old_phone_number · string · required

Response

200

application/json

OK

blind_index · string

created_at · string

status · string

Status is one of: PROVISIONED (new wallet), ADOPTED (took over an unaffiliated wallet), ALREADY_EXISTS (you are already a member), or LINK_REQUIRED (wallet belongs to another merchant — start the consent link flow at POST /v1/users/link/request to gain operating rights).

Example:

"PROVISIONED"

wallet_address · string