Skip to content

Creation

Find in this article examples on how to create different types of wallets. Some wallets might require you contact Treezor to create them.

Regardless the type of Wallet created, the wallet.create webhook is sent upon creation.

Info icon

Information – Feature also available on the Dashboard

Wallets can also be managed via the Dashboard.

Payment Account Wallet

The Payment Account Wallet has a walletTypeId of 10. This type of wallet requires KYC validation of the associated User.

Mandatory parameters

Below are the necessary parameters to create a Payment Account Wallet.

AttributeTypeDescription
tariffId integerThe fees applied to the Wallet, as defined by your contract with Treezor. Usually required, but may have a default value set by Treezor.
walletTypeId integer10 for Payment Account Wallet.
userId integerThe unique identifier of the User who owns the Wallet.
currency stringThe currency of the Wallet. Can only be EUR.
eventName stringThe name of the Wallet.
code icon

API – Swagger documentation available

For a complete list of Wallet attributes, check the Wallets section of the Swagger.

Request

Here is the request to create a Wallet:

bash
curl -X POST {baseUrl}/v1/wallets \
	--header 'Authorization: Bearer {accessToken}' \
	--header 'Content-Type: application/json' \
	-d '{payload}'

Here is an example of {payload}:

json
{
	"walletTypeId":10,
	"tariffId":{tariffId},
	"userId":123456,
	"currency":"EUR",
	"eventName":"My Payment Account Wallet"
}

Returns a Wallet object, with its id. An IBAN (iban) and BIC (bic) are also automatically assigned and populated. You may create Virtual IBANs in a second step.

json
{
    "wallets": [
        {
            "walletId": 2605378,
            "walletTypeId": 10,
            "walletStatus": "VALIDATED",
            "codeStatus": 120005,
            "informationStatus": "",
            "walletTag": "",
            "userId": 100078924,
            "userLastname": "Alex",
            "userFirstname": "Oak",
            "jointUserId": 0,
            "tariffId": 396,
            "eventName": "Event_test",
            "eventAlias": "event-test-65aa83976d9df",
            "eventDate": "2024-01-26",
            "eventMessage": "",
            "eventPayinStartDate": "2024-01-19",
            "eventPayinEndDate": "0000-00-00",
            "contractSigned": 0,
            "bic": "TRZOFR21XXX",					// BIC automatically assigned to the Wallet
            "iban": "FR761679800001000012345678",	// IBAN automatically assigned to the Wallet
            "urlImage": "",
            "currency": "EUR",
            "createdDate": "2024-01-19 15:13:43",
            "modifiedDate": "0000-00-00 00:00:00",
            "payinCount": 0,
            "payoutCount": 0,
            "transferCount": 0,
            "solde": 0,
            "authorizedBalance": 0,
            "totalRows": 1,
            "country": "FR"
        }
    ]
}

Treezor also sends the wallet.create webhook.

Electronic Money Wallet

The Electronic Money Wallet has a walletTypeId of 9. This type of wallet doens't need KYC validation of the associated User.

Mandatory parameters

Below are the necessary parameters to create an Electronic Money Wallet.

AttributeTypeDescription
tariffId integerThe fees applied to the Wallet, as defined by your contract with Treezor. Usually required, but may have a default value set by Treezor.
walletTypeId integer9 for Electronic Money Wallet.
userId integerThe unique identifier of the User who owns the Wallet.
currency stringCurrency of the Wallet. Can only be EUR.
eventName stringThe Name of the Wallet.
code icon

API – Swagger documentation available

For a complete list of Wallet attributes, check the Wallets section of the Swagger.

Request

Here is the request to create a Wallet:

bash
curl -X POST {baseUrl}/v1/wallets \
	--header 'Authorization: Bearer {accessToken}' \
	--header 'Content-Type: application/json' \
	-d '{payload}'

Here is an example of {payload}:

json
{
	"walletTypeId":9,
	"tariffId":{tariffId},
	"userId":123456,
	"currency":"EUR",
	"eventName":"My Electronic Money Wallet"
}

Returns a Wallet object with its id. An IBAN (iban) and BIC (bic) are also automatically assigned and populated. You may create Virtual IBANs in a second step.

json
{
    "wallets": [
        {
            "walletId": 2605123,
            "walletTypeId": 0,
            "walletStatus": "VALIDATED",
            "codeStatus": 120005,
            "informationStatus": "",
            "walletTag": "",
            "userId": 100078924,
            "userLastname": "Alex",
            "userFirstname": "Oak",
            "jointUserId": 0,
            "tariffId": 396,
            "eventName": "Event_test",
            "eventAlias": "event-test-65aa83976d9df",
            "eventDate": "2024-01-26",
            "eventMessage": "",
            "eventPayinStartDate": "2024-01-19",
            "eventPayinEndDate": "0000-00-00",
            "contractSigned": 0,
            "bic": "TRZOFR21XXX",					// BIC automatically assigned to the Wallet
            "iban": "FR761679800001000012345678",	// IBAN automatically assigned to the Wallet
            "urlImage": "",
            "currency": "EUR",
            "createdDate": "2024-01-19 15:13:43",
            "modifiedDate": "0000-00-00 00:00:00",
            "payinCount": 0,
            "payoutCount": 0,
            "transferCount": 0,
            "solde": 0,
            "authorizedBalance": 0,
            "totalRows": 1,
            "country": "FR"
        }
    ]
}

Treezor also sends the wallet.create webhook.

Mirror or Technical Wallet

The Mirror or Technical Wallet has a walletTypeId of 13 and cannot be created manually.

Warning icon

Caution – Never use Wallet 13 for SEPA Transfers

Although Mirror and Technical Wallets have an IBAN, these IBAN should never be used to emit or receive SEPA Transfers.

Electronic Money Card

The Electronic Money Card type of wallet has a walletTypeId of 14 and cannot be created manually.

Warning icon

Caution – Never use Wallet 14 for SEPA Transfers

Although Mirror and Technical Wallets have an IBAN, these IBAN should never be used to emit or receive SEPA Transfers.