Skip to main content

Introduction to Two-Factor Authentication

In this type of scheduling, it is necessary to confirm the payment programming via token sent to the person with powers to approve account movements in the crediting account.

The TED scheduling request by integrating partners configured to use two-factor authentication is performed similarly to what is described in request TED transaction scheduling. The difference occurs in the addition of the tfa_info object, containing information about the transfer approver and the contact method, and the status of a successful request which will always be pending_2fa_approval.

The same applies to TED batch scheduling described in request TED transaction scheduling in batch.

Flow for a TED scheduling with authorization​

The successful TED scheduling will follow the following process flow:

  1. Execution of the TED transaction request and receiving a synchronous response with pending_2fa_approval status and schedule_key value.
  2. The indicated approver will receive a 6-digit token composed of numbers.
  3. The requester performs the TED transaction confirmation with the schedule_key and the token.
  4. The scheduling will then be updated to scheduled status.

Observations​

  • Each scheduling has a maximum limit of 5 token validation attempts. When this limit is reached, the scheduling will be automatically set to rejected status (rejected).
  • Each token has a maximum duration of 5 minutes.
  • A scheduling can have its token renewed and resent to the transfer approver. This process restarts the 5-minute timer and does not restart the invalid attempts counter. The previous token becomes invalid.
  • The notification event for sending the token to the approver is baas.token_validation.ted.schedule.single. It is possible to customize the message sent.
  • The implemented token sending methods (contact_type) are by sms and email.