ExpirationDate
, thereby releasing the preauthorized funds.
The PaymentStatus
can be set to:
CANCELED
when no preauthorized pay-ins have been made to capture funds. Trying to cancel a used preauthorization returns an error.VALIDATED
when at least one preauthorized pay-in has been made to capture funds. Trying to validate an unused preauthorization returns an error.CANCELED
or VALIDATED
status can’t be reused.CANCELED
, VALIDATED
The status of the preauthorization object:WAITING
– The remaining preauthorized funds can be captured by making one or several preauthorized pay-ins. Pay-ins can only be made against a preauthorization with the WAITING
status.CANCELED
– The preauthorization was canceled manually before any preauthorized pay-ins were made, or it was canceled automatically because the authorization failed.EXPIRED
– The hold period on the preauthorized funds has ended without any preauthorized pay-ins taking place.VALIDATED
– During the hold period: Indicates that all the preauthorized funds have been captured (RemainingFunds
is zero) and no more preauthorized pay-ins can be made. After the hold period: Indicates that at least one capture was made during the hold period.200 - Canceled (no captures)
null
.CREATED
, SUCCEEDED
, FAILED
The status of the authorization.WAITING
, CANCELED
, EXPIRED
, VALIDATED
The status of the preauthorization object:WAITING
– The remaining preauthorized funds can be captured by making one or several preauthorized pay-ins. Pay-ins can only be made against a preauthorization with the WAITING
status.CANCELED
– The preauthorization was canceled manually before any preauthorized pay-ins were made, or it was canceled automatically because the authorization failed.EXPIRED
– The hold period on the preauthorized funds has ended without any preauthorized pay-ins taking place.VALIDATED
– During the hold period: Indicates that all the preauthorized funds have been captured (RemainingFunds
is zero) and no more preauthorized pay-ins can be made. After the hold period: Indicates that at least one capture was made during the hold period.PaymentStatus
changes to EXPIRED
if no captures were made or VALIDATED
if at least one capture was made.DEFAULT
, FORCE
, NO_CHOICE
The mode applied for the 3DS2 protocol for CB, Visa, and Mastercard. The options are:DEFAULT
– Requests an exemption to strong customer authentication (SCA), and thus a frictionless payment experience, if allowed by your Mangopay contract and accepted by the issuer.FORCE
– Requests SCA.NO_CHOICE
– Leaves the choice to the issuer whether to allow for a frictionless payment experience or to enforce SCA.SecureModeNeeded
parameter is set to true
).SecureMode
was used.CARD
, DIRECT_DEBIT
, PREAUTHORIZED
, BANK_WIRE
The type of pay-in.WEB
, DIRECT
, EXTERNAL_INSTRUCTION
The type of execution for the pay-in.V1
, V2_1
The 3DS protocol version to be applied to the transaction.V1
, V2_1
The 3DS protocol version applied to the transaction.VISA
, MASTERCARD
, CB
, MAESTRO
The card network to use, as chosen by the cardholder, in case of co-branded cards.null
is returned.200 - Validated following successful capture
null
.CREATED
, SUCCEEDED
, FAILED
The status of the authorization.WAITING
, CANCELED
, EXPIRED
, VALIDATED
The status of the preauthorization object:WAITING
– The remaining preauthorized funds can be captured by making one or several preauthorized pay-ins. Pay-ins can only be made against a preauthorization with the WAITING
status.CANCELED
– The preauthorization was canceled manually before any preauthorized pay-ins were made, or it was canceled automatically because the authorization failed.EXPIRED
– The hold period on the preauthorized funds has ended without any preauthorized pay-ins taking place.VALIDATED
– During the hold period: Indicates that all the preauthorized funds have been captured (RemainingFunds
is zero) and no more preauthorized pay-ins can be made. After the hold period: Indicates that at least one capture was made during the hold period.PaymentStatus
changes to EXPIRED
if no captures were made or VALIDATED
if at least one capture was made.DEFAULT
, FORCE
, NO_CHOICE
The mode applied for the 3DS2 protocol for CB, Visa, and Mastercard. The options are:DEFAULT
– Requests an exemption to strong customer authentication (SCA), and thus a frictionless payment experience, if allowed by your Mangopay contract and accepted by the issuer.FORCE
– Requests SCA.NO_CHOICE
– Leaves the choice to the issuer whether to allow for a frictionless payment experience or to enforce SCA.SecureModeNeeded
parameter is set to true
).SecureMode
was used.CARD
, DIRECT_DEBIT
, PREAUTHORIZED
, BANK_WIRE
The type of pay-in.WEB
, DIRECT
, EXTERNAL_INSTRUCTION
The type of execution for the pay-in.V1
, V2_1
The 3DS protocol version to be applied to the transaction.V1
, V2_1
The 3DS protocol version applied to the transaction.VISA
, MASTERCARD
, CB
, MAESTRO
The card network to use, as chosen by the cardholder, in case of co-branded cards.null
is returned.400 - Cancel attempted after capture
400 - Validation attempted before capture