/transactions
endpoint allows you to operate on the Transaction entity.
In order to pass the payload of a transaction to Flagright and verify the transaction, you will need to call this endpoint with the transaction payload. Not all fields are mandatory, you will only need to pass in the fields that you have and are relevant for your compliance setup.
Here are some of the most used payload fields explained (you can find the full payload schema below with 1 line descriptions):
type
: Type of transaction (Ex: WITHDRAWAL
, DEPOSIT
, TRANSFER
etc).transactionId
- Unique Identifier for the transaction. Flagright API will generate a transactionId
if this field is left emptytimestamp
- UNIX timestamp in milliseconds of when the transaction took placetransactionState
- The state of the transaction, set to CREATED
by default. More details hereoriginUserId
- Unique identifier (if any) of the user who is sending the money. This user must be created within the Flagright system before using the create a consumer user or create a business user endpointdestinationUserId
- Unique identifier (if any) of the user who is receiving the money. This user must be created within the Flagright system before using the create a consumer user or create a business user endpointoriginAmountDetails
- Details of the amount being sent from the origindestinationAmountDetails
- Details of the amount being received at the destinationoriginPaymentDetails
- Payment details (if any) used at the origin (ex: CARD
, IBAN
, WALLET
etc). You can click on the dropdown next to the field in the schema below to view all supported payment types.destinationPaymentDetails
- Payment details (if any) used at the destination (ex: CARD
, IBAN
, WALLET
etc). You can click on the dropdown next to the field in the schema below to view all supported payment types.