Create and execute OWTs

Create and execute an outgoing wire transferWire TransferA 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). (OWTOWT (Outgoing Wire Transfer). 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.) with a Confirmation of PayeeConfirmation of Payee (CoP). 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. (CoP) check.

Create and execute an OWT

1. Create the OWT and run the CoP check

Create a GBP OWTOWT (Outgoing Wire Transfer). 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. using the following endpoint. You can initiate the transfer using a Linked AccountLinked AccountAn entity in the Weavr system that represents an external bank account or payment service provider (PSP) account that a customer 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. ID, trusted payeeTrusted PayeeA trusted recipient for payments, including the business or individual's details and their bank account or instrument details. Sending to a Trusted Payee may let customers skip Strong Customer Authentication (SCA) on Outgoing Wire Transfer or Send transactions, reducing the number of approval steps required. Previously referred to as a Beneficiary. ID, or by providing bankAccountDetails → FasterPaymentBankDetails for a one-time payment:

POST/outgoing_wire_transfersOpen API reference →

/outgoing_wire_transfers

{  "profileId": "10001",  "tag": "customer-123",  "sourceInstrument": {    "type": "managed_accounts",    "id": "123456789"  },  "transferAmount": {    "currency": "GBP",    "amount": 1250  },  "purpose": "Invoice payment",  "description": "Invoice 1042",  "destinationBeneficiary": {    "name": "Alex Smith",    "type": "PERSONAL",    "address": "1 High Street, London W1A 1AA",    "bankName": "National Westminster Bank PLC",    "bankAddress": "250 Bishopsgate, London EC2M 4AA",    "bankCountry": "GB",    "bankAccountDetails": {      "iban": "GB29NWBK60161331926819",      "bankIdentifierCode": "NWBKGB2L"    },    "nationality": "GB",    "dateOfBirth": "1990-01-01"  },  "scheduledTimestamp": "1786118400000"}

After the OWTOWT (Outgoing Wire Transfer). 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. is created, we automatically run a CoP check to verify the bank account details. The OWTOWT (Outgoing Wire Transfer). 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. state updates to PENDING_CONFIRMATION and the CoP result is returned in the response.

The response to POST/outgoing_wire_transfers (and to GET/outgoing_wire_transfers and GET/outgoing_wire_transfers/{id}) returns the OWTOWT (Outgoing Wire Transfer). 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. in PENDING_CONFIRMATION state with a validationOutcomes array containing the CoP result.

Example response (excerpt)

{
  "id": "{{owtId}}",
  "state": "PENDING_CONFIRMATION",
  "validationOutcomes": [
    {
      "category": "UK_CONFIRMATION_OF_PAYEE",
      "categoryResult": {
        "match": "CLOSE_MATCH",
        "reasonCode": "MBAM",
        "accountName": "Acme Ltd"
      }
    }
  ]
  ...
}

CoP result fields

Field	Description
category	Always UK_CONFIRMATION_OF_PAYEE for GBP OWTsOWT (Outgoing Wire Transfer). 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..
categoryResult.match	EXACT_MATCH, CLOSE_MATCH, or NO_MATCH.
categoryResult.reasonCode	Explains why the check returned CLOSE_MATCH or NO_MATCH. Not returned for EXACT_MATCH. See CoP reason codes for the full list.
categoryResult.accountName	The registered account name. Only returned for CLOSE_MATCH with reason code MBAM, BAMM, or PAMM, so the end user can accept it and re-run the check.

If the OWTOWT (Outgoing Wire Transfer). 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. was created with a Linked AccountLinked AccountAn entity in the Weavr system that represents an external bank account or payment service provider (PSP) account that a customer 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. ID, destinationInstrument also includes a linkedAccount value.

Linked accounts skip CoP

When creating an OWTOWT (Outgoing Wire Transfer). 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. using a Linked AccountLinked AccountAn entity in the Weavr system that represents an external bank account or payment service provider (PSP) account that a customer 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. ID, a CoP result isn't returned and the confirm step isn't required.

2. Handle the CoP result with the end user

Display the validationOutcomes result to the end user and offer them the following options:

• Accept the suggested name — for CLOSE_MATCH results where accountName is returned, the payee name updates to the registered name and the check re-runs.
• Enter a new name — correct the payee name and re-run the CoP check.
• Proceed with the OWTOWT (Outgoing Wire Transfer). 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. — confirm using the name as entered. Skip to step 3.
• Cancel the OWTOWT (Outgoing Wire Transfer). 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. — abandon the payment. See Cancel the OWT.

To accept the suggested name or enter a new name, use the following endpoint. Both options re-run the CoP check and return updated validationOutcomes:

PATCH/outgoing_wire_transfers/{id}Open API reference →

/outgoing_wire_transfers/123456789

{  "name": "Alex Smith",  "acceptVerifiedName": true}

In the case of a CLOSE_MATCH, you can accept the suggested name:

{
  "acceptVerifiedName": true
}

Otherwise, you'll need to submit a new name:

{
  "name": "Corrected Payee Name"
}

After the check re-runs, repeat step 2 and display the updated result to the end user.

3. Execute the OWT

Confirm the OWT

To confirm and proceed with the OWTOWT (Outgoing Wire Transfer). 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., use the /confirm endpoint.

POST/outgoing_wire_transfers/{id}/confirmOpen API reference →

/outgoing_wire_transfers/123456789/confirm

The OWTOWT (Outgoing Wire Transfer). 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. state immediately changes from PENDING_CONFIRMATION to PENDING_CHALLENGE, which requires completing before the OWTOWT (Outgoing Wire Transfer). 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. is fully submitted.

Returned state	What it means and what to do next
PENDING_CHALLENGE	Confirmation succeeded. Complete the transaction confirmation challenge.
PENDING_CONFIRMATION	The transfer still needs confirming. Call the confirm endpoint again.
SUBMITTED, or any state that follows it	The transfer is already accepted and in flight. Don't call the confirm endpoint again. Track progress with the POST/outgoing_wire_transfers/watch webhook instead.

The value returned by /confirm is authoritative, and you should check that rather than assuming the transfer has moved to PENDING_CHALLENGE.

Complete SCA

Complete the transaction confirmation SCASCA (Strong Customer Authentication). 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, then call /confirm again.

The state then changes from PENDING_CHALLENGE to SUBMITTED.

A 200 response doesn't guarantee that the state advanced, so always read state from the /confirm response.

Cancel the OWT (optional)

If the end user wants to abandon the process, use the following endpoint:

POST/outgoing_wire_transfers/{id}/cancelOpen API reference →

/outgoing_wire_transfers/123456789/cancel

{  "cancellationReason": "Payment no longer required"}

Webhook event

The POST/outgoing_wire_transfers/watch webhook includes the eventType PENDING_CONFIRMATION in its payload, letting you react asynchronously when an OWTOWT (Outgoing Wire Transfer). 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. is awaiting confirmation.

POST/outgoing_wire_transfers/watchOpen reference →