Concepts

flowchart LR
  ProductConfig -- manages who can access --> Product
  ProductFeeConfig -- manages what fees are charged --> Product
  ProductLimitConfig -- manages how much can be transacted --> Product

  Product -- instantiates as --> Transaction
  
  Transaction -- remits/sends as --> _Entity_
  Transaction -- credits/debits --> _Account_
  Transaction -- off-ramps --> _PaymentInstrument_

  _Entity_ --- Identity
  _Entity_ --- Organization

  _Account_ --- LedgerAccount
  _Account_ --- VirtualAccount
  _Account_ --- BlockchainWallet

  _PaymentInstrument_ --- ACH
  _PaymentInstrument_ --- swiftwire[SWIFT Wire]
  _PaymentInstrument_ --- uswire[US Wire]
  _PaymentInstrument_ --- clabe[Mexico CLABE]
  _PaymentInstrument_ --- afbank[African Bank]
  _PaymentInstrument_ --- afmomo[African Mobile Money]

Customer

This is you. As a customer of MoveUSD platform, you get access to MoveUSD APIs and MoveUSD customer dashboard. All other objects in the platform (see below) are configured within your Customer tenancy.

Once on-boarded to the platform, a Customer tenancy will be provisioned for you.

Product

The capabilities of the platform are encapsulated into a set of Products. Platform Overview lists the available products.

Product configuration, such as their availability, fees and limits, are discoverable via the API. See Product Configurations for more information.

Based on your arrangement with MoveUSD platform, you will be provisioned with the Products available to you. You can further configure these via following APIs:

• Product config: Product availability
• Product fee config: Fees charged by us and fees you can set for your own customers
• Product limit config: Limits enforced by us and limits you can set for your own customers

Transaction

Customers use Products by executing Transactions. Some transactions are executed within the platform, such as wire withdrawals, while others may be initiated from outside the platform, such as wire deposits.

Transactions are typically associated with some other platform objects:

• Entity: On behalf of whom is this transaction being executed, i.e. sender (in case of withdrawals) or remitter (in case of deposit) of funds
• Account: Which account is credited or debited as a result of executing the transaction
• Payment instrument: Which external financial instrument is the target of the funds being transferred (specific to withdrawal products)

Transactions are represented as an individual APIs such as Deposit API, Withdrawal API, etc.

Entity

Customers execute Transactions on behalf of Entities. Entities need to be on-boarded to the platform before they can be used in Transactions. During the on-boarding, the entities are verified for compliance, Anti-Money Laundering and other legal requirements (KYC and KYB).

There are two types of Entities:

• Identities: Individuals, a person with a legal name
• Organizations: Businesses, registered as a legal entity

As a customer, you also have a primary Organization that represents your business.

You can mange your identities and organizations via Identity and Organization APIs respectively.

Account

MoveUSD and other currencies are held in Accounts.

The platform currently offer the following Accounts:

• Ledger Account: A platfrom-custody Account that can hold MoveUSD. Ledger Accounts are the primary place to hold your funds within MoveUSD platform. They are specified during Transactions as source or target for the funds, depending on the Product.
• Virtual Account: Coming soon!
• Blockchain Wallet: A self-custody blockchain wallet, where you can hold your funds off-platform. They can be nominated as source or target for the funds, depending on the Product.

Accounts belong to an Entity and can be managed as a sub-resource of a given Identity or Organization. For example, you can manage Ledger Accounts via Ledger Account (for an Identity) and Ledger Account (for an Organization).

Payment Instrument

Before funds can be withdrawn from the platform an external target, that target needs to be registered as a Payment Instrument. Examples of Payment Instruments include: Wire accounts, ACH accounts, Mexican CLABE accounts, etc.

Payment Instruments belong to an Entity and can be managed as a sub-resource of a given Identity or Organization, i.e. Payment Instrument (for an Identity) and Payment Instrument (for an Organization).