Spending Authorization (Allowance) API
Last updated
Last updated
This transaction is only available for ERC-20s and interfaces that extend ERC-20 such as ERC-1404. It is also available on all supported EVM chains that have equivalent interfaces such as Avalanche, Polygon, Binance Smart Chain, etc.
The allowance itself does not spend funds like a transfer does, however, there is still a fee associated. So before the tx takes place, you should estimate the fee & check the balance of the native currency on the blockchain of the currency you are authorizing someone else to spend. For example, if you would like to authorize your spouses wallet to spend 100 USDC on Ethereum from your wallet you need to pay the fee for that authorization in ETH.
This is the transaction that actually authorizes the spending amount. As with other transactions, you should prepare the seed phrase for transport and provide details about the authorized spender address and the currency/amount that address is authorized to spend on your behalf.
Asset symbol
ETH
The nature of the transaction on which a fee should be estimated for. By default TRANSFER_TX is used
TRANSFER_TX
Available options: Optional value only used when dealing with non native assets (aka tokens), it can be ERC_20, BEP_20, ALGO_STANDARD, ALGO_APP. If native asset, keep the field empty
ERC_20
Available options: Origin or spender address
0x6127DCB35b4625C2559526EEc22300c2Df804B5c
Recipient address
0x7cBc2e807d0191c5b9EA332CCec2423f8d72D626
Transfer or allowance amount
100
Fee estimate value was returned successfully
Asset valid address
0x9bf4001d307dfd62b26a2f1307ee0c0307632d59
Asset symbol, for instance: USDT, ETH, ALGO, etc, ...
USDT
Optional value only used when dealing with non native assets (aka tokens), it can be ERC_20, BEP_20, ALGO_STANDARD, ALGO_APP. If native asset, keep the field empty
ERC_20
Available options: Optional value only used when querying non native assets(tokens), it can be ERC_20, BEP_20, ALGO_STANDARD. If native asset, keep the field empty
ERC_20
Message retrieved from the backend
717ea458b62a430cb37ced7c22ebec97
e3421d7f9d6888ea83bef6b28ce0a2ab6eb6fe8a8fbfa3743240992590816b08f9a62edcc63296d056c552054d583fec36d23ef11dffb24c95aaf4a47d50dccc
Signature generated after signing the provided data field
0xb44e88ff3c67de6e6548a6caf006bf6e1cb841119d0b9ea1b7e9b2d36a5e0ed42fd9f5e543243d1d73dc4b7800cc2026f74961f4edc769699678a316abb34e661c
The owner's address
0x44Fa139F39D97b000cfAB1266ce8154782Bcef9D
The spender's address
0x44Fa139F39D97b000cfAB1266ce8154782Bcef9D
The amount the owner wishes to allow the spender to spend
10
The asset ID for which you wish to specify an alloance
ed378076-80c0-43ed-9914-5988e1abd748
The asset contract address
0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48
Transaction reference
a4dedb83-4d59-41ca-84b5-4b24a98878d8
Transaction memo or note
Allowance for buying NOTE
Seed encrypted asymmetrically by current user corresponding wallaby auth public key, to be decrypted inside the secure code execution environment
{"iv":"b7b643ebccf35c262aa2d5c2729c5f3d","ephemPublicKey":"040cff71ed16f1105c45c2214c9e72d3eabde48efe3759c6f150352b19aa8054c302dc1fd8b4f3927bd7d74ae0186854b3a13de7673be4f8424a6ba3702c239729","ciphertext":"736bc1881a02fa08df4a3f1e35d426660e3c35471facba2866e960f8a19b783bac30d037b07dc9e6406e258d09a4a7e4a7cf58d20cf7b8b7201db0f80849a48d20389039e3fc196f42796fe6d501f47afb030f9946ecbc148d8da1e46c3793a4","mac":"b6cbbdbbc3a311d919340fc3ec9ee1911d9ead6d989efa73e0ac3303c51a353e"}
Allowance has been created successfully