Get information about a customer's account used in an order
This is a method that Trustly will call on the merchant's system in order to send information about the account used in this order.
This notification is not enabled by default, please contact our support if you want to receive it.
KYC data in account notification
For additional personal data in account notification, merchant will need to use Trustly's Lean KYC service.
Restrictions in provided data may apply depending on merchant business and/or markets. For more information, reach out to your commercial contact at Trustly.
Example of an account notification, sent by the Trustly system to the merchants listening service at the specified NotificationURL:
{
"method": "account",
"params": {
"signature":"RI1PTmjTgr5Ig1p....AF7ejFUGxwKQ==",
"uuid": "258a2184-2842-b485-25ca-293525152425",
"data": {
"notificationid":"35673567",
"messageid":"453455465",
"orderid":"3473567567",
"accountid":"1234567890",
"verified":"1",
"attributes":
{
"clearinghouse":"SWEDEN",
"bank":"SEB",
"descriptor":"**** *084057",
"lastdigits":"084057"
}
}
},
"version": "1.1"
}
{
"method": "account",
"params": {
"signature":"RI1PTmjTgr5Ig1p....AF7ejFUGxwKQ==",
"uuid": "258a2184-2842-b485-25ca-293525152425",
"data": {
"notificationid":"35673567",
"messageid":"453455465",
"orderid":"3473567567",
"accountid":"1234567890",
"verified":"1",
"attributes":
{
"clearinghouse":"SWEDEN",
"bank":"SEB",
"descriptor":"**** *084057",
"lastdigits":"084057",
"personid": "SE198201019876",
"name": "John Doe",
"address": "Examplestreet 1",
"zipcode": "12345",
"city": "Examplecity"
}
}
},
"version": "1.1"
}
New parameters may be added to the notification in future versions of the API but current parameters will never be removed.
| Hash key | Description | Type | Example |
|---|---|---|---|
| messageid | Your unique ID of the order. | Text | 98348932 |
| orderid | The unique ID in our system for your messageid | Text | 87654567 |
| notificationid | Unique ID for this notification. Each notification must only be handled once in your system. | Text | 4567897654 |
| accountid | Unique ID for this account. | Text | 1234567890 |
| verified | Whether the account is verified or not. 0 for not verified, 1 for verified. | Text | 1 |
| attributes | Optional attributes for this notification. | Hash |
All attributes are not always present, the possible attributes are:
| Attribute name | Description | Type | Example |
|---|---|---|---|
| clearinghouse | The clearinghouse of the end user's bank account (i.e, the country where the bank account is held). Note: this is not necessarily the same as the end user's country of residence | Text | SWEDEN |
| bank | The bank for this account | Text | SEB |
| descriptor | A text that is safe to show the enduser for identifying the account. Do not parse this text since it will be a different format for different accounts. | Text | **** *084057 |
| lastdigits | The last digits of the bank account number. This can be used for matching against received KYC data from your manual routines. | Text | 084057 |
| personid | An ID that uniquely identifies the account holder. Note: The format of this field will for some countries look different than the example. | Text | SE198201019876 |
| name | The name of the account holder | Text | Joh Doe |
| address | The address of the account holder | Text | Examplestreet 1 |
| zipcode | The zipcode of the account holder | Text | 12345 |
| city | The city of the account holder | Text | Examplecity |
| directdebitmandate | 1 if a direct debit mandate exists for this account, 0 otherwise | Numeric | 1 |
Valid responses are:
| Status | Description |
|---|---|
| OK | The notification has been received. |
Example of OK reponse:
{
"result": {
"signature": "R9+hjuMqbsH0Ku ... S16VbzRsw==",
"uuid": "258a2184-2842-b485-25ca-293525152425",
"method": "account",
"data": {
"status": "OK"
}
},
"version":"1.1"
}