American Express OptBlue® Program Registration Scenarios
You will need to register a merchant for the American Express OptBlue® program before you can enable American Express® card acceptance in the merchant boarding system. The American Express Merchant Registration application allows you to submit and maintain the merchant registration. There are several registration scenarios that may occur depending on how the acquirer is set up with TSYS. These scenarios include:
- Front-end Only: The merchant will only process authorization and capture data through TSYS.
- Back-end Only: The merchant will only process clearing and settlement data through TSYS.
- Full Service: The merchant will process front-end and back-end data through TSYS.
These scenarios determine how you will register the merchant for American Express.
Here are some typical registration scenarios:
New Boarding Scenarios
Merchant not eligible for OptBlue due to prohibited MCC, no alternate AMEX service selected
In this scenario, an error will occur on registration.
Registration Required?
|
No
|
TSYS sends Sales Performance File(s) to Amex?
|
N/A
|
TSYS sends Registration (Sponsored Merchant) File(s) to Amex?
|
N/A
|
Disposition within the Amex Merchant Registration (AMR)
|
N/A
|
Status
|
N/A
|
AMEX Acceptance field value (front and back end)
|
N
|
OptBlue field value (front and back end)
|
N
|
Merchant is not eligible for OptBlue due to estimated volume > $1M/$100K (R12/R3) in an industry category subject to the threshold. AMEX agrees to take merchant as "direct"
In this scenario, the AMEX Acceptance field being set to Y on the back-end means that TSYS can post Amex activity on reports and on merchant statements. Funding and billing the merchant would not be allowed.
Registration Required?
|
No
|
TSYS sends Sales Performance File(s) to Amex?
|
N/A
|
TSYS sends Registration (Sponsored Merchant) File(s) to Amex?
|
N/A
|
Disposition within the Amex Merchant Registration (AMR)
|
N/A
|
Status
|
N/A
|
AMEX Acceptance field value (front and back end)
|
Y
|
OptBlue field value (front and back end)
|
N
|
Merchant not eligible for OptBlue due to being on AMEX Franchise List
In this scenario, the AMEX Acceptance field being set to Y on the back-end means that TSYS can post Amex activity on reports and on merchant statements. Funding and billing the merchant would not be allowed.
Registration Required?
|
No
|
TSYS sends Sales Performance File(s) to Amex?
|
N/A
|
TSYS sends Registration (Sponsored Merchant) File(s) to Amex?
|
N/A
|
Disposition within the Amex Merchant Registration (AMR)
|
N/A
|
Status
|
N/A
|
AMEX Acceptance field value (front and back end)
|
Y
|
OptBlue field value (front and back end)
|
N
|
Merchant not eligible for OptBlue due to being on the AMEX Merchant Financing Program
In this scenario, the AMEX Acceptance field being set to Y on the back-end means that TSYS can post Amex activity on reports and on merchant statements. Funding and billing the merchant would not be allowed.
Registration Required?
|
No
|
TSYS sends Sales Performance File(s) to Amex?
|
N/A
|
TSYS sends Registration (Sponsored Merchant) File(s) to Amex?
|
N/A
|
Disposition within the Amex Merchant Registration (AMR)
|
N/A
|
Status
|
N/A
|
Amex Acceptance field value (front and back end)
|
Y
|
OptBlue field value (front and back end)
|
N
|
Merchant not eligible for OptBlue due to risk evaluation
Registration Required?
|
No
|
TSYS sends Sales Performance File(s) to Amex?
|
N/A
|
TSYS sends Registration (Sponsored Merchant) File(s) to Amex?
|
N/A
|
Disposition within the Amex Merchant Registration (AMR)
|
N/A
|
Status
|
N/A
|
AMEX Acceptance field value (front and back end)
|
N
|
OptBlue field value (front and back end)
|
N
|
Merchant eligible for OptBlue but declined AMEX
Note: If the merchant's Registration Status in this scenario is changed to anything other than R, the GSMF (previously SPOIG) file will not include the merchant record.
Registration Required?
|
Yes
|
TSYS sends Sales Performance File(s) to Amex?
|
Yes
|
TSYS sends Registration (Sponsored Merchant) File(s) to Amex?
|
No
|
Disposition within the Amex Merchant Registration (AMR)
|
Declined Amex
|
Registration Status
|
R
|
AMEX Acceptance field value (front and back end)
|
N
|
OptBlue field value (front and back end)
|
N
|
Merchant wants to accept AMEX but opt out of OptBlue; AMEX agrees to take merchant as "direct"
In this scenario, the AMEX Acceptance field being set to Y on the back-end means that TSYS can post Amex activity on reports and on merchant statements. Funding and billing the merchant would not be allowed.
Note: If the merchant's Registration Status in this scenario is changed to anything other than R, the GSMF (previously SPOIG) file will not include the merchant record.
Registration Required?
|
Yes
|
TSYS sends Sales Performance File(s) to Amex?
|
Yes
|
TSYS sends Registration (Sponsored Merchant) File(s) to Amex?
|
No
|
Disposition within the Amex Merchant Registration (AMR)
|
ESA
|
Status
|
R
|
AMEX Acceptance field value (front and back end)
|
Y
|
OptBlue field value (front and back end)
|
N
|
Merchant wants to accept AMEX and opts for OptBlue
In this scenario, the client is responsible for funding Amex transactions through the Transmit bank.
Note: If the merchant's Registration Status in this scenario is changed to anything other than R, the GSMF (previously SPOIG) file will not include the merchant record.
Registration Required?
|
Yes
|
TSYS sends Sales Performance File(s) to Amex?
|
Yes
|
TSYS sends Registration (Sponsored Merchant) File(s) to Amex?
|
Yes
|
Disposition within the Amex Merchant Registration (AMR)
|
OptBlue
|
Status
|
R
|
AMEX Acceptance field value (front and back end)
|
Y
|
OptBlue field value (front and back end)
|
Y
|
Existing Registration Scenarios
OptBlue merchant moves to AMEX Direct due to high volume
In this scenario, Amex contacts TSYS, TSYS contacts PSE, and PSE maintains the boarding system. This is known as a High CV Conversion process; see Switch from OptBlue to ESA/Direct.
The AMEX Acceptance field being set to Y on the back-end means that TSYS can post Amex activity on reports and on merchant statements. Funding and billing the merchant would not be allowed.
Note: If the merchant's Registration Status in this scenario is changed to anything other than R, the GSMF (previously SPOIG) file will not include the merchant record.
Registration Required?
|
Yes
|
TSYS sends Sales Performance File(s) to Amex?
|
No - Sales Performance is only at initial registration
|
TSYS sends Registration (Sponsored Merchant) File(s) to Amex?
|
No
|
Disposition within the Amex Merchant Registration (AMR)
|
Moves from OptBlue to ESA
|
Status
|
R
|
AMEX Acceptance field value (front and back end)
|
Stays as Y
|
OptBlue field value (front and back end)
|
Changes from Y to N
|
ESA/direct AMEX-registered merchant moves to OptBlue
In this scenario, the client is responsible for funding Amex transactions through the Transmit bank. Coordination with TSYS and Amex may be required for target date of changes to the merchant funding.
Note: If the merchant's Registration Status in this scenario is changed to anything other than R, the GSMF (previously SPOIG) file will not include the merchant record.
Registration Required?
|
Yes if change required
|
TSYS sends Sales Performance File(s) to Amex?
|
No - Sales Performance is only at initial registration
|
TSYS sends Registration (Sponsored Merchant) File(s) to Amex?
|
Yes
|
Disposition within the Amex Merchant Registration (AMR)
|
Moves from ESA to OptBlue
|
Status
|
R
|
AMEX Acceptance field value (front and back end)
|
Stays as Y
|
OptBlue field value (front and back end)
|
Changes from N to Y
|
Non-Existing Registration Scenarios
ESA/direct AMEX-unregistered merchant moves to OptBlue
In this scenario, the client is responsible for funding AMEX transactions through the Transmit bank. Coordination with TSYS and AMEX may be required for target date of changes to the merchant funding.
Note: If the merchant's Registration Status in this scenario is changed to anything other than R, the SPOIG file will not include the merchant record.
Registration Required?
|
Yes
|
TSYS sends Sales Performance File(s) to Amex?
|
Yes
|
TSYS sends Registration (Sponsored Merchant) File(s) to Amex?
|
Yes
|
Disposition within the Amex Merchant Registration (AMR)
|
Moves from N/A to OptBlue
|
Status
|
R
|
AMEX Acceptance field value (front and back end)
|
Stays as Y
|
OptBlue field value (front and back end)
|
Changes from N to Y
|
