# Wallet-to-Wallet Transfers
You can transfers funds from Wallet to Wallet, without using the SEPA network, offering much quicker transfers.
Transfers are instantaneous, are available 24/7 and can be scheduled (see Scheduled Payments). They send transfer.create webhooks and are mapped to Transfers objects.
Prerequisites – Funds can be transferred if:
- Both Wallets are active and belong to your Treezor environment
- The Authorized Balance of the debited Wallet is sufficient
- The amount is within the sender's KYC limits and greater or equal to €0,05
# Creation
Information – SCA depends on the user the credited Wallet belong to (beneficiaryWalletId)
- Per session – If the credited Wallet belongs to the user initiating the transfer
- Per operation – If the credited Wallet doesn't belong to the user initiating the transfer
# Parameters
| Attribute | Type | Description |
|---|---|---|
walletId | integer | The unique identifier of the Wallet to be debited. |
beneficiaryWalletId | integer | The unique identifier of the Wallet to be credited. |
amount | float | The amount of the Transfer. |
currency | string | The currency of the Transfer. Both Wallets must have the same currency. As of today, can only be EUR. |
transferTypeId | integer | The type of Transfer, which can be:
|
transferTag | string | Custom attribute to use as you see fit. Learn more in the Object tags article. |
label | string | Custom data. |
Best practice – Make good use of the transferTypeId parameter
Using the transferTypeId=3 when billing your customers for your services is strongly recommended. Improper use of transferTypeId prevents you from displaying fees on Account Statements.
API – Swagger documentation available
For a complete list of Transfer attributes, check the Transfers section of the Swagger.
# Request example
Here is a {payload} example:
Returns the Transfer object if successful:
A transfer.create webhooks is also sent.
Note – Treezor sends 1 webhook per transfer-related event
Treezor doesn't send a webhook per Wallet (e.g., one for the debited Wallet and another for the credited Wallet). Ony one transfer.create and transfer.update webhook is sent per transfer-related event.
# Endpoints
| Endpoint | Description | Scope |
|---|---|---|
/v1/transfers | Search Transfers | read_only |
/v1/transfer | Create a Transfers | read_write |
/v1/transfers/{transferId} | Retrieve a Transfer using its id | read_only |
/v1/transfers/{transferId} | Delete a Transfer using its id | read_write |