Corporate KYB - UBO Additional Information Requirements​

As part of our ongoing improvements to compliance and due diligence processes, we have extended the information captured as part of UBO applications; where UBO business ownership is 25% or greater.

For each qualifying UBO, the following information will need to be provided:

• Place of Birth
• Official ID
• Email Address
• Address, including country of permanent residence

Capturing of this additional information will be required, per qualifying UBO application, as of 12th April 2022.

Annual Corporate KYB Refresh.​

As part of our ongoing improvements to compliance and due diligence processes, we have extended verification procedures; in connection with pre-existing corporate KYB information.

On an annual basis KYB information supplied will undergo additional verification. Information will be refreshed as part of this process, which will include corporate root users re-validating through the KYB process, and if necessary, for directors to provide updated KYC information.

Once a refresh has been initiated there are three indications:

• The corporate due diligence status will show a purple bar, stating KYB refreshing, on the Weavr portal.
• The corporate root user, and individual directors (if necessary), will receive an email advising the need to update due diligence information.
• A webhook event will be triggered that includes an additional “OngoingStatus” parameter, indicating the refresh progress.

Two additional email templates have been incorporated as part of the notification to root users and directors. Default branding is used for such templates, but these can be branded according to your corporate design. If you have not already provided input for branding in connection with these emails, and wish to update this, please contact us via our support portal https://support.weavr.io and our team will be able to provide assistance with your specific requirements.

Corporate & Consumer Charge Fee - Additional Transaction Details​

When using the charge fee API, additional transaction details will be included within the response payload, including the state and transaction ID, allowing the correlation of transaction and associating fee.

Affected APIs:

• POST /consumers/fees/charge
• POST /corporates/fees/charge

Password & Passcode UI Components - New Submit Events​

Password and Passcode UI components will support the use of enter key interactions for triggering events. Such events can be used instead of requiring users to click a button, allowing for smoother interactions and automatic form submissions.

For more information please refer to our Password UI component and Passcode UI component guides.

Prepaid Cards - Fund Transfers on Destroyed & Expired Cards​

When using the Transfer API, unloading of funds will be supported for prepaid cards in a destroyed or expired status. Such transfers must be to another managed account or managed card belonging to the same corporate or consumer identity.

Affected APIs:

• POST /transfers

Inbound and Outbound 3rd Party UK Faster Payments​

We are pleased to announce that the UK Faster Payments payment method now supports 3rd party inbound and outbound domestic transfers for both Corporates and Consumers.

For GBP managed accounts connected to this service, you will receive a sort code and account number when upgrading the managed account. These details can be used for domestic payments in GBP. The payment reference that was previously required to make deposits will not be required when using this sort code and account number.

Please note: Managed accounts may be marked as inactive for a short period of time after opening, whilst the account details are assigned. Once assigned a webhook notification will be sent to you confirming that the account is now active. You should only initiate the upgrade account request once the account is marked active. Find more details on how to upgrade managed accounts in our guide.

If you would like to start using this payment method now, please contact us via the Support Portal so that we can enable it for you.

In due course all GBP managed accounts will be automatically upgraded.

Deposit Transactions - Additional Sender Information​

When depositing funds using the new UK Faster Payments payment method, the senderIban, senderName and senderReference fields will be included as part of the managed account deposit transaction.

All three fields are available when retrieving a managed account statement, as part of the entry.additionalFields, and when you are notified of a managed account deposit via the webhook. They are also displayed as part of the managed account activity within the portal.

These fields will be added to SEPA and SWIFT deposits soon.

Affected APIs:

• GET /managed_accounts/{id}/statement

Affected Webhooks:

• POST /managed_accounts/deposits/watch

Consumer place of birth - New Optional Field​

When onboarding a consumer identity you can optionally include the placeOfBirth field. If provided, this information is pre-filled for the user when they are submitting their information for KYC.

If the user hasn’t completed KYCm, you can also update the field via the Update Consumer API endpoint.

Affected APIs:

• POST /consumers
• PATCH /consumers

Physical Cards - New Optional second line for name on card​

The name on card for physical cards now supports 2 lines. You can optionally specify a second line via the nameOnCardLine2 field when upgrading a virtual card to a physical card. When provided, the second line will also be printed on the physical card itself.

Affected APIs:

