---
title: "Release FPS inbound transaction [beta]"
method: POST
path: "/v1/payments/fps/release/{endToEndId}"
tags: ["Faster payments"]
---

# Release FPS inbound transaction [beta]

`POST /v1/payments/fps/release/{endToEndId}`

This endpoint moves the suspended transaction amount from additional funds to available balance and marks the transaction as settled.

This endpoint generates a [FPS inbound payment processed](https://developers.pismo.io/events/docs/fps-fps-in-status-change-1) event with status `SETTLED`.

## Path parameters

- `endToEndId` string, required

## Headers

- `Authorization` string, required
- `x-tenant` string, required
- `x-cid` string

## Response `200`

Response Body

- FpsReleaseFpsReleaseResponse
  - `end_to_end_id` string — Client-generated transaction identifier. Must be unique for each transaction.
  - `status` 'SETTLED' — - `SETTLED` - Transaction was completed processed and settled
  - `amount` number, double — Fee amount.

## Other responses

- `400` — Bad Request
- `403` — Forbidden
- `404` — Not Found
- `409` — Conflict
- `429` — Too Many Requests
- `500` — Internal Server Error
- `502` — Bad Gateway

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)