Create an Instant Conversion between user Wallets

The unique identifier of the user at the source of the transaction. In a conversion, both the debited and credited wallets are owned by the author.

The unique identifier of the debited wallet (in the sell currency).

The unique identifier of the credited wallet (in the buy currency).

Max. length: 255 characters

Custom data that you can add to this object, such as unique identifiers in your system. To store multiple values, you can serialize them into a single string, for example a JSON object: "{\"id_1\":AB123,\"id_2\":DE456}".

Max length: 128 characters (see data formats for details)

The unique identifier of the object.

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.

Unix timestamp (UTC) of the date and time the object was created.

Returned values: CREATED, SUCCEEDED, FAILED

The status of the transaction.

The unique identifier of the user at the source of the transaction. In a conversion, both the debited and credited wallets are owned by the author.

The unique identifier of the debited wallet (in the sell currency).

The unique identifier of the credited wallet (in the buy currency).

The code indicating the result of the operation. This information is mostly used to <a href="/errors/codes">handle errors</a> or for filtering purposes.

The explanation of the result code.

Unix timestamp (UTC) of the date and time the status changed to SUCCEEDED, indicating that the transaction occurred. The statuses CREATED and FAILED return an ExecutionDate of null.

Max. length: 255 characters

Custom data that you can add to this object, such as unique identifiers in your system. To store multiple values, you can serialize them into a single string, for example a JSON object: "{\"id_1\":AB123,\"id_2\":DE456}".