Added
Extended Preauthorization feature to rename Deposit Preauthorizations
Mangopay has re-released its 30-day preauthorization feature under the new name of Extended Preauthorizations.
The previous use of the term “deposit” was for convenience only and does not constitute a traditional banking deposit under applicable banking regulations, including the EU Capital Requirements Directive (Directive 2013/36/EU) or the Deposit Guarantee Schemes Directive (Directive 2014/49/EU). Accordingly, these funds are not covered by any statutory deposit protection schemes, and Mangopay does not operate as a licensed banking institution.
Note – Update to Extended Preauthorization before end of 2027
Platforms who have integrated the Deposit Preauthorization for cards or PayPal need to update their integration to the new Extended Preauthorization endpoints before the end of 2027, at which point the legacy endpoints will be decommissioned and no longer function.
The Extended Preauthorization feature is a like-for-like renaming of the legacy Deposit Preauthorization – the behavior is otherwise unchanged.
The full list of new endpoints is:
- POST Create a Card Extended Preauthorization
- POST Create a PayPal Extended Preauthorization
- GET View an Extended Preauthorization
- PUT Cancel an Extended Preauthorization
- GET List Extended Preauthorizations for a Card
- GET List Extended Preauthorizations for a User
- GET List Transactions for an Extended Preauthorization
- POST Create an Extended Preauthorized PayIn
Eight new webhook event types are available, mirroring the deprecated Deposit Preauthorization events:
EXTENDED_PREAUTHORIZATION_CREATEDEXTENDED_PREAUTHORIZATION_FAILEDEXTENDED_PREAUTHORIZATION_PAYMENT_WAITINGEXTENDED_PREAUTHORIZATION_PAYMENT_VALIDATEDEXTENDED_PREAUTHORIZATION_PAYMENT_FAILEDEXTENDED_PREAUTHORIZATION_PAYMENT_CANCEL_REQUESTEDEXTENDED_PREAUTHORIZATION_PAYMENT_CANCELEDEXTENDED_PREAUTHORIZATION_PAYMENT_EXPIRED
The pay-in object captured against an Extended Preauthorization returns the new ExtendedPreauthorizationId, which your platform must rely on for the new feature.
Regardless of which endpoint was used to capture the preauthorized funds, the pay-in object returns both the ExtendedPreauthorizationId and the now-deprecated DepositId containing the same unique identifier.
The prefix of the unique identifier allows you to determine the endpoint used to create the preauthorization:
ext_auth_wt_<uuid>– POST Create a Card Extended Preauthorization or POST Create a PayPal Extended Preauthorizationdeposit_wt_<uuid>– POST Create a Card Deposit Preauthorization or POST Create a PayPal Deposit Preauthorization
Changed
Deposit Preauthorization feature deprecated
The Deposit Preauthorization endpoints and webhook events are deprecated in favor of their Extended Preauthorization equivalents.
- POST Create a Card Deposit Preauthorization
- POST Create a PayPal Deposit Preauthorization
- GET View a Deposit Preauthorization
- PUT Cancel a Deposit Preauthorization
- GET List Deposit Preauthorizations for a Card
- GET List Deposit Preauthorizations for a User
- GET List Transactions for a Deposit Preauthorization
- POST Create a Deposit Preauthorized PayIn
The following webhook event types are also deprecated:
DEPOSIT_PREAUTHORIZATION_CREATEDDEPOSIT_PREAUTHORIZATION_FAILEDDEPOSIT_PREAUTHORIZATION_PAYMENT_WAITINGDEPOSIT_PREAUTHORIZATION_PAYMENT_VALIDATEDDEPOSIT_PREAUTHORIZATION_PAYMENT_FAILEDDEPOSIT_PREAUTHORIZATION_PAYMENT_CANCEL_REQUESTEDDEPOSIT_PREAUTHORIZATION_PAYMENT_CANCELEDDEPOSIT_PREAUTHORIZATION_PAYMENT_EXPIRED
In the pay-in object captured against a Deposit Preauthorization, the DepositId is deprecated in favor of the new ExtendedPreauthorizationId, which contains the same unique value (see above).