• POST /managed_cards/\{id\}/physical
• POST /managed_cards/assign

Spend Rule - Allowed merchant countries​

You can now specify an allowed or blocked list of countries from where the user can make purchases. The card purchase country is determined from the merchant's registration country.

The allowed and blocked lists can be configured in the card profile level via the Multi portal or per card in the Multi API.

Affected APIs:

• GET /managed_cards/\{id\}/spend_rules
• PUT /managed_cards/\{id\}/spend_rules

Spend Rule - Single card purchases​

You can now specify the minimum and / or maximum amount of a single card purchase via the Multi API.

Card purchases that are below the minimum amount or above the maximum amount will be automatically declined. This control can be configured per card.

Affected APIs:

• GET /managed_cards/\{id\}/spend_rules
• PUT /managed_cards/\{id\}/spend_rules

Card purchase simulator - forex configuration​

You can now simulate card purchases that include a forex fee and / or a forex padding via the Multi portal. This option has been added to the Purchase by Card ID and Purchase by Card Number simulators.

Authorisation webhook - additional forex information​

The forexPadding field is now available as part of the card authorisation webhook. This field is included when the purchase currency is different from the card's currency and therefore forex is required.

Affected webhooks:

• POST /managed_cards/authorisations/watch

Service status announcements​

You can now view the status of our services and subscribe to receive service status updates. The same announcements are also visible in the Multi portal.

Card friendly names - Emojis Support​

Your customers can now include emojis in their card friendly names to further personalise their cards ✨

Updated the company registration number to optional​

You can now onboard sole traders who do not have a company registration number. The company.registrationNumber parameter can now be left empty.

Note, that for other company types, the registration number is still required to complete the KYB process.

Affected APIs:

• GET /corporates
• POST /corporates
• PATCH /corporates

New sender name information in the deposit webhook​

The account deposit webhook now includes new senderName field as part of the deposit information.

Affected webhooks:

• POST /managed_accounts/deposits/watch

New cancelled type for card authorisations​

Card authorisations are cancelled if an approve or reject decision is not received by the provider in the agreed time. This ensures that no authorisations are wrongly approved.

If a card authorisation is cancelled by the provider, you will receive a card authorisation webhook notification having the authorisationType field set as CANCELLED. Cancelled card authorisations are now included in the card statement API endpoint with their entry.transactionId.type being AUTHORISATION_CANCELLATION.

Affected webhooks:

• POST /managed_cards/authorisations/watch

Affected APIs:

• GET /managed_cards/\{id\}/statement

New Pending state for deposit, transfer and send transactions​

In most cases, transactions are executed instantly, however there are cases where a transaction needs to be temporarily paused. This may be due to different reasons, ranging from asynchronous processes to transaction monitoring.

If a deposit, transfer or send transaction is in a pending state, its transaction state will be marked as PENDING and will resume automatically as soon as all requirements are met.

Affected APIs:

• GET /transfers
• GET /transfers/\{id\}
• POST /transfers
• GET /sends
• GET /sends/\{id\}
• POST /sends

Additional transaction information in the managed account and managed card statement​

The following fields are now available in the the managed account and managed card statement:

• actualBalanceAfter
• actualBalanceAdjustment
• availableBalanceAfter
• availableBalanceAdjustment
• entryState

Instrument balances are represented using both an actual and an available balance. The actual balance shows how much funds actually reside on the instrument, while the available balance shows how much funds are available to be used. If there are no pending transactions on the instrument, the available and actual balance should be equal. Transaction entries returned in the statement APIs are reporting a balance change in one or both balances.

Note that the balanceAfter field is now deprecated in favour of the availableBalanceAfter.

The new transaction entryState field indicates whether a transaction has moved into a PENDING or COMPLETED state. When a transaction is in a PENDING state, this means that some fund movements have completed however additional fund movements are still pending. Once a transaction is moved to a COMPLETED state, this means that all expected fund movements are now complete.

Affected APIs:

• GET /managed_cards/\{id\}/statement
• GET /managed_accounts/\{id\}/statement

New check for mobile number​

The mobile number used by authorised users within the same corporate or consumer identity must be unique. If a mobile number is already being used by another user, the API will return an HTTP 409 - Conflict error with error code MOBILE_NOT_UNIQUE.