Interface D1PushWallet
- 
 public interface D1PushWallet
- 
- 
Method SummaryAll Methods Instance Methods Abstract Methods Modifier and Type Method Description voidactivateDigitalCard(String cardID, OEMPayType oemType, D1Task.Callback<Void> callback)Activate the digital card which has been digitized but not yet done ID&V (Step up authentication - Yellow Flow inApp Verification).voidactivateDigitalCard(String digitalCardID, D1Task.Callback<Void> callback)Activate the digital card which has been digitized but not yet done ID&V (Step up authentication - Yellow Flow inApp Verification).voidactivateSamsungPay()Samsung Pay only.voidaddDigitalCardToOEM(String cardID, OEMPayType oemType, Activity activity, D1Task.Callback<Object> callback)Add Digital Card for a givencardIDfor OEM Type (Google Pay or Samsung Pay).voidgetCardDigitizationState(String cardID, OEMPayType oemType, D1Task.Callback<CardDigitizationState> callback)Check if the card has been digitized or not.voidupdateSamsungPay()Samsung Pay only.
 
- 
- 
- 
Method Detail- 
activateSamsungPayvoid activateSamsungPay() throws D1ExceptionSamsung Pay only.An utility function to bring the Samsung Pay app to a state in which cards can be added. End user need to sign-in into Samsung Pay app. Integrator should call this API when D1PushWallet.addDigitalCardToOEM failed with D1Exception.ErrorCode.ERROR_SPAY_SETUP_NOT_COMPLETED
 Possible errors:
 - Throws:
- D1Exception
 
 - 
updateSamsungPayvoid updateSamsungPay() throws D1ExceptionSamsung Pay only.An utility function to bring a user to update their Samsung Pay app. Integrator should call this API when D1PushWallet.addDigitalCardToOEM failed with D1Exception.ErrorCode.ERROR_SPAY_NEED_TO_UPDATE
 Possible errors:
 - Throws:
- D1Exception
 
 - 
getCardDigitizationStatevoid getCardDigitizationState(@NonNull String cardID, @NonNull OEMPayType oemType, @NonNull D1Task.Callback<CardDigitizationState> callback) Check if the card has been digitized or not. Use this API to determine if we need to show Add to Wallet button on the Application.- Parameters:
- cardID- The card identifier
- oemType- The oemType (Google Pay or Samsung Pay)
- callback- The callback for the result. When it succeeds, the returned argument of the- D1Task.Callback.onSuccess(Object)is always non-null.
 Possible errors:
 - D1Exception.ErrorCode.ERROR_NOT_LOGGED_IN
- D1Exception.ErrorCode.ERROR_NOT_AUTHORIZED
- D1Exception.ErrorCode.ERROR_DEVICE_ENVIRONMENT_UNSAFE
- D1Exception.ErrorCode.ERROR_GPAY_NOT_SUPPORTED
- D1Exception.ErrorCode.ERROR_SPAY_NOT_SUPPORTED
- D1Exception.ErrorCode.ERROR_CORE
- D1Exception.ErrorCode.ERROR_SPAY
- D1Exception.ErrorCode.ERROR_GPAY
- D1Exception.ErrorCode.ERROR_CARD
 
 
 - 
addDigitalCardToOEMvoid addDigitalCardToOEM(@NonNull String cardID, @NonNull OEMPayType oemType, @Nullable Activity activity, @NonNull D1Task.Callback<Object> callback) Add Digital Card for a givencardIDfor OEM Type (Google Pay or Samsung Pay).Integrator must override the Activity.onActivityResult()and pass the result back to SDK usingD1Task.handleCardResult(int, int, Intent)API- Parameters:
- cardID- The card identifier
- oemType- The oemType (Google Pay or Samsung Pay)
- activity- The caller activity. Set this value if the 'activity' value of- ConfigParams.buildConfigCard(Activity, OEMPayType, String)is null or they are different. Otherwise, you can set it to `null`.
- callback- The callback for the result. When it succeeds, the returned argument of the- D1Task.Callback.onSuccess(Object)is always null.
 Possible errors:
 - D1Exception.ErrorCode.ERROR_NOT_LOGGED_IN
- D1Exception.ErrorCode.ERROR_NOT_AUTHORIZED
- D1Exception.ErrorCode.ERROR_DEVICE_ENVIRONMENT_UNSAFE
- D1Exception.ErrorCode.ERROR_GPAY_NOT_SUPPORTED
- D1Exception.ErrorCode.ERROR_SPAY_NOT_SUPPORTED
- D1Exception.ErrorCode.ERROR_CORE
- D1Exception.ErrorCode.ERROR_SPAY
- D1Exception.ErrorCode.ERROR_GPAY
- D1Exception.ErrorCode.ERROR_CARD
 
- See Also:
- D1Task.handleCardResult(int, int, Intent)
 
 - 
activateDigitalCardvoid activateDigitalCard(@NonNull String cardID, @NonNull OEMPayType oemType, @NonNull D1Task.Callback<Void> callback) Activate the digital card which has been digitized but not yet done ID&V (Step up authentication - Yellow Flow inApp Verification). Integrator should call this API when the return state of getCardDigitizationState(String,OEMPayType, D1Task.Callback)isCardDigitizationState.PENDING_IDV- Parameters:
- cardID- The card ID
- oemType- The oemType (Google Pay or Samsung Pay)
- callback- The callback for result. When it succeeds, the returned argument of the- D1Task.Callback.onSuccess(Object)is always null.
 Possible errors:
 - D1Exception.ErrorCode.ERROR_NOT_LOGGED_IN
- D1Exception.ErrorCode.ERROR_NOT_AUTHORIZED
- D1Exception.ErrorCode.ERROR_DEVICE_ENVIRONMENT_UNSAFE
- D1Exception.ErrorCode.ERROR_CORE
- D1Exception.ErrorCode.ERROR_CARD
- D1Exception.ErrorCode.ERROR_CARD_NO_PENDING_IDV
- D1Exception.ErrorCode.ERROR_SPAY
- D1Exception.ErrorCode.ERROR_GPAY
 
 
 - 
activateDigitalCardvoid activateDigitalCard(@NonNull String digitalCardID, @NonNull D1Task.Callback<Void> callback) Activate the digital card which has been digitized but not yet done ID&V (Step up authentication - Yellow Flow inApp Verification). Integrator should call this API to activate a digital card when a wallet app redirect digital card activation to the Issuer app. - Parameters:
- digitalCardID- The digital card identifier
- callback- The callback for result. When it succeeds, the returned argument of the- D1Task.Callback#onSuccess(Void)is always null.
 Possible errors:
 
- Since:
- 3.2.0
 
 
- 
 
-