Skip to main content

Multi API v3.1.0

· 2 min read
Maria Stellini

New manufacturing status details for 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.​

A new manufacturingState field has been added to the managedCard.physicalCardDetails object to improve traceability of the fulfilment of 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..

The following are the supported manufacturing statuses:

  • REQUESTED: The physical cardPhysical 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. has been requested.
  • SENT_FOR_FULFILLMENT: The card has been sent for printing.
  • DISPATCHED: The card has been manufactured and dispatched.
  • DELIVERED: The card has been received and activated by the recipient.

The following endpoints return the 'ManagedCard' in their response, and will now start including this optional detail in case of 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.:

  • GET /multi/managed_cards post
  • GET /multi/managed_cards/\{id\}
  • PATCH /multi/managed_cards/\{id\}
  • POST /multi/managed_cards/assign
  • POST /multi/managed_cards/\{id\}/physical
  • POST /multi/managed_cards/\{id\}/physical/activate
  • POST /multi/managed_cards/\{id\}/physical/replace_lost_stolen

You can also view the manufacturing state of a physical cardPhysical 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. in the MultiMulti Weavr Multi is an embedded finance solution that allows you to integrate financial services into your own application, providing a seamless experience for your customers. It enables you to offer managed accounts, managed cards, and transactions without requiring financial expertise. Portal by accessing the card’s detail screen.

Card spend limits can now be applied to a time interval​

You can now set spend limits for different time intervals to better control the usage of debit modeDebit Mode A card mode where the card does not have a balance of its own. Instead, debit cards are linked to a parent managed account and the system uses the linked account's balance to authorise and settle purchases registered on the card. Spend limits can be specified on the card via spend controls. cards.

In addition to the ALWAYS interval, we have added the following intervals:

  • DAILY: starting from 00:00:00 UTC of current day to 23:59:59 UTC of current day
  • WEEKLY: 00:00:00 UTC Monday of current week to following Sunday 23:59:59 UTC
  • MONTHLY: 1st of current calendar month to end of current calendar month
  • QUARTERLY: starting from beginning of current quarter where quarters are defined as follows
    • 1 January 00:00:00 UTC to 31 March 23:59:59 UTC
    • 1 April 00:00:00 UTC to 30 Jun 23:59:59 UTC
    • 1 July 00:00:00 UTC to 30 September 23:59:59 UTC
    • 1 October 00:00:00 UTC to 31 December 23:59:59 UTC
  • YEARLY: 1 January 00:00:00 UTC of current calendar year to 31 December 23:59:59 UTC of current calendar year

Affected APIs:

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