### Treezor API Postman Collection Guide Source: https://docs.treezor.com/llms.txt Quickly get started with the Treezor API using our Postman Collection, to explore common API use cases for rapid integration understanding. This guide explains how to set up and use the collection, providing step-by-step instructions and the official link. ```APIDOC ## Treezor API Postman Collection Guide ### Description Guide to setting up and using the Treezor API Postman Collection for exploring common API use cases and rapid integration. ### Endpoint /api-reference/postman.md ``` -------------------------------- ### SCA Mobile Abstraction Layer Source: https://docs.treezor.com/llms.txt Technical guide for configuration and usage of React abstraction layer of the Mobile SDK. Includes JavaScript code examples. ```APIDOC ## SCA Mobile Abstraction Layer ### Description Technical guide for configuration and usage of React abstraction layer of the Mobile SDK. Includes JavaScript code examples. ### Method GET ### Endpoint /guide/strong-customer-authentication/sdk-abstraction.md ``` -------------------------------- ### Verify users with Qualified eSignature (QES) Source: https://docs.treezor.com/llms.txt Technical guide for verifying users (KYC) with qualified eSignature (QES) via the Treezor API, including required parameters, request structure, and response examples. ```APIDOC ## Verify users with Qualified eSignature (QES) ### Description Technical guide for verifying users (KYC) with qualified eSignature (QES) via the Treezor API. Includes required parameters, request structure, and response examples. ### Endpoint /guide/user-verification/qes.md ``` -------------------------------- ### Create Wallets Source: https://docs.treezor.com/llms.txt Technical guide for creating payment accounts and electronic money wallets via the Treezor API, including required parameters, request structure, and response examples. ```APIDOC ## Create Wallets ### Description Technical guide for creating payment accounts and electronic money wallets via the Treezor API. Includes required parameters, request structure, and response examples. ### Endpoint /guide/wallets/creation.md ``` -------------------------------- ### Create KYC Documents Source: https://docs.treezor.com/llms.txt Technical guide for creating and managing KYC documents via the Treezor API, including required parameters, request structure, and response examples. ```APIDOC ## Create KYC Documents ### Description Technical guide for creating and managing KYC documents via the Treezor API. Includes required parameters, request structure, and response examples. ### Endpoint /guide/user-verification/documents.md ``` -------------------------------- ### Beneficiary Creation Payload Example Source: https://docs.treezor.com/guide/transfers/faking-operations.html Example JSON payload for creating a beneficiary. Includes user ID, name, address, IBAN, BIC, and usability for SCT. ```json { "userId": "{userId}", "name": "Sophie Weber", "nickName": "Test treezor", "address": "Test Bank address", "iban": "DE28503399002244668800", "bic": "TRZODEB2XXX", "usableForSct": true } ``` -------------------------------- ### Simulating SCA proof Source: https://docs.treezor.com/llms.txt Technical guide for generating an SCA Proof to test the SCA flow in Sandbox. ```APIDOC ## Simulating SCA proof ### Description Technical guide for generating an SCA Proof to test the SCA flow in Sandbox. ### Method POST ### Endpoint /guide/strong-customer-authentication/faking-operations.md ``` -------------------------------- ### Pre-review KYC Documents Source: https://docs.treezor.com/llms.txt Technical guide for pre-reviewing KYC documents via the Treezor API, including required parameters, request structure, and response examples. ```APIDOC ## Pre-review KYC Documents ### Description Technical guide for pre-reviewing KYC documents via the Treezor API. Includes required parameters, request structure, and response examples. ### Endpoint /guide/user-verification/documents-prereview.md ``` -------------------------------- ### Token Refresh Response Example Source: https://docs.treezor.com/guide/api-basics/authentication.html An example of a successful JSON response when refreshing an access token, including the new access token and its expiration time. ```json { "token_type": "Bearer", "expires_in": 3600, "access_token": "{accessToken}", "refresh_token": "{accessTokenAllowingForJwtRefresh}" } ``` -------------------------------- ### SEPA Recall Response Example Source: https://docs.treezor.com/guide/transfers/faking-operations.html Example JSON response when simulating a SEPA recall, returning the ID of the created Recall resource. ```json { "recalls": { "id": 10 } } ``` -------------------------------- ### Specify Desired Scopes Example Source: https://docs.treezor.com/guide/api-basics/authentication.html Demonstrates how to define user and desired scopes, illustrating the intersection that determines the returned scopes. ```javascript user_scopes = ['A', 'B', 'C']; desired_scopes = ['A', 'B', 'D']; ``` ```javascript returned_scopes = ['A', 'B']; ``` -------------------------------- ### User Live Verification Source: https://docs.treezor.com/llms.txt Technical guide for verifying users (KYC) with live verification via the Treezor API, including required parameters, request structure, and response examples. ```APIDOC ## User Live Verification ### Description Technical guide for verifying users (KYC) with live verification via the Treezor API. Includes required parameters, request structure, and response examples. ### Endpoint /guide/user-verification/live-verification.md ``` -------------------------------- ### SCTR Inst Recall Response Example Source: https://docs.treezor.com/guide/transfers/faking-operations.html Example JSON response for an SCTR Inst Recall simulation, returning the IDs for the SCTR Inst and the recall. ```json { "sctInstId": "c8457258-b18c-5647-9950-9ba3c99a9543", "recallrId": "f3f6a9c8-2f4b-5906-9ac7-2d908d04b681" } ``` -------------------------------- ### Verify Users with Video Conference Source: https://docs.treezor.com/llms.txt Technical guide for verifying users (KYC) with Video Conference via the Treezor API, including required parameters, request structure, and response examples. ```APIDOC ## Verify Users with Video Conference ### Description Technical guide for verifying users (KYC) with Video Conference via the Treezor API. Includes required parameters, request structure, and response examples. ### Endpoint /guide/user-verification/videoconf.md ``` -------------------------------- ### No Desired Scopes Example Source: https://docs.treezor.com/guide/api-basics/authentication.html Illustrates the scenario where no specific scopes are requested, resulting in the token covering all user scopes. ```javascript user_scopes = ['A', 'B', 'C']; ``` ```javascript returned_scopes = ['A', 'B', 'C']; ``` -------------------------------- ### Payout Simulation Response Example Source: https://docs.treezor.com/guide/overview/tinker.html A successful payout simulation returns information about the payout, including its ID and updated status. ```json { "payoutId": "12345", "payoutStatus": "VALIDATED", "payoutTypeId": 1, "payoutTag": "string" } ``` -------------------------------- ### SCTR Payload Example Source: https://docs.treezor.com/guide/transfers/faking-operations.html Example JSON payload for simulating an SCTR reception. Includes IBAN and amount. ```json { "iban": "FR7616798000010001726649397", "amount": 20 } ``` -------------------------------- ### CURL Request with Optional Scope Source: https://docs.treezor.com/guide/api-basics/authentication.html Example of a CURL request to obtain an OAuth token, showing how to optionally specify a scope. ```bash curl -X POST '{baseUrl}/oauth/token' \ --form 'grant_type="client_credentials"' \ --form 'client_id="{yourClientId}"' \ --form 'client_secret="{yourClientSecret}"' \ --form 'scope="admin"' # optional, for specific scope ``` -------------------------------- ### Payout Response Example Source: https://docs.treezor.com/guide/overview/tinker.html A successful payout request returns a Payout object, including its ID and status. ```json { "payoutId": "", "payoutTag": "", "payoutStatus": "PENDING", "payoutTypeId": , "payoutType": "", "walletId": , "payoutDate": "", "walletEventName": "", "userId": , "beneficiaryId": , "amount": "", "currency": "" // [...] some attributes are hidden } ``` -------------------------------- ### Send Funds Payload Example Source: https://docs.treezor.com/guide/overview/tinker.html The payload for sending funds includes wallet and beneficiary identifiers, validation ID, amount, and currency. ```json { "walletId": 826210, // required, the wallet to debit "beneficiaryId": {beneficiaryId}, // required, id of the beneficiary created in the previous step "beneficiaryValidationId": "{beneficiaryValidationId}", // required, id of the beneficiary validation created in the previous step "amount": 11.56, // required "currency": "EUR" // required } ``` -------------------------------- ### card.setpin Webhook Payload Example Source: https://docs.treezor.com/guide/cards/events.html This JSON payload represents the data received when a card's PIN is set or changed. It includes details about the card, user, wallet, and event specifics. This event is typically triggered by the /v1/cards/{cardId}/setPIN or /cards/{cardId}/setPIN API endpoints. ```json { "webhook": "card.setpin", "object": "card", "object_id": "333840683", "object_payload": { "cards": [ { "cardId": "333840683", "userId": "100150383", "walletId": "2677616", "walletCardtransactionId": "2678073", "mccRestrictionGroupId": null, "merchantRestrictionGroupId": null, "countryRestrictionGroupId": null, "eventName": "Event_test", "eventAlias": "event-test-65d48b7545d15", "publicToken": "105623117", "cardTag": "Event-test-card", "statusCode": "UNLOCK", "isLive": "1", "pinTryExceeds": "0", "maskedPan": "548821******7744", "embossedName": "ALEX OAK", "expiryDate": "2027-02-28", "CVV": "727", "startDate": "2024-02-24", "endDate": "0000-00-00", "countryCode": "FR", "currencyCode": "EUR", "deliveryTitle": "M", "deliveryLastname": "OAK", "deliveryFirstname": "ALEX", "deliveryAddress1": "33 ROSEWOOD LANE", "deliveryAddress2": "", "deliveryAddress3": "", "deliveryCity": "PARIS", "deliveryPostcode": "75000", "deliveryCountry": "FR", "mobileSent": "+33102030405", "limitsGroup": "TRZ-VL-001", "permsGroup": "TRZ-CU-012", "cardDesign": "8523", "virtualConverted": "1", "optionAtm": "0", "optionForeign": "1", "optionOnline": "1", "optionNfc": "1", "limitAtmYear": "0", "limitAtmMonth": "0", "limitAtmWeek": "2000", "limitAtmDay": "1000", "limitAtmAll": "0", "limitPaymentYear": "0", "limitPaymentMonth": "0", "limitPaymentWeek": "3000", "limitPaymentDay": "2000", "paymentDailyLimit": "500.00", "restrictionGroupLimits": null, "limitPaymentAll": "0", "totalAtmYear": "0", "totalAtmMonth": "0", "totalAtmWeek": null, "totalAtmDay": null, "totalAtmAll": "0", "totalPaymentYear": "0", "totalPaymentMonth": "0", "totalPaymentWeek": null, "totalPaymentDay": null, "totalPaymentAll": "0", "createdBy": "323252", "createdDate": "2024-02-20 15:13:11", "modifiedBy": "323252", "modifiedDate": "2024-02-20 15:21:17", "cancellationNumber": null, "physical": "0", "logoId": "", "logoBackId": "", "packageId": "", "customizedInfo": null, "letterCustomizedInfo": "", "freeCustomizedInfo": "", "deliveryMethod": "1", "pinMailer": "1", "batchDeliveryId": "1", "sendToParent": "1", "isTemporary": false } ] }, "webhook_created_at": 17084388772481, "webhook_id": "2d53e374-0385-438d-a661-13533c03d0f7", "object_payload_signature": "++++++++++++++++++++++++++++++++++++++++++++=" } ``` -------------------------------- ### Simulate Payout SDDR - Response JSON Source: https://docs.treezor.com/guide/transfers/faking-operations.html Example response when simulating a Payout SDDR with 'executeAfterParse' set to 1. Indicates the SDDR creation and batch execution launch. ```json { "messages":[ "[Simulation] [POST /payoutSddr] CORE SDDR created", "[Simulation] batchExecuteSddr() launched" ] } ``` -------------------------------- ### Update Wallets Source: https://docs.treezor.com/llms.txt Technical guide for updating wallets via the Treezor API, including required parameters, request structure, and response examples. ```APIDOC ## Update Wallets ### Description Technical guide for updating wallets via the Treezor API. Includes required parameters, request structure, and response examples. ### Endpoint /guide/wallets/modification.md ``` -------------------------------- ### Introduction to Wallets and accounts Source: https://docs.treezor.com/llms.txt Get a foundational understanding of Treezor wallet and account types, and their compatible functionalities. Includes key attributes, JSON structure, and related endpoints list. ```APIDOC ## Introduction to Wallets and accounts ### Description Get a foundational understanding of Treezor wallet and account types, and their compatible functionalities. Includes key attributes, JSON structure, and related endpoints list. ### Endpoint /guide/wallets/introduction.md ``` -------------------------------- ### Simulate Payout Creation Source: https://docs.treezor.com/guide/transfers/faking-operations.html This endpoint allows you to create a payout in the sandbox environment. It requires details such as payout type, wallet ID, beneficiary ID, amount, and currency. ```APIDOC ## POST /v1/payouts ### Description Creates a payout in the sandbox environment. ### Method POST ### Endpoint `/v1/payouts` ### Request Body - **payoutTypeId** (integer) - Required - The type of payout. - **walletId** (integer) - Required - The ID of the wallet from which the payout will be made. - **beneficiaryId** (integer) - Required - The ID of the beneficiary. - **beneficiaryValidationId** (string) - Optional - The ID for beneficiary validation. - **amount** (number) - Required - The payout amount. - **currency** (string) - Required - The currency of the payout (e.g., EUR). ### Request Example ```json { "payoutTypeId": 3, "walletId": {walletId}, "beneficiaryId": {beneficiaryId}, "beneficiaryValidationId": "{beneficiaryValidationId}", "amount": 800.00, "currency": "EUR" } ``` ### Response #### Success Response (200) Returns a Payout object. #### Response Example ```json { "payouts": [ { "payoutId": "8929329c-b4a5-4bb9-b792-0e9e9d98xxxa", "payoutTag": "", "payoutStatus": "PENDING", "payoutTypeId": 3, "payoutType": "Instant Credit Transfer", "walletId": 3059736, "payoutDate": "2024-06-26 10:15:17", "walletEventName": "Name of the Wallet", "walletAlias": "name-of-the-wallet-667bcd66d546b", "userFirstname": "Alex", "userLastname": "Oak.validated", "userId": 965725, "beneficiaryId": 40963, "uniqueMandateReference": "", "bankaccountIBAN": "FR761679800001000030XXXXXX3", "label": "", "amount": "800.00", "currency": "EUR", "partnerFee": "0", "createdDate": "2024-06-26 10:15:17", "modifiedDate": "", "virtualIbanId": null, "virtualIbanReference": null, "codeStatus": "160001", "informationStatus": "PENDING", "supportingFileLink": "", "endToEndId": "2dbb81b26db94db3b530988b4189aad7", "reasonCode": null, "reasonDescription": null, "internationalBeneficiaryId": null, "quotationId": null, "metadata": null, "totalRows": null, "beneficiaryValidationId": null } ] } ``` ``` -------------------------------- ### Request User KYC Review Source: https://docs.treezor.com/llms.txt Technical guide for making a KYC request via the Treezor API, including required parameters, request structure, and response examples. ```APIDOC ## Request User KYC Review ### Description Technical guide for making a KYC request via the Treezor API. Includes required parameters, request structure, and response examples. ### Endpoint /guide/user-verification/kyc-request.md ``` -------------------------------- ### Making an API Request with Bearer Token Source: https://docs.treezor.com/guide/api-basics/authentication.html Demonstrates how to make a GET request to an API endpoint using a Bearer token for authentication. Ensure the 'Authorization' header is correctly formatted. ```bash curl -X GET '{baseUrl}/example/of/endpoint' \ --header 'Authorization: Bearer {accessToken}' \ --header 'Content-Type: application/json' ``` -------------------------------- ### Securing Endpoints Source: https://docs.treezor.com/llms.txt Guide for declaring your end users actions (passive session, active session, or invididual), whether they are made with Treezor endpoints or not. Includes request and examples for the external operation declaration. ```APIDOC ## Securing Endpoints ### Description Guide for declaring your end users actions (passive session, active session, or invididual), whether they are made with Treezor endpoints or not. Includes request and examples for the external operation declaration. ### Method POST ### Endpoint /guide/strong-customer-authentication/securing-endpoints.md ``` -------------------------------- ### Create a Wallet Source: https://docs.treezor.com/guide/overview/tinker.html Creates a new wallet (payment account) for a specified user. The response includes the wallet details, its ID, and its IBAN. ```APIDOC ## POST /v1/wallets ### Description Creates a new wallet, represented as a payment account, and associates it with a previously created user. The response provides the wallet's ID and IBAN. ### Method POST ### Endpoint `/v1/wallets` ### Parameters #### Request Body - **walletTypeId** (integer) - Required - Specifies the type of wallet. `10` indicates a Payment Account Wallet. - **userId** (integer) - Required - The ID of the user to whom the wallet will be attached. - **currency** (string) - Required - The currency of the wallet (e.g., "EUR"). - **eventName** (string) - Required - A name or identifier for the wallet. ### Request Example ```json { "walletTypeId": 10, "userId": 1545392, "currency": "EUR", "eventName": "AO's Account" } ``` ### Response #### Success Response (200) Returns a Wallet object, including its `walletId` and ready-to-use `iban`. #### Response Example ```json { "wallets": [ { "walletId": 2702198, "walletTypeId": 10, "walletStatus": "VALIDATED", "codeStatus": 120005, "informationStatus": "", "walletTag": "", "userId": 1545392, "userLastname": "Oak.validated", "userFirstname": "Alex", "jointUserId": 0, "tariffId": 136, "eventName": "AO's Account", "eventAlias": "ao-s-account-65df2ab48f029", "eventDate": "2024-03-06", "eventMessage": "", "eventPayinStartDate": "2024-02-28", "eventPayinEndDate": "0000-00-00", "contractSigned": 0, "bic": "TRZOFR21XXX", "iban": "FR7616798000010000270219811", "urlImage": "", "currency": "EUR", "createdDate": "2024-02-28 13:44:36", "modifiedDate": "0000-00-00 00:00:00", "payinCount": 0, "payoutCount": 0, "transferCount": 0, "solde": 0, "authorizedBalance": 0, "totalRows": 1, "country": "FR" } ] } ``` ``` -------------------------------- ### SCA Mobile SDK Source: https://docs.treezor.com/llms.txt Technical guide for using the Mobile SDK for Strong Customer Authentication (SCA). Includes the links to download the SDK in multiple languages, for both sandbox and production. ```APIDOC ## SCA Mobile SDK ### Description Technical guide for using the Mobile SDK for Strong Customer Authentication (SCA). Includes the links to download the SDK in multiple languages, for both sandbox and production. ### Method GET ### Endpoint /guide/strong-customer-authentication/sdk.md ``` -------------------------------- ### SCA Wallet life cycle Source: https://docs.treezor.com/llms.txt Technical guide for managing the SCA Wallets life cycle, such as locking, unlocking, and changing passcodes or PINs. Includes required parameters, request structure, and response examples. ```APIDOC ## SCA Wallet life cycle ### Description Technical guide for managing the SCA Wallets life cycle, such as locking, unlocking, and changing passcodes or PINs. Includes required parameters, request structure, and response examples. ### Method PUT ### Endpoint /guide/strong-customer-authentication/sca-wallet-lifecycle.md ``` -------------------------------- ### Enrolled Devices Source: https://docs.treezor.com/llms.txt Technical guide to retrieve the SCA Wallets created from the Mobile SDK or the Web Native solution via the Treezor API. Includes required parameters, request structure, and response examples. ```APIDOC ## Enrolled Devices ### Description Technical guide to retrieve the SCA Wallets created from the Mobile SDK or the Web Native solution via the Treezor API. Includes required parameters, request structure, and response examples. ### Method GET ### Endpoint /guide/strong-customer-authentication/enrolled-devices.md ``` -------------------------------- ### Create a User Source: https://docs.treezor.com/guide/overview/tinker.html Creates a new physical user in the system. This user can then be used to offer banking services. ```APIDOC ## POST /v1/users ### Description Creates a new physical user. This is a prerequisite for offering banking services to end-users. ### Method POST ### Endpoint /v1/users ### Parameters #### Request Body - **userTypeId** (integer) - Required - 1 for Physical User. - **specifiedUSPerson** (integer) - Required. - **title** (string) - Optional. - **firstname** (string) - Optional. - **lastname** (string) - Optional. - **email** (string) - Required - Must be unique. - **address1** (string) - Required - Needed to create a Card later. - **phone** (string) - Required - Needed to create a Card later. ### Request Example ```json { "userTypeId": 1, "specifiedUSPerson": 0, "title": "MX", "firstname": "Alex", "lastname": "Oak.userStatusValidated", "email": "aoak@example.com", "address1": "101 Willow lane", "phone": "+33102030405" } ``` ### Response #### Success Response (200) Returns the newly created User object, including its unique `id`. ``` -------------------------------- ### Cross Device SCA Source: https://docs.treezor.com/llms.txt Technical guide for implementing strong customer authentication for web applications, by delegating the generation of SCA proofs to another enrolled device. Includes required parameters, request structure, and response examples. ```APIDOC ## Cross Device SCA ### Description Technical guide for implementing strong customer authentication for web applications, by delegating the generation of SCA proofs to another enrolled device. Includes required parameters, request structure, and response examples. ### Method POST ### Endpoint /guide/strong-customer-authentication/cross-device.md ``` -------------------------------- ### SCA Authentication Source: https://docs.treezor.com/llms.txt Technical guide for authenticating in the name of your end user for SCA. Learn how to obtain your SCA proof (JWS) and use it to request a JWT to authenticate. Includes required parameters, request structure, and response examples. ```APIDOC ## SCA Authentication ### Description Technical guide for authenticating in the name of your end user for SCA. Learn how to obtain your SCA proof (JWS) and use it to request a JWT to authenticate. Includes required parameters, request structure, and response examples. ### Method POST ### Endpoint /guide/strong-customer-authentication/authenticating.md ``` -------------------------------- ### KYC Simulation Source: https://docs.treezor.com/llms.txt Learn how to update the user KYC status within the Sandbox environment for development and API integration testing. ```APIDOC ## KYC Simulation ### Description Learn how to update the user KYC status within the Sandbox environment for development and API integration testing. ### Endpoint /guide/user-verification/faking-operations.md ``` -------------------------------- ### SEPA Recall Payload Example Source: https://docs.treezor.com/guide/transfers/faking-operations.html Example JSON payload for simulating a SEPA recall. It includes identifiers for the recall, status, transaction, and reason code. ```json { "cxlId": "401", "statusId": 2, "sctrId": 401, "txId": "401", "reasonCode": "TECH", "createPayinRefund": true } ``` -------------------------------- ### SCTR Inst Payload Example Source: https://docs.treezor.com/guide/transfers/faking-operations.html Example JSON payload for simulating an SCTR Inst reception. Includes recipient name, BIC, IBAN, currency, and amount. ```json { "name": "M. Firstname LASTNAME", // Name of the recipient (User) "bic": "TRZOFR21XXX", // BIC of the recipient (User) "iban": "FR76167980019999999999999", // IBAN of the recipient (Wallet) "currency": "EUR", "amount": 10.0 } ``` -------------------------------- ### Simulate Payin SDDE - Response JSON Source: https://docs.treezor.com/guide/transfers/faking-operations.html Example response for a simulated SEPA Direct Debit emission (SDDE). It returns the Payin object with details of the credited transaction. ```json { "payins": [ { "payinId": "", "payinTag": "", "payinStatus": "", "codeStatus": "", "informationStatus": "", "walletId": "", // id of the wallet to credit "userId": "", "amount": "", "currency": "", "[...]" // some attributes are hidden } ] } ``` -------------------------------- ### Get User KYC Status Source: https://docs.treezor.com/guide/overview/tinker.html After updating a user, make a GET /v1/users/{userId} call to retrieve the User object and check the updated `kycLevel` and `kycReview` attributes. ```json { "userId": 1545392, "kycLevel": "2", "kycReview": "2" // [...] some attributes are hidden } ``` -------------------------------- ### Create Physical User Request Source: https://docs.treezor.com/guide/overview/tinker.html This cURL command demonstrates how to create a physical user. It includes the necessary Authorization header and Content-Type, along with a JSON payload. ```bash curl -X POST '{baseUrl}/v1/users' \ --header 'Authorization: Bearer {accessToken}' \ --header 'Content-Type: application/json' \ -d '{payload}' ``` -------------------------------- ### Wallet Simulation Source: https://docs.treezor.com/llms.txt Learn how to update and manage Treezor Wallet statuses within the Sandbox environment for development and API integration testing. ```APIDOC ## Wallet Simulation ### Description Learn how to update and manage Treezor Wallet statuses within the Sandbox environment for development and API integration testing. ### Endpoint /guide/wallets/faking-operations.md ``` -------------------------------- ### SCTR Inst Recall Payload Example Source: https://docs.treezor.com/guide/transfers/faking-operations.html Example JSON payload for simulating an SCTR Inst Recall. Includes the SCTR Inst ID, demand date, reason code, and optional additional information. ```json { "sctInstId": "1380aeca-963b-5497-aef4-a9532086653c", "demandDate": "2022-11-24", "reasonCode": "FRAD", "additionalInformation": "" } ``` -------------------------------- ### JSON Payload for Beneficiary Validation (NOAP) Source: https://docs.treezor.com/guide/transfers/faking-operations.html Example JSON payload for beneficiary validation when no account is found. ```json { "beneficiaryName": "Sophy Weber", "beneficiaryIBAN": "DE82503399000000062899" } ```