Skip to main content

​
Added

​
Test email value to bypass SCA in Sandbox

In Sandbox, you can bypass SCA by including the word accept in the Email value of the Natural User or the LegalRepresentative.Email value of the Legal User – for example accept@example.com or john.doe+accept@example.com. If the user has accept in their email, then the API does not apply SCA during enrollment in the User endpoints or any of the SCA-triggering actions (recipient creation, transfers, and wallet access). The API proceeds with the requested action and doesn’t return the PendingUserAction.RedirectUrl SCA redirection link.

​
Added

​
ChargeBearer parameter for cost-bearing on SWIFT payouts

On SWIFT non-domestic payouts, platforms can now choose to bear the cost of all processing fees arising from correspondent banks. On a given payout request, platforms can set ChargeBearer to OUR on the POST Create a Payout endpoint to choose to pay all fees that may be incurred. Mangopay recovers the fees paid by your platform during the billing cycle. The OUR option allows the payout beneficiary to receive the full CreditedFunds.Amount of the payout on their recipient account. Otherwise, by default, Mangopay uses the SHA option of SWIFT bank wires. This means that the SWIFT fees are shared between the remitter and the beneficiary, and the beneficiary’s share is deducted from the payout amount that arrives on their account. Charge bearing is available in any currency (provided the option is supported) and on a per-request basis thanks to this new parameter. To activate the OUR option for your platform, contact our teams via the Dashboard. Read more about charge bearing for SWIFT payouts →