Overview

This document covers the functionalities and constraints of the Suspense Queue feature of the Paynetics Transfers product. It provides comprehensive information on how to integrate and operate it,

Product Description

Purpose of Suspense Queue

Paynetics Suspense Queue applies only to incoming transactions from third-party institutions. Paynetics Suspense Queue enables Partners to employ their compliance and fraud monitoring systems and processes by giving the ability to scan incoming transactions and decide if they want to return it to sender or let it be processed.

Supported Payment Rails and Currencies

The supported payment rails are SEPA Credit Transfer (SCT), SEPA Instant and Faster Payments (FPS).

Please, note, that if an incoming SEPA Instant transfer, upon review, is rejected, that transfer will be returned via SEPA SCT.

The supported transfer currencies are EUR and GBP.

Review Window

All transactions placed in Suspense Queue must be reviewed by the Partner within ten business days of entering the queue. Any transaction left in the queue after the tenth business day will be manually returned by Paynetics.

Reporting and reconciliation

You can track all transactions in the queue via API real-time.

Technical Integration

Prior to enabling Suspense Queue, Partners must have an approval of their compliance and fraud monitoring processes by Paynetics. Also, Partners must sign the relevant legal agreements. Once the agreements are signed, then you will be provided with access to your Sandbox instance where you can carry on the integration. Following the integration, you will run a set of tests, to be validated by Paynetics, and you will be ready to move to production.

Transaction entering Suspense Queue

Based on instance level configuration the IWT will be placed in queue where external system can make decision what must have done with the transfer. The Paynetics System will automatically return the transfer in case the account is not found, closed, or blocked.

Once the transfer has been added into the queue, then the TRANSACTION.SUSPENDED webhook will be sent to external system with token (identifier) of the queue record. In case the webhook has not been received from the first time the system will try to resend it 3 more times. You can use the queue token for managing the lifecycle of each queue entry.

Retrieve ALL transactions in Suspense Queue

You can get a list of all transactions within the Suspense Queue (based on your pagination requirements) via the endpoint GET /v2/queue/{page}/{limit} of the Transfers API.

Retrieve single transaction in Suspense Queue

You can get a specific transaction within the Suspense Queue via the endpoint GET /v2/queue/{token} where the token is provided via the TRANSACTION.SUSPENDED webhook.

Accepting a transaction in Suspense Queue

You can accept a transaction, release it from the Suspense Queue and direct it for processing by Paynetics via the endpoint POST /v2/queue/{token}/process.

Declining a transaction in Suspense Queue

You can decline a transaction, release it from the Suspense Queue and direct Paynetics to generate a return via the endpoint DELETE   /v2/queue/{token}/return.