Waiting Execution Transactions #

Returns outgoing transfers that are waiting for additional actions (SCA approval, review, etc.). Use this to build a “pending transfers” view.

Endpoint #

POST https://api-test.10npay.com/app/waiting-execution-transactions

Headers #

• Authorization: Bearer <access_token>
• Content-Type: application/json

Request Body #

Use WaitingExecutionTransactionsRequestModel:

{
  "sourceEntityId": 2077,
  "dataBatch": 1,
  "dataBatchCount": 20,
  "timestampFrom": "2026-05-01T00:00:00Z",
  "timestampTo": "2026-05-22T23:59:59Z",
  "amountFrom": "50",
  "amountTo": "500"
}

Response #

200 OK – WaitingExecutionTransactionsResponse

{
  "transactions": [
    {
      "transactionId": "TNP0007241580001",
      "amount": 120.5,
      "currency": "BGN",
      "paymentNotes": "Invoice #42",
      "waitingReasonCode": "SCA_PENDING",
      "waitingReasonText": "Awaiting app approval"
    }
  ],
  "transactionCount": 3
}

Each item matches the standard Transaction model but may include additional fields like waitingReasonCode, executionBlockedAt, etc.

Errors #

• 400 – invalid filters.
• 401 – missing/expired token.
• 404 – no pending transactions.
• 500 – transient server error.

Usage tips #

• Call this periodically or when the app resumes, so the user sees which transfers still need approval.
• If waitingReasonCode is SCA_PENDING, prompt the user to open the app’s SCA screen.
• Once the transfer moves to “executed”, it disappears from this list and appears in the regular transaction history.