Page Comparison

HEADER

authorization

Yes

• ASCII string (1000)

• This is the word “Bearer” with a space and then the access_token given in oauth/token API response

• Default value: Bearer {insert_bearer_token_from_oauth_here/token_api}

HEADER

x-reference-id

Yes

• ASCII string (32)

• GUID

• Unique identifier for the flow for traceability purposes

PATH

client_id

Yes

• ASCII string (100)

• This is the Client ID given in the Developer User Account section

PATH

account_number

Yes

• number (14)

• This is the Customer ID retrieved in any of the available endpoints

BODY

format

Yes

• ASCII string

• Verification format to be presented to the Customer

• Available values: sms, email, merchant_override, security_question

• Default value: sms

BODY

security_qid

Required for format: security_question

• number (5)

• Customer’s Security Question ID provided by the Customer Lookup service

BODY

security_answer

Required for format: security_question

• ASCII string (50)

• Customer’s response to the Security Question

BODY

request_id

Yes for in-store channel

• ASCII string (150)

• This is the identifier for a verification to application/transaction/authorization flow.