Skip to main content

Multi API v3.32

· 2 min read
Dragos Tigoianu

BeneficiaryBeneficiary A trusted recipient for payments that includes both information about the business or individual as well as their bank account or instrument details. When using trusted beneficiaries, customers may be allowed to skip Strong Customer Authentication (SCA) when executing Outgoing Wire Transfer or Send transactions, reducing the number of approval steps required. names for 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. now support special characters​

When creating an 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). (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.), it will be possible to include special characters as part of the destinationBeneficiary.name field.

The supported characters are inline with the accepted SEPA or FPS payment schemes. If an unsupported characters is used this will be automatically converted to “.”, avoiding any interruption to the 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. submission.

For SEPA we follow the EPC guidelines of the Extended Character Set.

For FPS, the special characters are:

  • "/" (forward slash)
  • "-" (hyphen)
  • "?" (question mark)
  • ":" (colon)
  • "(" (left parenthesis))
  • ")" (right parenthesis)
  • "." (full stop)
  • "," (comma)
  • "’" (right single quote)
  • "+"(plus sign)
  • (blank space)
  • "#" (hash)
  • "=" (equals)
  • "!" (exclamation mark)
  • ” (right double quote)
  • "%" (percentage)
  • "&" (ampersand)
  • "*" (asterisk)
  • "<" (less than)
  • ">" (greater than)
  • ";" (semicolon)
  • "{" (left curly bracket)
  • "@" (commercial at)
  • CrLf (carriage return line feed)

Ability to increase the maximum allowable characters on bespoke plastic cards​

If you provide physical cardsPhysical Card A payment card that is printed or embedded in wearables and sent to customers directly. Physical cards are created by first creating a virtual card and then upgrading it to a physical card. They are sent in an inactive state and must be activated by the card assignee before first use. for your customers and opt for our bespoke plastic cards; depending on your bespoke design and configuration, it will be possible to increase the maximum allowable characters of the nameOnCard and nameOnCardLine2 fields printed on the cards, to a maximum of 27 characters per field.

For on-demand designs, the maximum allowable characters for both fields will remain at 20 characters.

If you already use a bespoke card design, or would like to upgrade your cards and design, contact Weavr Support to determine the maximum allowable characters for your bespoke plastic card programmes.