All newly created payment objects have Conditions, and before any payment objects can be processed all conditions must be finalised. Payment Objects will be stay in state PENDING until all conditions are met. Conditions can be categorised into mandatory conditions and optional conditions. All mandatory conditions are automatically added while optional conditions can be provided upon creation of the payment object.

Mandatory Conditions

  1. KYT (Know Your Transaction): Validates transaction compliance with regulations. This happens automatically and does not require any input from the user.
  2. 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

  1. Four Eyes: This means that a payment has to be approved by a user via the Dashboard. By default this is required, but it can be disabled on a payment level by setting the 'noFourEyesApproval' configuration, or it can be disabled completely on a company level, by setting this in the company configuration.

Custom Conditions

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

  2. Time-Based Conditions (coming soon):

    • Scheduled Date: Processes payment after a specific time, and will be triggered by the Scheduler.

Example request body

{
    "amount":  12000,
    "currency": "EUR",
    "payer": { "type": "SPLIT" },
    "payee": { "id": "ACC_271545453577" },
    "config": {
        "noFourEyesApproval": true,
        "conditions": [
            { "type":"Tag", "value": "order-x0013389829-delivered"}
        ]
    }
}

Condition Workflow

  1. Setting Conditions: When creating a payment, core conditions are automatically added, but you can add additional conditions when creating the payment via the config in the payment object creation request.
  2. Evaluation: Upon the source data of the condition changing, all the conditions on the payment are evaluated.
  3. Execution: Once all conditions are met, payment processing is started automatically.