Package com.onlinepayments.domain
Class GPayThreeDSecure
java.lang.Object
com.onlinepayments.domain.GPayThreeDSecure
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionDimensions of the challenge window that potentially will be displayed to the customer.Allows you to indicate if you want the customer to be challenged for extra security on this transaction.In PSD2, the ExemptionRequest field is used by merchants requesting an exemption when not using authentication on a transaction, in order to keep the conversion up.Object containing browser specific redirection related datatrue = 3D Secure authentication will be skipped for this transaction.voidsetChallengeCanvasSize(String value) Dimensions of the challenge window that potentially will be displayed to the customer.voidsetChallengeIndicator(String value) Allows you to indicate if you want the customer to be challenged for extra security on this transaction.voidsetExemptionRequest(String value) In PSD2, the ExemptionRequest field is used by merchants requesting an exemption when not using authentication on a transaction, in order to keep the conversion up.voidObject containing browser specific redirection related datavoidsetSkipAuthentication(Boolean value) true = 3D Secure authentication will be skipped for this transaction.withChallengeCanvasSize(String value) Dimensions of the challenge window that potentially will be displayed to the customer.withChallengeIndicator(String value) Allows you to indicate if you want the customer to be challenged for extra security on this transaction.withExemptionRequest(String value) In PSD2, the ExemptionRequest field is used by merchants requesting an exemption when not using authentication on a transaction, in order to keep the conversion up.Object containing browser specific redirection related datawithSkipAuthentication(Boolean value) true = 3D Secure authentication will be skipped for this transaction.
-
Constructor Details
-
GPayThreeDSecure
public GPayThreeDSecure()
-
-
Method Details
-
getChallengeCanvasSize
Dimensions of the challenge window that potentially will be displayed to the customer. The challenge content is formatted to appropriately render in this window to provide the best possible user experience. Preconfigured sizes are width x height in pixels of the window displayed in the customer browser window. Possible values are- 250x400 (default)
- 390x400
- 500x600
- 600x400
- full-screen
-
setChallengeCanvasSize
Dimensions of the challenge window that potentially will be displayed to the customer. The challenge content is formatted to appropriately render in this window to provide the best possible user experience. Preconfigured sizes are width x height in pixels of the window displayed in the customer browser window. Possible values are- 250x400 (default)
- 390x400
- 500x600
- 600x400
- full-screen
-
withChallengeCanvasSize
Dimensions of the challenge window that potentially will be displayed to the customer. The challenge content is formatted to appropriately render in this window to provide the best possible user experience. Preconfigured sizes are width x height in pixels of the window displayed in the customer browser window. Possible values are- 250x400 (default)
- 390x400
- 500x600
- 600x400
- full-screen
-
getChallengeIndicator
Allows you to indicate if you want the customer to be challenged for extra security on this transaction. Possible values:- no-preference - You have no preference whether or not to challenge the customer (default)
- no-challenge-requested - you prefer the cardholder not to be challenged
- challenge-requested - you prefer the customer to be challenged
- challenge-required - you require the customer to be challenged
- no-challenge-requested-risk-analysis-performed – letting the issuer know that you have already assessed the transaction with fraud prevention tool
- no-challenge-requested-data-share-only – sharing data only with the DS
- no-challenge-requested-consumer-authentication-performed – authentication already happened at your side – when login in to your website
- no-challenge-requested-use-whitelist-exemption – cardholder has whitelisted you at with the issuer
- challenge-requested-whitelist-prompt-requested – cardholder is trying to whitelist you
- request-scoring-without-connecting-to-acs – sending information to CB DS for a fraud scoring
-
setChallengeIndicator
Allows you to indicate if you want the customer to be challenged for extra security on this transaction. Possible values:- no-preference - You have no preference whether or not to challenge the customer (default)
- no-challenge-requested - you prefer the cardholder not to be challenged
- challenge-requested - you prefer the customer to be challenged
- challenge-required - you require the customer to be challenged
- no-challenge-requested-risk-analysis-performed – letting the issuer know that you have already assessed the transaction with fraud prevention tool
- no-challenge-requested-data-share-only – sharing data only with the DS
- no-challenge-requested-consumer-authentication-performed – authentication already happened at your side – when login in to your website
- no-challenge-requested-use-whitelist-exemption – cardholder has whitelisted you at with the issuer
- challenge-requested-whitelist-prompt-requested – cardholder is trying to whitelist you
- request-scoring-without-connecting-to-acs – sending information to CB DS for a fraud scoring
-
withChallengeIndicator
Allows you to indicate if you want the customer to be challenged for extra security on this transaction. Possible values:- no-preference - You have no preference whether or not to challenge the customer (default)
- no-challenge-requested - you prefer the cardholder not to be challenged
- challenge-requested - you prefer the customer to be challenged
- challenge-required - you require the customer to be challenged
- no-challenge-requested-risk-analysis-performed – letting the issuer know that you have already assessed the transaction with fraud prevention tool
- no-challenge-requested-data-share-only – sharing data only with the DS
- no-challenge-requested-consumer-authentication-performed – authentication already happened at your side – when login in to your website
- no-challenge-requested-use-whitelist-exemption – cardholder has whitelisted you at with the issuer
- challenge-requested-whitelist-prompt-requested – cardholder is trying to whitelist you
- request-scoring-without-connecting-to-acs – sending information to CB DS for a fraud scoring
-
getExemptionRequest
In PSD2, the ExemptionRequest field is used by merchants requesting an exemption when not using authentication on a transaction, in order to keep the conversion up.- none = No exemption requested
- transaction-risk-analysis = Fraud analysis has been done already by your own fraud module and transaction scored as low risk
- low-value = Bellow 30 euros
- whitelist = The cardholder has whitelisted you with their issuer
-
setExemptionRequest
In PSD2, the ExemptionRequest field is used by merchants requesting an exemption when not using authentication on a transaction, in order to keep the conversion up.- none = No exemption requested
- transaction-risk-analysis = Fraud analysis has been done already by your own fraud module and transaction scored as low risk
- low-value = Bellow 30 euros
- whitelist = The cardholder has whitelisted you with their issuer
-
withExemptionRequest
In PSD2, the ExemptionRequest field is used by merchants requesting an exemption when not using authentication on a transaction, in order to keep the conversion up.- none = No exemption requested
- transaction-risk-analysis = Fraud analysis has been done already by your own fraud module and transaction scored as low risk
- low-value = Bellow 30 euros
- whitelist = The cardholder has whitelisted you with their issuer
-
getRedirectionData
Object containing browser specific redirection related data -
setRedirectionData
Object containing browser specific redirection related data -
withRedirectionData
Object containing browser specific redirection related data -
getSkipAuthentication
- true = 3D Secure authentication will be skipped for this transaction. This setting should be used when isRecurring is set to true and recurringPaymentSequenceIndicator is set to "recurring"
- false = 3D Secure authentication will not be skipped for this transaction
Note: This is only possible if your account in our system is setup for 3D Secure authentication and if your configuration in our system allows you to override it per transaction
-
setSkipAuthentication
- true = 3D Secure authentication will be skipped for this transaction. This setting should be used when isRecurring is set to true and recurringPaymentSequenceIndicator is set to "recurring"
- false = 3D Secure authentication will not be skipped for this transaction
Note: This is only possible if your account in our system is setup for 3D Secure authentication and if your configuration in our system allows you to override it per transaction
-
withSkipAuthentication
- true = 3D Secure authentication will be skipped for this transaction. This setting should be used when isRecurring is set to true and recurringPaymentSequenceIndicator is set to "recurring"
- false = 3D Secure authentication will not be skipped for this transaction
Note: This is only possible if your account in our system is setup for 3D Secure authentication and if your configuration in our system allows you to override it per transaction
-