Skip to main content

​
Return Payments You Can’t Process

Sometimes you receive payments that can’t be credited — closed accounts, compliance blocks, or beneficiary disputes. Inventi handles the return protocol so you can focus on the decision.
What happens when you return a payment:
  1. You identify an inbound payment that can’t be credited
  2. You submit a return request via API with a reason code
  3. Inventi sends a PACS.004 return message through CENTROlink or EKS
  4. Funds are returned to the originating bank

​
Use Cases

Account Issues

Account closed, blocked, or invalid credentials

Compliance

AML flags or sanctions screening failures

Disputes

Beneficiary disputes the incoming payment

​
API Reference

Return Transaction

Initiate a return for an inbound SEPA CT

Transaction Status Webhook

Track return transaction lifecycle

Get Transaction

Retrieve transaction details

Transaction Status History

View complete status timeline

​
How It Works

When you initiate a return, the platform validates the original transaction, creates a return transaction, and sends a PACS.004 message to the originating bank.

​
Initiate a Return

curl -X POST https://api.pgw-sandbox.finventi.com/v1/transactions/{trx_id}:return \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{
    "reason": "AC04",
    "additionalInfo": "Account closed"
  }'
The platform validates that the transaction exists, is inbound, and is eligible for return before processing.

​
Return Statuses

StatusDescription
CreatedReturn initiated
AcceptedClearing system accepted
CompletedFunds returned to originator

​
Data Model

Store these fields for complete audit trails:
​
trx_id
string
required
Original inbound transaction ID
​
return_trx_id
string
Return transaction ID (if separate from original)
​
reason
string
required
Return reason code (ISO 20022)
​
status_history
array
required
Append-only list of status transitions

​
Integration Checklist

1

Implement idempotent webhook handler

Upsert transactions by ID to handle duplicate deliveries safely
2

Store return metadata

Persist return reason codes and timestamps for compliance
3

Link related transactions

Maintain references between original and return transactions for reporting

​
What’s Next?

You now understand how to return inbound payments. Complete your exception handling with cancellation flows and reconciliation:

Cancel Outbound Payments

Request cancellation of your outgoing payments

Respond to Cancellations

Handle incoming cancellation requests

Track and Reconcile

Monitor transactions and verify with Nostro statements