The Transactive API has a limited number of entities which are used to tailor Transactive to your needs.
Details about your contractual relationship(s) (currently only one allowed) with Transactive, including approved products, pricing and limitations/constraints if applicable.
Members of your staff that are allowed access to Transactive.
System principals (programs/apps, not humans) that are allowed access to Transactive.
Your Transactive virtual bank account(s), to and from which Payments are routed, and from which fees are paid. Each Account has a balance and a list of entries. Each entry can be traced to a single Payment.
Activities occur on an account. Activities include deposits, fees, payouts, transfers out and reversals.
Role-oriented permissions, used to control what Contacts and Applications can do and see.
Permission to direct payments to, and receive payments from, specific bank accounts.
URLs/endpoints in your own software system(s). Transactive will send event notifications to these Webhooks, e.g. the arrival of an inbound Payment.
In addition of configuration entities, the Transactive API has a potentially unlimited number of operational entities which are the by product of your business activities.
Transfers of funds to and from your Accounts.
Payment-related principal or fee amounts posted to Accounts. A Payment may result in multiple entries in multiple Accounts.
Significant Payment events, e.g. the arrival of a new inbound Payment.