AuthorId
.
RedirectUrl
from the WWW-Authenticate
response header, 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 user’s UserCategory
is OWNER
:USER_PRESENT
– The user is initiating the wallet access request and is actively present. The platform must redirect the user for SCA using the PendingUserAction.RedirectUrl
returned, unless a successful SCA session for wallet access occurred in the last 180 days.USER_NOT_PRESENT
– No user is present: the access is automated by the platform as part of their declared and authorized workflow. On these requests, 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 wallet access →CREATED
, SUCCEEDED
, FAILED
The status of the transaction. You can filter on multiple values by separating them with a comma.CreationDate
parameter). You can filter on a specific time range by using both the AfterDate
and BeforeDate
query parameters.CreationDate
parameter). You can filter on a specific time range by using both the AfterDate
and BeforeDate
query parameters.PAYIN
, TRANSFER
, CONVERSION
, PAYOUT
The type of the transaction. You can filter on multiple values by separating them with a comma.REGULAR
, REPUDIATION
, REFUND
, SETTLEMENT
The nature of the transaction, providing more information about the context in which the transaction occurred. You can filter on multiple values by separating them with a comma.200
401 - SCA required
redirectUrl
in the WWW-Authenticate
response header:returnUrl
query parameter, and redirect the user.Read more about SCA redirection and SCA on wallet access →