Withdrawals using FIO Address

This is the most basic integration option and fits within existing withdrawal screens. It allows the user to use their FIO Address (in another wallet or exchange) as their withdrawal address.

• User

  • Users enters FIO Address as their withdrawal address for any crypto.

  • User does not need to register a FIO Address inside the exchange for this integration.

• Exchange

  • Fetch public address using /get_pub_address.

  • Rest of flow unchanged.

Example

Deposits using FIO Request

With this option the the user will trigger a FIO Request from a deposit area of the exchange to their wallet using a FIO Address

• User

  • User picks FIO Request as an option to make deposit of any crypto.

  • User enters:

    • Their FIO Address

    • Amount

    • Memo (optional)

• Exchange

  • Sends FIO Request using /new_funds_request with

    • From FIO Address

      • DECISION 1

        • A. Generic FIO Address, e.g. deposits@greatexchange OR

          • For this option User does not need to register a FIO Address inside the exchange.

        • B. User-registered FIO Address, e.g. bob@greatexchange

  • Public address, where funds to be sent for deposit

    • This address can include attached blockchain specific tags or memos, e.g. Destination Tags for Ripple

  • Memo (optional)

• User

  • User approves request in their wallet and a native blockchain transaction is executed

  • A FIO Data transaction is automatically sent to the FIO Chain and it includes native blockchain transaction ID.

• Exchange

  • Sees the native transaction and credits the user

  • Can also fetch the FIO Data transaction using /get_obt_data

Example

FIO Address Registration

Each user will need a FIO Address on an exchange domain if you want to enable:

• Deposit using FIO Request with request coming from user-registered FIO Address, e.g. bob@greatexchange

• Deposits using FIO Address

• Withdrawal using FIO Request

DECISION 2

• A. Exchange controls the UX

  • User

    • Picks a FIO Address

      • DECISION 3

        • A. Address registration part of on-boarding OR

          • DECISION 4

          • A. A FIO Address can automatically be assigned when a user creates an exchange account OR

          • B. You may use a value already being collected, e.g. user_name@greatexchange, or

        • B. Address registration as an option

          • Any user may choose to register a FIO Address when they want to access the FIO features.

  • Exchange

    • Foundation-paid FIO Addresses

      • Register FIO Address on chain using /register_fio_address

        • DECISION 5

          • A. You want to keep the domain private. Only the exchange can register FIO Addresses on that domain.

          • Exchange will have to transfer domain ownership to Foundation

          • B. The domain can be public

          • Custom permission set-up will be required.

    • Exchange-paid FO Addresses

      • Register FIO Address on chain using /register_fio_address

        • Register FIO Address on chain using /register_fio_address

• B. Exchange links user off to registration site

  • FIO Addresses registered to a FIO Public Key can be obtained for display using /get_fio_addresses

Example

Deposits using FIO Address

With this option, the user can make a deposit to their exchange without ever logging into it, by simply sending crypto the their FIO Address, e.g. to bob@greatexchange

• User

  • DECISION 6

    • A. User explicitly decided which crypto currencies are mapped to their FIO Address

    • B. The exchange automatically maps all supported crypto currencies to the FIO Address

• Exchange

  • Maps public addresses using /add_pub_address and FIP-15 Standard

Example

Withdrawal using FIO Request

With this option, the user can send a FIO Request from their wallet to their exchange FIO Address e.g. bob@greatexchange

• User

  • Send a FIO Request to their exchange FIO Address e.g. bob@greatexchange with

    • Chain code

    • Token code

    • Withdrawal address

    • Memo (optional)

• Exchange

  • Receives the FIO Request

  • Authenticates the user

    • DECISION 7

      • A. User has to log-in and approve request.

      • B. User approves request by clicking on email.

      • C. User whitelists their FIO Address and withdrawal address and FIO Request is automatically approved when received.

More examples

https://kb.fioprotocol.io/user-guides/user-guides

Tech docs