Transactional MFA

Transaction Types

PAYOUT_WALLET: External outgoing transaction (sent to blockchain).
TRANSFER_WALLET: Internal outgoing transaction to an address (does not go to blockchain).
TRANSFER_PHONE: Internal outgoing transaction to a phone number (does not go to blockchain).

Currently, only transactional emails are operational.

❗️
The email must be verified

The transaction is verified by the anti-fraud service.
The parameter sendConfirmation: false indicates that no confirmation notification containing a verification code will be sent to the user.
If the transaction passes verification and does not require 2FA, it immediately transitions to the PROCESSINGstatus and continues processing normally.

Example Response:

 {
  "txId" : "c5e83ed6722b77424",
  "sequenceId" : "c5e83ed3-cf07-4b77424",
  "fee" : 0.00463,
  "internal" : false,
  "sendConfirmation" : false
}

👍
If the transaction is internal, it is created immediately with an APPROVED status

The transaction is sent to the anti-fraud service.
If the transaction requires confirmation via 2FA, the system sends a confirmation code to the user, and the transaction status changes toNEED_2FA.
Before sending the confirmation notification to the user, the transaction transitions to WAITING_APPROVE_2FA.
The parameter sendConfirmation: true indicates that a confirmation code will be sent to the user.
The user receives a confirmation code via email.
The user enters the received confirmation code into the appropriate field.

Example Response:

 {
  "txId" : "5edf6cbe260bf",
  "sequenceId" : "5edf6ed28cbe260bf",
  "fee" : 14.55058751,
  "internal" : false,
  "sendConfirmation" : true
}

❗️
The decision on whether a transaction requires 2FA is based on our internal regulations