All payment objects that are created have Conditions, and before any payment objects can be processed all conditions must be finalised. Payment Objects will be stay in the state PENDING until all conditions are met. Conditions can either be categorised into either mandatory conditions or optional conditions. All mandatory conditions are automatically added while optional conditions can be provided upon creation of the payment object.
Mandatory Conditions
- KYT (Know Your Transaction): Validates transaction compliance with regulations. This happens automatically and does not require any input from the user.
- Signing: If the target account has a payout IBAN, it requires signing in the app. If not, this conditions will be automatically met.
Optional Conditions
-
Four Eyes: Requires separate approval from a second user, via the Dashboard. This is only required if four eyes is configured for the payment or at the company level. By default this is required, but can be changed via the noFourEyesApproval configuration that can be set on a payment object or company level.
-
Tags: Attach tags to singular or multiple payments (e.g., "payments-for-march"). All payment objects with the specified group tag would be triggered. This can be triggered via the condition tag endpoint.
-
Time-Based Conditions (coming soon):
- Scheduled Date: Processes payment after a specific time, and will be triggered by the Scheduler.
Condition Workflow
- Setting Conditions: When creating a payment, core conditions are automatically added and additional special conditions can be added in the create payment api. These conditions can be added as a config in the payment object creation request.
- Evaluation: Upon the source data of the condition changing, all the conditions on the payment are evaluated.
- Execution: Once all conditions are met, payment processing is started automatically.