Skip to main content

48 posts tagged with "Multi-v2"

View All Tags

Version 2.13.11

· 4 min read
Maria Stellini

What's Changed​

  • Physical cards can be assigned a custom delivery name and surname which when provided will replace the identity's business name on the postage address when delivering the physical card. This is particularly useful when you want to deliver a physical to a corporate user rather than the business.
    • POST /managed_cards/{id}/physical/upgrade
    • POST /managed_cards/get
    • POST /managed_cards/{id}/unfreeze
    • POST /managed_cards/{id}/physical/report_stolen
    • POST /managed_cards/{id}/physical/replace_damaged
    • POST /managed_cards/{id}/physical/report_lost
    • POST /managed_cards/{id}/physical/replace_lost_stolen
    • POST /managed_cards/{id}/physical/activate
    • POST /managedcards//assign
    • POST /managed_cards/{id}/remove
    • POST /managed_cards/{id}/get
    • POST /managed_cards/{id}/update
    • POST /managedcards//create
    • POST /managed_cards/{id}/freeze

Version 2.13.3

· One min read
Maria Stellini

What's Changed​

  • The hasPending request parameter has been removed for both the managed_account and managed_card resources.
    • POST /managed_accounts/get
    • POST /managed_cards/get

Version 2.13.0

· 5 min read
Maria Stellini

What's New​

Initiating Outgoing Wire Transfers

A new financial service that supports incoming and outgoing wire transfers has been introduced to the Weavr Platform. This service enables consumers and corporates to receive and send funds, from and to third parties as well as their own bank accounts. The capabilities associated with this service are represented under the new outgoing_wire_transfers resource.

The API to get the bank details associated with a Managed Account has not changed, however the details returned might change so as to allow for 3rd party deposits. To submit an outgoing wire transfer, a new API ​/outgoing_wire_transfers​/_​/execute has been added that enables corporates and consumers to send funds from a Managed Account to an external bank account.

  • POST /outgoingwire_transfers//execute

Once, an outgoing wire transfer is submitted, the status and details of the transfer can be retrieved via the API.

  • POST /outgoing_wire_transfers/get
  • POST /outgoing_wire_transfers/{id}/get

What's Changed​

Managed Accounts

  • Withdrawal: The withdrawal APIs under the managed_accounts resource have been removed, however the capability is still supported (if permitted by the service provider). To submit a withdrawal from a managed account, the new ​/outgoing_wire_transfers​/_​/execute should be used.

    • POST /managed_accounts/withdraw/get
    • POST /managed_accounts/{id}/withdraw/{withdraw_id}/cancel
    • POST /managed_accounts/{id}/withdraw/{withdraw_id}/get
    • POST /managedaccounts/{id}/withdraw//create
    • POST ​/managed_accounts​/{id}​/withdraw​/get

  • Creating an Account: Four new error codes (IDENTITY_LIMITS_EXCEEDED, PROGRAMME_LIMITS_EXCEEDED, INNOVATOR_LIMITS_EXCEEDED, SYSTEM_LIMITS_EXCEEDED) were introduced and may be returned when creating an instrument.

    • POST /managedaccounts//create

  • Un/Freezing an Account: A new error message INSTRUMENT_INACTIVE has been added and will be returned if the instrument being frozen/unfrozen hasn't been created yet.

    • POST /managed_accounts/{id}/freeze
    • POST /managed_accounts/{id}/unfreeze

Managed Cards

  • Physical Cards: The activationCode does not need to be unique any more. Multiple physical cards can have the same activation code.

    • POST /managed_cards/{id}/physical/replace_damaged
    • POST /managed_cards/{id}/physical/replace_lost_stolen
    • POST /managed_cards/{id}/physical/activate
    • POST /managed_cards/{id}/physical/upgrade

  • Creating a Card: Four new error codes (IDENTITY_LIMITS_EXCEEDED, PROGRAMME_LIMITS_EXCEEDED, INNOVATOR_LIMITS_EXCEEDED, SYSTEM_LIMITS_EXCEEDED) were introduced and can be returned when creating an instrument.

    • POST /managedcards//create

  • New Auth Rule: A new auth rule has been introduced which when configured can block any credit type authorisations. Credit authorisations translate in the cardholder receiving funds on a card.

    • POST /managed_cards/{id}/auth_rule/get
    • POST /managed_cards/{id}/auth_rule/set

  • Removing a Managed Account: A new error code INSTRUMENT_HAS_PENDING_ACTIONS has been added and can be returned if the instrument being deleted still has pending actions.

    • POST /managed_cards/{id}/remove

