Flutterwave · Arazzo Workflow

Flutterwave Orchestrator Charge And Verify

Version 1.0.0

Initiate a one-call Orchestrator charge then verify the resulting charge status.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub PaymentsPayoutsMobile MoneyCardsAfricaFintechRemittanceVirtual AccountsChargebacksMulti-CurrencyArazzoWorkflows

Provider

flutterwave

Workflows

orchestrator-charge-and-verify
Initiate an Orchestrator charge in one call and verify it reached a final status.
Packages customer, payment method, and charge creation into a single Orchestrator call, then retrieves the charge and branches on whether it succeeded, failed, or is pending authentication.
2 steps inputs: accessToken, amount, currency, customer, paymentMethod, redirectUrl, reference outputs: chargeId, chargeStatus, redirectUrl
1
initiateCharge
Create customer, payment method, and charge in a single Orchestrator call.
2
verifyCharge
Retrieve the charge to confirm its final processing status.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Flutterwave Orchestrator Charge And Verify
  summary: Initiate a one-call Orchestrator charge then verify the resulting charge status.
  description: >-
    Uses the Orchestrator helper to create a customer, payment method, and
    charge in a single request, then retrieves the returned charge to confirm
    whether it settled, failed, or still needs customer authentication. The
    verify step branches on the final status so the caller can fulfil the order
    or surface a redirect URL. 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
sourceDescriptions:
- name: chargesApi
  url: ../openapi/flutterwave-charges-api-openapi.yml
  type: openapi
- name: orchestrationApi
  url: ../openapi/flutterwave-orchestration-api-openapi.yml
  type: openapi
workflows:
- workflowId: orchestrator-charge-and-verify
  summary: Initiate an Orchestrator charge in one call and verify it reached a final status.
  description: >-
    Packages customer, payment method, and charge creation into a single
    Orchestrator call, then retrieves the charge and branches on whether it
    succeeded, failed, or is pending authentication.
  inputs:
    type: object
    required:
    - accessToken
    - amount
    - currency
    - customer
    properties:
      accessToken:
        type: string
        description: OAuth2 client-credentials bearer token for the Authorization header.
      amount:
        type: number
        description: Amount to charge in the major currency unit.
      currency:
        type: string
        description: ISO currency code for the charge.
      customer:
        type: object
        description: Inline customer object (email and optional name/phone) to charge.
      paymentMethod:
        type: object
        description: Inline payment method object (card, mobile money, bank transfer, USSD).
      reference:
        type: string
        description: Optional merchant reference to correlate the charge.
      redirectUrl:
        type: string
        description: Optional URL to return the customer to after authentication.
  steps:
  - stepId: initiateCharge
    description: Create customer, payment method, and charge in a single Orchestrator call.
    operationId: initiateOrchestratorCharge
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    requestBody:
      contentType: application/json
      payload:
        amount: $inputs.amount
        currency: $inputs.currency
        customer: $inputs.customer
        payment_method: $inputs.paymentMethod
        reference: $inputs.reference
        redirect_url: $inputs.redirectUrl
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      chargeId: $response.body#/id
      initialStatus: $response.body#/status
  - stepId: verifyCharge
    description: Retrieve the charge to confirm its final processing status.
    operationId: getCharge
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: id
      in: path
      value: $steps.initiateCharge.outputs.chargeId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      chargeStatus: $response.body#/status
      redirectUrl: $response.body#/redirect_url
    onSuccess:
    - name: chargeSucceeded
      type: end
      criteria:
      - context: $response.body
        condition: $.status == "succeeded"
        type: jsonpath
    - name: chargeFailed
      type: end
      criteria:
      - context: $response.body
        condition: $.status == "failed"
        type: jsonpath
  outputs:
    chargeId: $steps.initiateCharge.outputs.chargeId
    chargeStatus: $steps.verifyCharge.outputs.chargeStatus
    redirectUrl: $steps.verifyCharge.outputs.redirectUrl

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/flutterwave-orchestrator-charge-and-verify-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.