Transactions

Verify a Transaction

POST

POST Transactions

/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.

Payload

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 empty
  • timestamp - UNIX timestamp in milliseconds of when the transaction took place
  • transactionState - The state of the transaction, set to CREATED by default. More details here
  • originUserId - 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 endpoint
  • destinationUserId - 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 endpoint
  • originAmountDetails - Details of the amount being sent from the origin
  • destinationAmountDetails - Details of the amount being received at the destination
  • originPaymentDetails - 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.

Query parameters

validateOriginUserIdenumOptional
Boolean string whether Flagright should validate if provided originUserId exist. True by default
Allowed values: truefalse
validateDestinationUserIdenumOptional
Boolean string whether Flagright should validate if provided destinationUserId exist. True by default
Allowed values: truefalse

Request

This endpoint expects an object.
type
enumRequired
transactionId
stringRequired
Unique transaction identifier
timestamp
doubleRequired
Timestamp of when transaction took place
originUserId
stringOptional
UserId for where the transaction originates from
destinationUserId
stringOptional
UserId for transaction's destination. In other words, where the value is being transferred to.
transactionState
enumOptional
Model for transaction states. E.g. Processing, Refunded, Successful etc.
originAmountDetails
objectOptional
Model for transaction amount details
destinationAmountDetails
objectOptional
Model for transaction amount details
originPaymentDetails
unionOptional
Payment details of the origin. It can be a bank account number, wallet ID, card fingerprint etc.
destinationPaymentDetails
unionOptional
Payment details of the destination. It can be a bank account number, wallet ID, card fingerprint etc.
relatedTransactionIds
list of stringsOptional
IDs of transactions related to this transaction. Ex: refund, split bills
productType
stringOptional
Type of produce being used by the consumer (ex wallets, payments etc)
promotionCodeUsed
booleanOptional
Whether a promotion code was used or not the transaction
reference
stringOptional
Reference field for the transaction indicating the purpose of the transaction etc.
originDeviceData
objectOptional
Model for device data
destinationDeviceData
objectOptional
Model for device data
tags
list of objectsOptional
Additional information that can be added via tags

Response

This endpoint returns an object
executedRules
list of objects
Unique transaction identifier
hitRules
list of objects
Unique transaction identifier
status
enum
Model for rule action if a rule is hit. This is returned in the API response and can be configured on Console by operational accounts like a Compliance Analyst
Allowed values: ALLOWFLAGBLOCKSUSPEND
transactionId
string
Transaction ID that the results pertain to
message
stringOptional
riskScoreDetails
objectOptional

Errors