Recipient Flows
Creating a recipient
The recipient is a person or institution who is the ultimate beneficiary of a transfer. Requirements for Recipient will vary depending on their type.
The 3.2. [EntryPoint] Create the recipient for the quote
process handles this flow.
Process payload
{
"recipientBody": {
"currency": "GBP",
"type": "sort_code",
"profile": 14733,
"ownedByCustomer": true,
"accountHolderName": "Ann Johnson",
"details": {
"email": "ana_Jhons@mail.com",
"legalType": "PRIVATE",
"sortCode": "231470",
"accountNumber": "28821822"
}
},
"token": "e0172d1b-e17f-40d2-94af-784fc59da298",
"language": "es"
}
Parameter | Type | Description | Required |
---|---|---|---|
recipientBody | object | An object holding details about the recipient. | Yes |
recipient.type | string | This field’s type is based on the currency. For instance for EUR, the type will be iban , for USD the type can be ABA , and for GBP the type can be sort_code . | Yes |
recipient.profile | string | The recipient’s profile ID. | Yes |
recipient.ownedByCustomer | boolean | A boolean value to check if the recipient’s account is owned by the transferer. Values can be only true or false . | Yes |
recipient.accountHolderName | string | The full name attached to the recipient’s account. | Yes |
recipient.details | object | An object holding the recipient’s personal details. | Yes |
recipient.details.email | string | The recipient’s email address. | Yes |
recipient.details.legalType | string | The type of legal entity that the recipient is Private for an individual and Business for a business. | Yes |
recipient.details.sortCode | string | The sort code is a six-digit number that identifies a bank. | Yes |
recipient.details.accountNumber | string | The recipient’s account number. | Yes |
token | string | The client’s token, which is retrieved in the user creation and login process. | Yes |
language | string | The language code, which can be found in Wise’s Language Support page. | Yes |
Get the recipients list
Each user has their own list of recipients associated with their Wise profile. This process retrieves the list of all recipients filtered by profileId
.
The 3.2.1. [EntryPoint] Get recipient list
process handles this flow.
Process payload
{
"profileId": 14733,
"token": "e0581691-4e43-474f-88c9-f2583027608b"
}
Parameter | Type | Description | Required |
---|---|---|---|
profileId | integer | The client’s profile ID, which is retrieved in the user creation and login process. | Yes |
token | string | The client’s token, which is retrieved in the user creation and login process. | Yes |
Get recipient account info by ID
The response to this flow includes a hash of a recipient, which can be used to track if the recipient details changes. The hash will remain constant unless the recipient’s name or the information in the details object changes.
The 3.2.2. [EntryPoint] Get recipient account info by id - v2
process handles this flow.
Process payload
{
"accountId": "148165674",
"token": "e0581691-4e43-474f-88c9-f2583027608b"
}
Parameter | Type | Description | Required |
---|---|---|---|
accountId | string | The client’s account ID. | Yes |
token | string | The client’s token, which is retrieved in the user creation and login process. | Yes |
Deleting a recipient
A recipient can be deleted by changing their status to inactive. Only active recipients can be deleted and a recipient cannot be reactivated; however, a new recipient can be created with the same details.
The 3.2.6. [EntryPoint] Delete recipient
process handles this flow.
Process payload
{
"accountId": "148165674",
"token": "e0581691-4e43-474f-88c9-f2583027608b"
}
Parameter | Type | Description | Required |
---|---|---|---|
accountId | string | The client’s account ID. | Yes |
token | string | The client’s token, which is retrieved in the user creation and login process. | Yes |
Creating a refund recipient
A refund recipient is a person or institution that will receive a refund transfer from Wise. The process payload for creating refund recipients will differ depending on the source currency.
The 3.2.4 [EntryPoint] Create refund recipient - v2
process handles this flow.
Process payload
{
"refundRecipientBody": {
"currency": "GBP",
"country": "GB",
"type": "sort_code",
"profile": 14733,
"legalEntityType": "PERSON",
"name": {
"fullName": "Ann Johnson"
},
"details": {
"sortCode": "231470",
"accountNumber": "28821822"
}
},
"token": "e0581691-4e43-474f-88c9-f2583027608b"
}
Parameter | Type | Description | Required |
---|---|---|---|
refundRecipientBody | object | An object containing information about the recipient that will receive a refund. | Yes |
refundRecipientBody.currency | string | The three letter currency code for the recipient’s account. | Yes |
refundRecipientBody.country | string | The two letter country code for the country. | Yes |
refundRecipientBody.profile | integer | The profile ID of the recipient. | Yes |
refundRecipientBody.legalEntityType | string | The type of legal entity. In most instances the value will be PERSON for an indivdual. | Yes |
refundRecipientBody.name.fullName | string | The full name of the recipient that will receive a refund. | Yes |
sortCode | string | The sort code is a six-digit number that identifies a bank. | Yes |
refundRecipientBody.details.sortCode | string | The sort code is a six-digit number that identifies a bank. | Yes |
refundRecipientBody.details.accountNumber | string | The refund recipient’s account number. | Yes |
token | string | The client’s token, which is retrieved in the user creation and login process. | Yes |
Get the receipt PDF
This process allows you to download the transfer confirmation receipt, in PDF format, for transfers that are have the outgoing_payment_sent
status.
The 3.2.5. [EntryPoint] Get Receipt PDF - v1
process handles this flow.
Process payload
{
"transferId": "49511866",
"token": "e0581691-4e43-474f-88c9-f2583027608b"
}
Parameter | Type | Description | Required |
---|---|---|---|
transferId | string | The transfer ID, which is retrieved in the transfer creation flow. | Yes |
token | string | The client’s token, which is retrieved in the user creation and login process. | Yes |
Patching quotes with recipient information
All quotes should be updated with the recipient data to retrieve the correct payment options, prices, and the estimated delivery time. This is due to the different costs charged by different payment networks that may be used by Wise to send currencies to some countries. For more information, see the quotes update endpoint in the Wise documentation.
The 3.3. [EntryPoint] Patch Quote with recipient information
process handles this flow.
Process payload
{
"profileId": 14733,
"quoteId": "e2451439-ff94-4146-9ff4-b6e1d65bb3cb",
"recipientId": 147774783,
"token": "e0581691-4e43-474f-88c9-f2583027608b"
}
Parameter | Type | Description | Required |
---|---|---|---|
profileId | integer | The client’s profile ID, which is retrieved in the user creation and login process. | Yes |
quoteId | string | The quote ID, which is retrieved in the quote creation process. | Yes |
recipientId | integer | The recipient ID, which is retrieved from the recipient creation process. | Yes |
token | string | The client’s token, which is retrieved in the user creation and login process. | Yes |