DCB 3.0 to IFC Migration Flow

DCB 3.0 to IFC Migration Flow

Overview

The purpose of the Migration flow is to support existing DCB 3.0 users on the IFC API specification. The input to this flow will be the Operator User Token (OUT) that identifies the user in the DCB 3.0 specification. The flow will result in the association with the user's carrier account of a Google Payment Token (GPT) that identifies the user in the IFC specification.

The authenticateWithToken method will be used to link an existing OUT to an authenticationRequestID. This authenticationRequestID will then be used as an input to the associateAccount method.

How the flow works

This flow is meant to exchange an OUT for a GPT without user involvement. A mapping of OUTs to carrier accounts is a prerequisite to this flow.

Migration Flow

DCB 3.0 to IFC Migration Flow

Here is a list of objects in the diagram and what they represent:

  • Google Server: The backend server at Google that facilitates the migration of an OUT with an Authentication Request ID and receives the authentication result from the integrator.
  • Payment Integrator Server: The backend server of the integrator that receives the authentication request, returns the Authentication result to Google, and handles the Associate Account request.
  1. Google begins the migration flow by calling authenticateWithToken with an existing OUT and a new Authentication Request ID.
  2. The Authentication Request is validated by the Payment Integrator Server, which responds SUCCESS indicating the OUT was recognized and the Authentication Request ID has been saved.
  3. The Google Server validates the authentication response and calls Associate Account with the Authentication Request ID and a new GPT.
  4. The Payment Integrator Server associates the GPT to the user's account with the carrier and responds SUCCESS with the required account association information. After this point, the GPT may be used for purchase flows.

Migration Flow - Authentication Failed

DCB 3.0 to IFC Migration Flow Failure

  1. Google begins the migration flow by calling authenticateWithToken with an existing OUT and a new Authentication Request ID.
  2. The Authentication Request is validated by the Payment Integrator Server, which responds AUTHENTICATION_FAILURE indicating the OUT was not recognized.