Corporates

  • The ipAddress property has been updated so that is supports IPv6 IP addresses, it's length has increased from 15 characters to 45 characters.

    • POST /corporates/{id}/get
    • POST /corporates/{id}/update
    • POST /corporates/_/create

  • Charging a Fee: A new error code IDENTITY_NOT_OWNER_OF_INSTRUMENT has been added to the /corporates/\{id\}/charge_fee API. The error code will be returned if the identity owning the source instrument from where the fee is to be taken, does not match the identity currently logged in.

    • POST /corporates/{id}/charge_fee

  • Updating a Corporate: It is now possible to update the baseCurrency of a corporate.

    • POST /corporate/{id}/update

  • Activating/Deactivating a User: The response code 409 was removed from the possible response types.

    • POST /corporates/{id}/users/{user_id}/activate
    • POST /corporates/{id}/users/{user_id}/deactivate

Consumers

  • Charging a Fee: A new error code IDENTITY_NOT_OWNER_OF_INSTRUMENT has been added to the /consumers/\{id\}/charge_fee API. The error code will be returned if the identity owning the source instrument from where the fee is to be taken, does not match the identity currently logged in.

    • POST /consumers/{id}/charge_fee

  • Updating a Consumer: It is now possible to update the baseCurrency of a consumer.

    • POST /consumers/{id}/update

Version 2.12.3

· 14 min read
Maria Stellini

What's Changed​

  • Corporates and Consumer Due Diligence Limits: Multiple limits may start to apply to a particular Corporate. For this reason, the current allowedLimit object and remainingLimit object which support only 1 limit have been deprecated in favour of 2 new objects allowedLimits and remainingLimits which support an array of limits. The old objects allowedLimit and remainingLimit will continue to return the most restrictive limit from the set.

    • POST /corporates/{id}/kyb/get
    • POST /corporates/{id}/get
    • POST /corporates/{id}/update
    • POST /corporates/_/create
    • POST /consumers/{id}/kyc/get
    • POST /consumers/{id}/get
    • POST /consumers/{id}/update
    • POST /consumers/_/create

  • Managed Accounts: Two new properties accountNumber and sortCode have been added to the bank details associated with a Managed Account.

    • POST /managed_accounts/get
    • POST /managed_accounts/{id}/unfreeze
    • POST /managed_accounts/{id}/remove
    • POST /managed_accounts/{id}/get
    • POST /managed_accounts/{id}/update
    • POST /managedaccounts//create
    • POST /managed_accounts/{id}/freeze

Version 2.12.0

· 5 min read
Maria Stellini

What's Changed​

  • Corporates: Two new objects registrationAddress and a businessAddress have been added to the corporate's information. The registrationAddress refers to the address submitted to the state's registry (example CompaniesHouse in the UK), while the businessAddress refers to the address where the business is currently operating.

    • POST /corporates/{id}/get
    • POST /corporates/{id}/update
    • POST /corporates/_/create

  • Corporates: The companyRegistrationAddress and a companyBusinessAddress have been marked as deprecated as they will be replaced by the new address objects registrationAddress and a businessAddress.

    • POST /corporates/{id}/get
    • POST /corporates/{id}/update
    • POST /corporates/_/create

  • Corporates: The MANUFACTURINGPR_MARKETING property within the industry enum has been split up into 2 properties MANUFACTURING and PR_MARKETING.

    • POST /corporates/{id}/get
    • POST /corporates/{id}/update
    • POST /corporates/_/create