UserCategory
OWNER
initiates a transfer to another OWNER
, they are required to complete SCA unless Mangopay can apply an exemption (read more about SCA on transfers).To let the user complete the SCA session on the Mangopay-hosted webpage, your platform needs to retrieve the returned PendingUserAction.RedirectUrl
, add an encoded returnUrl
query parameter, and redirect the user. Read more about how to redirect them in the SCA session guide.USER_PRESENT
, USER_NOT_PRESENT
Default value: null
The SCA context of the request, which should be considered required if the AuthorId
references a user whose UserCategory
is OWNER
:USER_PRESENT
– The user is initiating the transfer and is actively present. The platform must redirect the user for SCA using the PendingUserAction.RedirectUrl
returned, unless an exemption can be applied by Mangopay such as on low-amount and low-risk transfers. Platforms are not able to request specific exemptions (read more).USER_NOT_PRESENT
– No user is present: the transfer is automated by the platform as part of their declared and authorized workflow. On these transfers, SCA redirection is not initially required, but in future Mangopay may be required to override the request.ScaContext
is a temporary mechanism to introduce SCA on existing endpoints and workflows. New integrations should consider the parameter required and send USER_PRESENT
by default. Read more about SCA on transfers →200
USER_PRESENT
, USER_NOT_PRESENT
Default value: null
The SCA context of the request, which should be considered required if the AuthorId
references a user whose UserCategory
is OWNER
:USER_PRESENT
– The user is initiating the transfer and is actively present. The platform must redirect the user for SCA using the PendingUserAction.RedirectUrl
returned, unless an exemption can be applied by Mangopay such as on low-amount and low-risk transfers. Platforms are not able to request specific exemptions (read more).USER_NOT_PRESENT
– No user is present: the transfer is automated by the platform as part of their declared and authorized workflow. On these transfers, SCA redirection is not initially required, but in future Mangopay may be required to override the request.ScaContext
is a temporary mechanism to introduce SCA on existing endpoints and workflows. New integrations should consider the parameter required and send USER_PRESENT
by default. Read more about SCA on transfers →CreditedFunds
= DebitedFunds
- Fees
).CREATED
, SUCCEEDED
, FAILED
The status of the transaction.SUCCEEDED
, indicating that the transaction occurred. The statuses CREATED
and FAILED
return an ExecutionDate
of null
.PAYIN
, TRANSFER
, CONVERSION
, PAYOUT
The type of the transaction.REGULAR
, REPUDIATION
, REFUND
, SETTLEMENT
The nature of the transaction, providing more information about the context in which the transaction occurred:REGULAR
– Relative to most of the transactions (pay-ins, payouts, and transfers) in a usual workflow.REPUDIATION
– Automatic withdrawal of funds from the platform’s repudiation wallet as part of the dispute process (when the user has requested a chargeback).REFUND
– Reimbursement of a transaction to the user (pay-in refund), to a wallet (transfer refund), or of a payout (payout refund, only initiated by Mangopay).SETTLEMENT
– Transfer made to the repudiation wallet by the platform to settle a lost dispute.null
).400 - Currency incompatibility