Revolut [PREVIEW] Transaction outcomes API

Return what a Revolut-card transaction produced. :::warning [Pre-release preview] This is a pre-release preview of upcoming documentation. The features, workflows, and UI described here are subject to change before the final release. :::

Operations 1

POST /transaction-outcomes/search [PREVIEW] Fetch transaction outcomes for a transaction #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/revolut:revolut-preview-transaction-outcomes-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

revolut-preview-transaction-outcomes-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: '[PREVIEW] Revolut Wallet Partner Callbacks [PREVIEW]…'
  version: '2026-07-01'
  description: ':::warning [Pre-release preview]

    This is a pre-release preview of upcoming documentation.

    The features, workflows, and UI described here are subject to change before the final release.

    :::


    Endpoints you host and Revolut calls. Implement them to this contract so we can pull data

    on demand. Revolut is always the client; you are the server.


    - **Fetch transaction outcomes**: `POST /transaction-outcomes/search`. Called after a customer pays

    with a Revolut card, we ask what `passes` and `digital_receipts` that transaction produced.

    - **Fetch a pass update**: `GET /passes/{partner_reference}`. We poll for the current state of

    a pass so we can refresh it in the customer''s wallet.


    Passes are identified by **your own** `partner_reference`, which is the value you set when you return a

    pass here, and that Revolut echoes back when it calls the companion Revolut-hosted API

    (`/docs/api/revolut-wallet-partner`).


    The base URL in `servers` is illustrative; you register your real base URL during onboarding.


    Passes in transaction outcomes and poll responses can use any supported format: `revpass`

    (native semantic model), `pkpass_base64`, `pkpass_url`

    (URL to download a .pkpass file), or `walletobjects_json` (Wallet Objects resource family and

    class/object pair).

    The `format` field on each pass selects the encoding.


    :::info

    Start with the Revolut Wallet guide and Get started to onboard your business.

    :::'
  contact:
    name: Revolut Wallet partner onboarding
    email: revwallet-partner-onboarding@revolut.com
    url: https://developer.revolut.com
servers:
- url: https://passes.partner.example/revolut-wallet
  description: Your registered base URL (example)
security:
- mtls: []
- mtls: []
  jws: []
- jws: []
- oauth2:
  - passes.read
- oauth2:
  - passes.read
  mtls: []
tags:


# --- truncated at 32 KB (102 KB total) ---
# Full source: https://artifacts.apis.io/revolut/openapi/revolut-preview-transaction-outcomes-api-openapi.yml