Skip to main content

​
Description

The Bizum PayIn object allows your platform to process Bizum payments. There are two Bizum flows, both using the same endpoint with different payloads:
  • Phone – If Phone is sent, the ReturnURL is ignored and RedirectURL is not returned because no redirection is necessary: the user receives a push notification from the Bizum app asking them to authenticate. In Sandbox, the RedirectURL is returned in all cases, because it is the only way to complete the transaction.
  • Redirect – If Phone is not sent, then ReturnURL is required and you must redirect the user to the RedirectURL in the response so they can enter their phone number themselves.
Read more about Bizum →

​
Attributes

​
string
Max length: 128 characters (see data formats for details)The unique identifier of the object.
​
string
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.
​
Unix timestamp
The date and time at which the object was created.
​
string
The unique identifier of the user at the source of the transaction.
​
object
Information about the debited funds.
​
object
Information about the credited funds (CreditedFunds = DebitedFunds - Fees).
​
object
Information about the fees.
​
string
Returned values: CREATED, SUCCEEDED, FAILEDThe status of the transaction.
​
string
The code indicating the result of the operation. This information is mostly used to handle errors or for filtering purposes.
​
string
The explanation of the result code.
​
Unix timestamp
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.
​
string
Returned values: PAYIN, TRANSFER, CONVERSION, PAYOUTThe type of the transaction.
​
string
Returned values: REGULAR, REPUDIATION, REFUND, SETTLEMENTThe 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.
​
string
The unique identifier of the credited wallet.
​
string
Default value: The unique identifier of the owner of the credited wallet.The unique identifier of the user whose wallet is credited.
​
string
Returned values: BIZUMThe type of pay-in.
​
string
Returned values: WEB, DIRECT, EXTERNAL_INSTRUCTIONThe type of execution for the pay-in.
​
string
Format: International E.164 standard (preceded by plus sign and country code, +34 in Spain); pattern: ^(\\+?34)?[6-9][0-9]{8}$The phone number of the end user to which the Bizum push notification is sent to authenticate the transaction.On Bizum, if the Phone parameter is sent, then RedirectURL is not returned and ReturnURL not required.
​
string
Max. length: 255 charactersThe URL to which the user is returned after the payment, whether the transaction is successful or not.
​
string
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.
​
string
Max. length: 10 characters; only alphanumeric and spacesCustom description to appear on the user’s bank statement along with the platform name. Different banks may show more or less information. See the Customizing bank statement references article for details.