Weavr platform updates

CorporatesCorporates (Corporate Identity). Business entities that can be onboarded as customers on Weavr. Corporate customers represent companies and require Know Your Business (KYB) verification. They can have multiple authorised users and issue cards to card assignees. can opt out of Verification of PayeeVerification of PayeeThe EU equivalent of Confirmation of Payee (CoP). A service that validates the name of a payment beneficiary against the IBAN registered with their bank or Payment Service Provider (PSP) before a SEPA payment is executed. for bulk SEPASEPA (Single Euro Payments Area). Single Euro Payments Area - the European scheme that standardises euro-denominated bank transfers across participating countries. EUR managed accounts settle incoming and outgoing wire transfers via SEPA Credit Transfer (SCT) or SEPA Instant; our [Verification of Payee](/transactions/owt/vop/overview) check runs against the IBAN registered with the beneficiary's bank or PSP before a SEPA payment executes. payments, authorization forwarding now carries point-of-sale and acquirer data, and single-spend cards return their leftover balance when they're destroyed.

Verification of Payee opt-out for bulk payments

CorporatesCorporates (Corporate Identity). Business entities that can be onboarded as customers on Weavr. Corporate customers represent companies and require Know Your Business (KYB) verification. They can have multiple authorised users and issue cards to card assignees. can now opt out of Verification of PayeeVerification of PayeeThe EU equivalent of Confirmation of Payee (CoP). A service that validates the name of a payment beneficiary against the IBAN registered with their bank or Payment Service Provider (PSP) before a SEPA payment is executed. (VoP) for EUR outgoing wire transfersWire 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). submitted through bulk operationsBulk OperationsThe capability of grouping multiple individual API-based actions into a batch. Bulk operations allow you to execute hundreds or thousands of operations by making only one or two API calls, increasing throughput, accomplishing actions in a secure session, and reducing complexity in your application. in a bulk of two or more payments. Payments submitted on their own are always checked.

• GET /corporates/settings returns the corporate's settings, and PATCH /corporates/settings updates them. The opt-out is verificationOfPayee.bulkPayments, either OPTED_IN (the default) or OPTED_OUT.
• Opting out needs a stepped-up tokenStepped-up tokenAn access token that has been elevated to a higher authentication level by successfully completing a step-up challenge (typically an OTP via SMS or a biometric prompt). A stepped-up token is required to perform sensitive operations such as creating a user, managing authentication factors, or confirming high-value transactions. See the [step-up authentication guide](/apis/authentication/stepup/) for how to issue and complete a challenge., and your app must show the user the risks before they confirm. Opting back in needs no step-up.
• Opting out is only available once our team has certified your app's opt-out screen. Until then, an opt-out returns a 409 with VOP_BULK_OPT_OUT_NOT_AVAILABLE.
• 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. that skips the check has a SEPAVerificationOfPayee result of OPTED_OUT and doesn't wait for confirmation.
• A new Corporate settings updated webhook tells you when the setting changes, including when our team opts a corporate back in.

Verification of PayeeHow VoP checks work on EUR outgoing wire transfers.Read documentation →Operations in bulkGroup many API operations into one bulk process.Read documentation →

Point-of-sale and acquirer data in authorization forwarding

Authorization forwarding webhooks now include posData and acquirerData when the card network provides them. posData covers how the card was read, whether the cardholder was present, how they were verified, Strong Customer Authentication exemptions, and whether the merchant started the transaction. acquirerData identifies the acquirer and its country. Every field is optional.

Authorization forwardingApprove or decline card authorizations in real time.Read documentation →

Leftover balance on single-spend cards

When a prepaid single-spend card is destroyed after its spend, any balance left on it is now returned to the managed accountManaged AccountAn account held at a financial institution that can be created and managed through the Weavr platform. Each account has a balance where customers can hold funds. Optionally, an IBAN can be assigned to enable wire transfers to bank accounts outside of Weavr. that funded it. The card's adjustment webhook reports the return with an adjustmentType of DESTROYED_CARD_BALANCE_TRANSFER.

Card replacements keep the expiry of cards set not to renew

Replacing a lost, stolen, or damaged card with a renewalType of NO_RENEW now keeps the original card's expiry date. If that date is less than a month away, the replacement is refused with a 409 and INSTRUMENT_EXPIRY_DATE_TOO_CLOSE.

Lost or stolen cardsReport a card lost or stolen and replace it.Read documentation →Replace a damaged cardShip a new physical card with the same card details.Read documentation →

Email subjects in templates

Your customized email templates can now set their own subject line with a <!-- subject: ... --> marker. We can also set a different sender name for each program on request.

Customizing templatesPrepare and submit your own email and SMS templates.Read documentation →

Fixes

• Reporting a card lost a second time now returns a 409 with INSTRUMENT_ALREADY_MARKED_LOST and leaves the card blocked. Previously the repeat request could destroy the card.
• Reporting a card lost when it's already destroyed now returns a 409 with INSTRUMENT_DESTROYED.
• sourceOfFundsOther longer than 255 characters on corporatesCorporates (Corporate Identity). Business entities that can be onboarded as customers on Weavr. Corporate customers represent companies and require Know Your Business (KYB) verification. They can have multiple authorised users and issue cards to card assignees. and consumersConsumers (Consumer). Individual people who can be onboarded as customers on Weavr. Consumer customers require Know Your Customer (KYC) verification. For consumers, the card owner and card assignee are typically the same person. is now rejected with a 400.
• Retrying POST /corporates with the same idempotency-ref now returns the original corporate even when the retry comes from a different IP address. Previously the retry failed with ROOT_EMAIL_NOT_UNIQUE.
• Changing a corporate user's mobile number now always deactivates their enrolled authentication factors, so they need to enroll again. Previously this only happened when the old number had been verified.