Multi API v3.54.0
Changes in End Customer onboarding
New FI T&Cs agreement onboarding screen
Onboarding flows for all new end customers will change to require an updated method of recording agreement to financial institution terms and conditions (FI T&Cs).
All ConsumersConsumers Individual persons who can be onboarded as identities on Weavr. Consumer identities represent individual customers and require Know Your Customer (KYC) verification. For consumers, the card owner and card assignee are typically the same person. and all Root UsersRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user. of CorporatesCorporates Business entities that can be onboarded as identities on Weavr. Corporate identities represent companies and require Know Your Business (KYB) verification. They can have multiple authorised users and issue cards to card assignees. will now be shown the following screen when onboarding:
This enables us to record the agreement of the End Customer to the FI T&Cs directly, as well as automatically update the version of T&Cs if they are revised in future. T&Cs updates will be communicated in advance in each case.
This FI T&Cs agreement screen is implemented automatically in the standard embedded onboarding flows, prior to the Customer Due Diligence steps (e.g. identity verification and proof of address) in the rest of the process.
Live programmes will need to ensure that they remove any older T&Cs agreement steps from their own sign up flows (i.e. to remove duplication of a step) as soon as feasible. EmbeddersEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers. should still ensure the correct versions of the T&Cs documents are available to the End Customer to find easily via their application, support docs etc.
Documentation links:
Existing End Customers on live programmes will not be affected (since they already agreed to terms and conditions when they signed up, and were sent any subsequent changes).
Updated/moved Micro-enterprise declaration in KYBKYB Know Your Business - the identity verification process for corporate identities. This process allows you to seamlessly and securely verify your business customer's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers. onboarding
As well as the above new T&Cs step for all onboarding flows, we will now require a clearer Micro-enterprise declaration, which we are adding into the KYBKYB Know Your Business - the identity verification process for corporate identities. This process allows you to seamlessly and securely verify your business customer's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers. onboarding:
As shown, the Root UserRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user. of the Corporate needs to answer the two questions and then agree to the declaration about whether the Corporate is or is not considered a Micro-enterprise.
This replaces the previous question in the KYBKYB Know Your Business - the identity verification process for corporate identities. This process allows you to seamlessly and securely verify your business customer's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers. questionnaire, and these changes take place automatically.
Documentation links:
Existing End Customers on live programmes will not have to take any action directly. If our records show that a Corporate’s profile is unclear about their Micro-enterprise status, we will follow up with the EmbedderEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers.’s team about how to refresh KYBKYB Know Your Business - the identity verification process for corporate identities. This process allows you to seamlessly and securely verify your business customer's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers. profiles in this respect.
Changes relating to wire transfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). functionality in UK programmes
From 7 Oct 2024, new regulations come into force in the UK regarding the fraud compensation rights of retail customers using Faster Payment System payments, known in the industry as “push payments”, and hence the regulations relate to “authorised push payment fraud” or APP Fraud.
EmbeddersEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers. with UK programmes should familiarise with the following background information: APP Fraud overview. Pay UK provides a timeline of regulatory changes here.
All UK programmes now choose a general payment model that takes into account changes to risk from APP Fraud regulations, and as part of these changes we are also implementing new features to be able to exclude “self-to-self” payments from the scope of future fraud claims.
These APP Fraud related changes do not affect EU/EEA programmes.
UK programme choices under new APP Fraud compensation regime
UK programmes will now be classified into three distinct approaches in terms of how APP Fraud risks are mitigated.
-
Cards-Focused programmes
End Customers will not be able to sendSend A transaction type that allows sending funds to another identity's instrument or to a beneficiary. Send transactions may require Strong Customer Authentication depending on the destination and whether it's a trusted beneficiary. or receive Faster Payment System wire transfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). except “self-to-self” to/from Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers., i.e. for the purpose of funding accounts for cards usage, and withdrawing any surplus balance.
-
Cards and Wire TransfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). programmes
End Customers will continue to take advantage of GBP OWTsOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. to third parties and IWTsIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds. from third parties via the Faster Payment System, but within new boundaries and features designed to control risk.
-
Wire TransfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). Focused programmes
The Embedded Payment RunPayment Run A list of payments created by Buyers to settle their outstanding financial obligations with their suppliers. Payment runs are typically managed by the accounts payable function within a business on a periodic basis and go through stages of creation, authorisation, funding, and execution. solution operates without cards and requires mitigations of APP Fraud risk: details for relevant programmes are available in separate release notes.
For (1) Cards-Focused programmes, changes must be made to implement Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers. (see below) and remove any previous functionality and UI/UX material relating to third party OWTsOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. and IWTsIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds..
For (2) Cards and Wire TransfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). programmes, changes include implementing new steps in OWTOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. flows, optionally making use of Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers. features, and establishing a working position with regard to real-time screening of IWTsIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds..
All live UK programmes will receive more detailed guidance to assist with change management.
Introducing Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers.
Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers. are a new feature available initially for UK programmes only.
Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers. are a representation of an End Customer’s own external accounts (such as a Corporate’s business bank account) which they register and verify in our systems. This means we can treat Incoming Wire TransfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). from the external account as a “self-to-self” funding transaction, and any Outgoing Wire TransferWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). back out to that account as a “self-to-self” withdrawal.
These transactions are then not in scope of APP Fraud claims, ensuring that a [UK] Cards-Focused programme can operate without exposure to risk from general third-party wire transferWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). flows. In the case of [UK] Cards and Wire TransferWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). programmes, Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers. can optionally be used to reduce risk by differentiating clearly between “self-to-self” flows and other third-party payments.
In summary:
- Both Consumer and Corporate End Customers on UK programmes can use Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers.
- Using Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers. is mandatory on UK Cards-Focused programmes
- Using Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers. is optional on UK Cards & Wire TransfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). programmes
- Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers. are not yet available for EU/EUR/SEPA programmes
Existing End Customers on live UK Cards-Focused programmes will need to set up at least one Linked AccountLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers. to be able to continue funding their payments (and withdrawing surplus funds if they desire). Weavr will assist live EmbeddersEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers. with this setup process for existing customers.
Documentation links:
- UK Linked Accounts: how to add and verify
- UX flow for registering and verifying a new Linked Account: flow diagram
Conditional acceptance of IWTsIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds.
We are offering the following new feature initially only for UK Cards and Wire TransfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). programmes. In these programmes EmbeddersEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers. have opted to continue offering features that allow End Customers to receive Faster Payment System [GBP] IWTsIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds. from third parties. Therefore, both the End Customer and the EmbedderEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers. are exposed to risk due to the possibility of external payers being retail customers who create a claim against a transaction with their (third-party / external) payer’s PSP.
On a beta basis we are working with affected programmes to put in place a real-time decisioning system so that the EmbedderEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers.’s business can selectively decide on a per-transaction basis whether to allow an End Customer to accept a [GBP FPS] IWTIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds..
This is described in our documentation as “IWT Forwarding Event” here.
We will discuss implementation details on a programme basis.
This feature is not available for EmbeddersEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers. on UK Cards-Focused programmes, although we use our own real-time decisioning in a similar way to reject IWTsIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds. which are not from external sources previously verified as Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers..
The feature does not currently apply to EU/EEA programmes and [EUR] SEPA payments.
Changed requirements for UK FPS OWTOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. creation to include Confirmation of PayeeConfirmation of Payee A service that automatically verifies bank account details when creating payment runs or outgoing wire transfers. For GBP payments, CoP checks return results showing Exact Match, Close Match, or No Match, including reason codes and additional information to help verify the payee details are correct.
We are offering the following new mandatory change for UK Cards and Wire TransfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). programmes, i.e. where End Customers are offered workflows to create [GBP FPS] OWTsOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. to third-party payees.
Affected programmes will need to make changes to the UX and logic of their OWTOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. workflow to incorporate a Confirmation of PayeeConfirmation of Payee A service that automatically verifies bank account details when creating payment runs or outgoing wire transfers. For GBP payments, CoP checks return results showing Exact Match, Close Match, or No Match, including reason codes and additional information to help verify the payee details are correct. check, and ensure the results are displayed intelligibly to the End Customer, so they can decide whether to proceed with the payment (or amend or cancel it).
This new OWTOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. flow splits the API calls so that the Weavr system can provide the CoP check result and await a confirmation from the end customer’s decision to proceed, which is followed by the SCASCA Strong Customer Authentication - a two-factor authentication solution required by PSD2 regulations for when end-users are accessing their payment account sensitive information or initiating transactions. SCA requires at least two of the following: something you know (password), something you have (device), or something you are (biometrics). challenge.
This implementation of Confirmation of PayeeConfirmation of Payee A service that automatically verifies bank account details when creating payment runs or outgoing wire transfers. For GBP payments, CoP checks return results showing Exact Match, Close Match, or No Match, including reason codes and additional information to help verify the payee details are correct. must be ready for End Customers to use (as the only OWTOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. flow available for GBP FPS) by 31 October 2024.
We will support EmbeddersEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers. making changes in live programmes to ensure the implementation is compliant and well-designed for end users to understand.
Documentation links:
- Overview of Confirmation of Payee (applies to GBP FPS OWTs)
- Contact us for further documentation on the API and UX flow logic of OWTOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. flows when implementing these changes
- Table of CoP responses and what to display to End Customers
Note Confirmation of PayeeConfirmation of Payee A service that automatically verifies bank account details when creating payment runs or outgoing wire transfers. For GBP payments, CoP checks return results showing Exact Match, Close Match, or No Match, including reason codes and additional information to help verify the payee details are correct. does not apply to EU/EEA programmes and [EUR] SEPA payments, but a similar solution (Verification of Payee) will come into force in the second half of 2025.
Recommended implementation of withdrawal OWTsOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. to Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers.
As noted above, UK Cards-Focused programmes will not be able to offer OWTsOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. to End Customers except as “self-to-self” withdrawals to external accounts registered and verified as Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers.. Applications in these programmes should not offer End Customers information or UX flows related to making OWTsOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. to third parties.
Live UK programmes which previously offered OWTOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. functionality and are now deprecating it should offer a revised UX flow for an End Customer creating a withdrawal transaction. The End Customer should be able to select one of their Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers. as the payee, without being asked to edit the payee details.
Contact us for specific documentation on the API and UX flow logic of withdrawal OWTsOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. to Linked AccountsLinked Account An entity in the Weavr system that represents an external bank account or payment service provider (PSP) account which an Identity has verified they own and control. This feature enables users to perform transactions, such as outgoing and incoming wire transfers, between their Linked Accounts and their Managed Accounts as 'self-to-self' transfers..