Updates to Accounts and Recipients

Overview

In order to clear up some ambiguity and streamline compliance processes for new accounts and recipients some minor field changes are being implemented to our accounts and payments endpoints. These field changes will ensure as much accurate data as possible is available from the offset to reduce potential back and forth when running checks. Additional guides will come in the next few weeks outlining more detail around account/recipient creation to help further improve this area.

Version Impacted: V2.0

Date Effective: 13th of May

Impacted Endpoints:

• POST/payment/transfer
• POST/payment/payout
• POST/recipient
• POST/recipient/{recipientID}/paymentAddress
• GET/payment
• POST/account/individual
• POST/account/corporate
• POST/account/{accountID}/authorisedRepresentative

Changes to Payments

• Added tax to the list of valid payment reasons
• Removed fromTradingAccount and toTradingAccount from transfer requests
• Make references on transfers optional
• Made payment reasons on transfers optional
• Removed fromTradingAccount from payout requests
• Made paymentAddress mandatory when creating a recipient
• Renamed paymentType to payoutType when creating a paymentAddress. This is to support updating paymentType field in GET Payment to now differentiate between payouts and transfers
• Renamed business fields to corporate fields in recipient creation.

Changes to Accounts

• Added the ability to add a primaryIdentification object to Authorised Representatives, Trust Beneficiaries and Trust Trustees
• Updated corporateType Enum
• Updated our corporate fields to now contain the following fields
  • Corporate Name
  • Corporate Business Name
  • Corporate Registration Number
  • Corporate Registration Type
  • Corporate Type
  • Country of Registration

📘

Got Questions?

Got questions or concerns about this change? Head over to our Discussion Board and leave us a note.