Create a Payconiq PayIn

POST

/v2.01/:ClientId/payins/payment-methods/payconiq

POST

/v2.01/:ClientId/payins/payment-methods/payconiq

$ curl -X POST https://api.sandbox.mangopay.com/v2.01/ClientId/payins/payment-methods/payconiq \
>      -H "Authorization: Bearer <token>" \
>      -H "Content-Type: application/json" \
>      -d '{
>   "body": {
>     "AuthorId": "user_m_01J18HZSACR1EMYNY1TBS8KTJD",
>     "CreditedWalletId": "wlt_m_01J18J1SQGG6KXNM3F8GD674TP",
>     "DebitedFunds": {
>       "Currency": "EUR",
>       "Amount": 1000
>     },
>     "Fees": {
>       "Currency": "EUR",
>       "Amount": 0
>     },
>     "Country": "BE",
>     "StatementDescriptor": "Example123",
>     "Tag": "Created using the Mangopay API Postman collection",
>     "ReturnURL": "http://example.com"
>   }
> }'

200Successful

1 {
2   "Id": "wt_706087f1-d1df-48a9-9d15-e8c603457d64",
3   "Tag": "Created using the Mangopay API Postman collection",
4   "CreationDate": 1720095972,
5   "AuthorId": "user_m_01J18HZSACR1EMYNY1TBS8KTJD",
6   "DebitedFunds": {
7     "Currency": "EUR",
8     "Amount": 1000
9   },
10   "CreditedFunds": {
11     "Currency": "EUR",
12     "Amount": 1000
13   },
14   "Fees": {
15     "Currency": "EUR",
16     "Amount": 0
17   },
18   "Status": "CREATED",
19   "ResultCode": null,
20   "ResultMessage": null,
21   "ExecutionDate": null,
22   "Type": "PAYIN",
23   "Nature": "REGULAR",
24   "CreditedWalletId": "wlt_m_01J18J1SQGG6KXNM3F8GD674TP",
25   "CreditedUserId": "user_m_01J18HZSACR1EMYNY1TBS8KTJD",
26   "PaymentType": "PAYCONIQ",
27   "ExecutionType": "WEB",
28   "ReturnURL": "http://example.com?transactionId=wt_706087f1-d1df-48a9-9d15-e8c603457d64",
29   "RedirectURL": "https://r2.girogate.de/payconiq/T1146/I?tx=1207176177&rs=8OHbVocjQQa4OIcB4o31BgQBw7c45bXK&cs=76745cafd862d134ce7be068a029c71368ff5e22339379d72780845cee02a10f",
30   "StatementDescriptor": "Example123",
31   "Country": "BE",
32   "DeepLinkURL": "https://PAYCONIQ.COM/PAY/2/F8B4348C390A925F00D0682C?returnUrl=https%3A%2F%2Fr2.giro[…]436a10f4077908aa014795ba528a622315b2bada9f1ddc33e097c2fe5d9f5b",
33   "QRCodeURL": "https://portal.payconiq.com/qrcode?c=https%3A%2F%2Fpayconiq.com%2Fpay%2F2%2Ff8b4348c390a925f00d0682c"
34 }

Deprecated – Payconiq discontinued from Dec 4, 2025

Following its acquisition by the European Payments Initiative (EPI), the Payconiq brand and services are being phased out (read more on Payconiq’s website).

The timeline is as follows:

Dec 4, 2025 - Payconiq pay-ins attempted after 12:00 noon CET will fail
Dec 31, 2025 - Final day for processing pay-in refunds
Jan 1, 2026 - Refunds possible using payouts (see guide)

Platforms using Payconiq are invited to integrate Bancontact, which allows users to continue paying with their Payconiq by Bancontact mobile app via the DeepLinkURL.

Note – Timeout after 1 hour

The Payconiq payment session lasts for 1 hour, at which point the pay-in fails automatically if no action has been taken by the user.

Create a Payconiq PayIn

