API changes on Elysium

The Elysium backend exposes the same API as production, with these additions. After a withdrawal on Elysium, the client records it through the transaction API so it can appear in history.

Record a withdrawal

POST /transaction · Requires auth Same endpoint as a normal send, with transactionType: "WITHDRAW". receiverAddress is any outside address; it doesn’t have to belong to a Numpay user.

string

required

Elysium transaction hash (66 characters).

string

required

The caller’s own Numpay smart-account address.

string

required

The outside destination address.

number

required

Decimal USDC.

string

required

WITHDRAW.

string

required

COMPLETED.

Server checks

Check	Failure
`senderAddress` belongs to a Numpay user	`404 Sender user not found`
That user is the caller (token phone or email)	`403 You can only record withdrawals from your own wallet`
Receipt exists on Elysium	`400 Withdrawal not recorded: transaction not found on Elysium`
Receipt status is `success`	`400 Withdrawal not recorded: transaction failed on-chain`
A USDC `Transfer` log matches sender, destination and exact amount	`400 Withdrawal not recorded: no matching USDC transfer in this transaction`

Response 201

{
  "id": "e41c…",
  "txhash": "0x51d0…9b7e",
  "transactionType": "WITHDRAW",
  "senderId": "4f0c…9e11",
  "receiverId": null,
  "counterparty": "0x2F1b…c0De",
  "amount": 5,
  "transactionStatus": "COMPLETED",
  "createdAt": "2026-11-05T12:30:11.000Z"
}

History

GET /transaction/user/{userId}?type=withdrawal Returns the user’s WITHDRAW rows. With no type, withdrawals are included alongside sends, receives and deposits. A withdrawal has receiver: null; the destination is in counterparty.

Not available on Elysium

/near/* deposit endpoints aren’t part of the Elysium build; funds arrive as test USDC sent directly to the user’s address.

​Record a withdrawal

​History

​Not available on Elysium

Record a withdrawal

History

Not available on Elysium