Note – Pay-in data retained for 13 monthsAn API call to retrieve a pay-in whose
CreationDate
is older than 13 months may return 404 Not Found.For more information, see the Data availability periods article.Path parameters
The unique identifier of the pay-in.
Responses
200
200
Returned values:
GIROPAY
, SOFORT
The type of direct debit.Max length: 128 characters (see data formats for details)The unique identifier of the object.
Max. length: 255 charactersCustom data that you can add to this object.
For transactions (pay-in, transfer, payout), you can use this parameter to identify corresponding information regarding the user, transaction, or payment methods on your platform.
For transactions (pay-in, transfer, payout), you can use this parameter to identify corresponding information regarding the user, transaction, or payment methods on your platform.
The date and time at which the object was created.
The code indicating the result of the operation. This information is mostly used to handle errors or for filtering purposes.
The explanation of the result code.
The unique identifier of the user at the source of the transaction.
Default value: The unique identifier of the owner of the credited wallet.The unique identifier of the user whose wallet is credited.
Information about the debited funds.
Information about the credited funds (
CreditedFunds
= DebitedFunds
- Fees
).Information about the fees taken by the platform for this transaction (and hence transferred to the Fees Wallet).
Returned values:
CREATED
, SUCCEEDED
, FAILED
The status of the transaction.The date and time at which the status changed to
SUCCEEDED
, indicating that the transaction occurred. The statuses CREATED
and FAILED
return an ExecutionDate
of null
.Returned values:
PAYIN
, TRANSFER
, CONVERSION
, PAYOUT
The type of the transaction.Returned values:
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.
The unique identifier of the credited wallet.
The unique identifier of the debited wallet.In the case of a pay-in, this value is always
null
since there is no debited wallet.Returned values:
CARD
, DIRECT_DEBIT
, PREAUTHORIZED
, BANK_WIRE
The type of pay-in.Returned values:
WEB
, DIRECT
, EXTERNAL_INSTRUCTION
The type of execution for the pay-in.The URL to which to redirect the user to complete the payment.Caution: This variable URL is specific to each payment. You must rely on the returned URL in full (host, path, and queries) and not hardcode any part of it.
Max. length: 220 charactersThe URL to which the user is returned after the payment, whether the transaction is successful or not.
Caution: This customization feature is deprecated and must no longer be used. You must redirect on the
RedirectURL
instead.The customized URL to which to redirect the user to complete the payment.Returned values: One of the supported languages in the ISO 639-1 format: CS, DA, DE, EL, EN, ES, FI, FR, HU, IT, NL, NO, PL, PT, SK, SV.The language in which the payment page is to be displayed.