Wallet Transactions

About

At Monta we capture any movement of money in Wallet Transactions.

A charge at Monta can involve many transactions, even though it might look like a single transaction for an end-user who just started a charge and paid via Credit Card:

Transaction from Credit Card to Users' Wallet
Transaction from Users' to Charge Point operator to pay for the charge
Transaction from Charge Point operator to Monta (fees)

Types of sender/recipients

At Monta any wallet is linked to either a team (for an end-user that could be their default, personal team) or operator. In a wallet transaction entity you will see this in the fields fromType and toType. Depending on the type, the fields from and to are populated either with an operator or team entity.

Transaction States

Any transaction has a state.

State	Description
reserved	We have reserved an amount (e.g. with credit card provider) to cover for an upcoming charge.
pending	Payment for transaction is still pending,
complete	Transaction is complete (and immutable).
failed	Transaction has failed, ie. we were not able to collect the money from the user's wallet.
other	Fall-back in case new types are added in future.

Transaction Groups

The group indicates if a transaction is related to a deposit, withdrawal or internal transaction.

State	Description
deposit	Money has been deposited to Monta wallet (e.g. from a Credit Card)
withdrawal	Money has been withdrawn from a Monta wallet (e.g. to a Credit Card or bank account)
internal	Indicates that money has been transferred internally between two Monta wallets.
other	Fall-back in case new types are added in future.

Reference Type & Id

You can use the reference type and id to link a transaction to a related event / entity in the Monta system. A typical use case is filtering by referenceType CHARGE and referenceId {charge.id} to retrieve wallet transactions related to the charge.