For tenants that prefer not to send transactions through our API, we support database-based transaction ingestion. With this integration, you provide us with read-only access to a database containing your transactions. You expose the required transaction data through a SQL view, and our transaction monitoring service periodically queries this view to retrieve transactions.
Recommendation: Create a dedicated SQL view for transaction monitoring instead of granting access to your underlying transaction tables. This gives you control over which data is exposed to the platform.

​
SQL View Schema

The view should return one row per transaction. The source represents the party — wallet, bank account, or card — from which the transaction originated. The fields to provide depend on the value of sourceMethod:
  • If sourceMethod is Wallet, provide sourceWalletIban and either sourceEntityId or sourceEntityCrmId.
  • If sourceMethod is BankAccount, provide sourceBankIban, sourceEntityType, and either sourceEntityNameEn or sourceEntityNameAr.
  • If sourceMethod is Card, provide either sourceEntityId or sourceEntityCrmId.
The target represents the party — wallet, bank account, or card — receiving the transaction. The same requirements that apply to the source fields also apply to the corresponding target fields. The remaining transaction columns are as follows:

​
Important Notes