On This Page
FILTER BY TAG

Device Binding Workflow with Step-Up Authentication

Device Binding Step-Up Workflow

Figure:

Bind a Device with Step-Up Authentication
  1. The customer sends a request to the merchant that they consent to bind the device.
  2. If the device is not enrolled, the merchant sends a request to
    TMS
    TMS
     to enroll the device.
    1. Test:
      POST
      https://apitest.cybersource.com
      /tms/v2/devices
  3. If the device is enrolled, the merchant sends a request to
    TMS
     to bind the device using the device ID.
    1. Test:
      POST
      https://apitest.cybersource.com
      /tms/v2/tokenized-cards/{id}/bindings
  4. TMS
     sends a binding request to the issuer with the binding ID.
  5. The issuer sends a response to
    TMS
     with a step-up authentication binding status.
  6. TMS
     sends a request to the issuer for authentication methods.
  7. The issuer sends a list of authentication methods that are passed on to the customer.
  8. The customer selects their authentication method and it is sent to the issuer.
  9. The issuer initiates authentication method.
  10. If authentication is valid,
    TMS
     binds the token to the device.
  11. The issuer notifies
    TMS
     that binding was successful.
  12. TMS
     sends a response to the merchant that the binding is completed.
  13. The merchant notifies the customer that their device binding is complete.

Step-Up Authentication Flow

This workflow shows the possible options for step-up authentication after you send a request to
/tokenized-cards/{id}/bindings
:

Figure:

Bind a Device with Step-Up Authentication
RELATED TO THIS PAGE