Fintecture · Arazzo Workflow

Fintecture Update Payment Communication

Version 1.0.0

Read a payment, patch its communication while it is still pending, then re-read to confirm.

1 workflow 1 source API 1 provider
View Spec View on GitHub Open BankingPaymentsPSD2FranceAccount InformationPayment InitiationInstant PaymentsSEPASmart TransferRequest to PayBuy Now Pay LaterE-MandatesAccount-to-AccountKYCArazzoWorkflows

Provider

fintecture

Workflows

update-payment-communication
Read a payment, patch its communication if still pending, and confirm.
Reads a payment, branches on whether it is still pending, patches the communication field, and re-reads the payment to confirm.
3 steps inputs: accessToken, communication, paymentId outputs: confirmedCommunication, confirmedStatus, initialStatus
1
getPayment
Read the payment and branch on its status — only a created or pending payment proceeds to the patch step.
2
patchPayment
Patch the payment's communication field while it is still editable.
3
confirmPayment
Re-read the payment to confirm the updated communication took effect.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Fintecture Update Payment Communication
  summary: Read a payment, patch its communication while it is still pending, then re-read to confirm.
  description: >-
    A safe payment-edit flow. It reads a payment and branches on whether it is
    still in an editable state, patches the payment's communication field only
    while it is editable, and re-reads the payment to confirm the change took
    effect. Every step spells out its request inline so the flow can be read and
    executed without opening the underlying OpenAPI description.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-1340.10
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-1340.10
      capability_name: Payment Initiation Management
      spec: fintecture-payments-api-openapi.yml
      confidence: 0.92
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: paymentsApi
  url: ../openapi/fintecture-payments-api-openapi.yml
  type: openapi
workflows:
- workflowId: update-payment-communication
  summary: Read a payment, patch its communication if still pending, and confirm.
  description: >-
    Reads a payment, branches on whether it is still pending, patches the
    communication field, and re-reads the payment to confirm.
  inputs:
    type: object
    required:
    - accessToken
    - paymentId
    - communication
    properties:
      accessToken:
        type: string
        description: A valid PIS-scoped bearer access token.
      paymentId:
        type: string
        description: Identifier of the payment to update.
      communication:
        type: string
        description: New free-form remittance information to write to the payment.
  steps:
  - stepId: getPayment
    description: >-
      Read the payment and branch on its status — only a created or pending
      payment proceeds to the patch step.
    operationId: getPaymentSession
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: payment_id
      in: path
      value: $inputs.paymentId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      status: $response.body#/status
    onSuccess:
    - name: editable
      type: goto
      stepId: patchPayment
      criteria:
      - context: $response.body
        condition: $.status in ["payment_created","payment_pending"]
        type: jsonpath
    - name: locked
      type: end
      criteria:
      - context: $response.body
        condition: $.status in ["payment_initiated","payment_completed","payment_rejected","payment_cancelled","payment_failed"]
        type: jsonpath
  - stepId: patchPayment
    description: Patch the payment's communication field while it is still editable.
    operationId: patchPisV2PaymentSession
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: payment_id
      in: path
      value: $inputs.paymentId
    requestBody:
      contentType: application/json
      payload:
        data:
          attributes:
            communication: $inputs.communication
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      patchedStatus: $response.body#/status
  - stepId: confirmPayment
    description: Re-read the payment to confirm the updated communication took effect.
    operationId: getPaymentSession
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: payment_id
      in: path
      value: $inputs.paymentId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      confirmedCommunication: $response.body#/attributes/communication
      confirmedStatus: $response.body#/status
  outputs:
    initialStatus: $steps.getPayment.outputs.status
    confirmedStatus: $steps.confirmPayment.outputs.confirmedStatus
    confirmedCommunication: $steps.confirmPayment.outputs.confirmedCommunication

Work with this as data

Every workflow 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 arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • 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 workflow
curl "https://apis.io/api/v1/arazzo/fintecture-update-payment-communication-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?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.