<Warning icon="fa-regular fa-triangle-exclamation"> **Deprecated – Payconiq discontinued from Dec 4, 2025** Following its acquisition by the European Payments Initiative (EPI), the Payconiq brand and services are being phased out (<a href="https://www.payconiq.be/en/payconiq-evolves" target="_blank">read more</a> on Payconiq's website). The timeline is as follows: - Dec 4, 2025 - [Payconiq pay-ins](/api-reference/payconiq/create-payconiq-payin) attempted after **12:00 noon CET** will fail - Dec 31, 2025 - Final day for processing [pay-in refunds](/api-reference/refunds/create-refund-payin) - Jan 1, 2026 - Refunds possible using payouts ([see guide](/guides/payment-methods/payconiq#refunds-from-jan-1,-2026)) Platforms using Payconiq are invited to integrate [Bancontact](https://www.notion.so/guides/payment-methods/bancontact), which allows users to continue paying with their Payconiq by Bancontact mobile app via the `DeepLinkURL`. </Warning> <Note icon="fa-regular fa-circle-info"> **Note – Timeout after 1 hour** The Payconiq payment session lasts for 1 hour, at which point the pay-in fails automatically if no action has been taken by the user. </Note> Create a Payconiq PayIn

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

If your platform is using a proxy to take SCA-triggering action on behalf of users, you also need to integrate mTLS authentication and use the api-mtls base URL.

Bearer authentication of the form `Bearer <token>`, where token is your auth token. If your platform is using a [proxy](/guides/sca/proxy-management) to take SCA-triggering action on behalf of users, you also need to integrate [mTLS authentication](/guides/sca/platform) and use the `api-mtls` base URL.

Path parameters

ClientIdstringRequired

Platform's API account identifier, associated with the API key.

Request

This endpoint expects an object.

AuthorIdstringRequired

The unique identifier of the user at the source of the transaction.

DebitedFundsobjectRequired

Information about the debited funds.

FeesobjectRequired

Information about the fees.

CreditedWalletIdstringRequired

The unique identifier of the credited wallet.

ReturnURLstringRequired

Max. length: 255 characters

The URL to which the user is returned after the payment, whether the transaction is successful or not.

CountrystringRequired

Allowed values: BE, LU

The country of residence of the user.

TagstringOptional

Max. length: 255 characters

Custom data that you can add to this object.

StatementDescriptorstringOptional

Max. length: 10 characters; only alphanumeric and spaces

Custom 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.

Response

Success

Idstring

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

The unique identifier of the object.

Tagstring

Max. length: 255 characters

Custom data that you can add to this object.

CreationDateinteger

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

AuthorIdstring

The unique identifier of the user at the source of the transaction.

DebitedFundsobject

Information about the debited funds.

CreditedFundsobject

Information about the credited funds (CreditedFunds = DebitedFunds - Fees).

Feesobject

Information about the fees.

Statusstring

Returned values: CREATED, SUCCEEDED, FAILED

The status of the transaction.

ResultCodestring

The code indicating the result of the operation. This information is mostly used to handle errors or for filtering purposes.

ResultMessagestring

The explanation of the result code.

ExecutionDateinteger

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.

Typestring

Returned values: PAYIN, TRANSFER, CONVERSION, PAYOUT

The type of the transaction.

Naturestring

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.

CreditedWalletIdstring

The unique identifier of the credited wallet.

CreditedUserIdstring

Default value: The unique identifier of the owner of the credited wallet.

The unique identifier of the user whose wallet is credited.

PaymentTypestring

Returned values: PAYCONIQ

The payment type of the pay-in.

ExecutionTypestring

Returned values: WEB

The execution type of the pay-in.

ReturnURLstring

Max. length: 255 characters

The URL to which the user is returned after the payment, whether the transaction is successful or not.

RedirectURLstring

The URL to which to redirect the user to complete the payment on a hosted page showing the QR code and Payconiq by Bancontact branding and instructions.

Note: In Sandbox, this value redirects to Mangopay’s web-based simulator.

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.

StatementDescriptorstring

Max. length: 10 characters; only alphanumeric and spaces

Countrystring

Returned values: BE, LU

The country of residence of the user.

DeepLinkURLstring

The mobile URL to which to redirect the user to complete the payment in an app-to-app flow.

Note: In Sandbox, this value is a placeholder: the RedirectURL must be used to complete the payment using Mangopay’s web-based simulator.

QRCodeURLstring

The URL of a page containing only the QR code which you can use in your payment experience.

You can lightly customize the QR code’s format, size, and color by adding query parameters to the QRCodeURL before redirecting the user. See the Payconiq guide for details.

Note: In Sandbox, this value is a placeholder. The RedirectURL must be used to complete the payment using Mangopay’s web-based simulator.