Paystack · Arazzo Workflow

Paystack Create Recipient and Initiate Transfer

Version 1.0.0

Create a transfer recipient from bank details, initiate a transfer to it, then verify the transfer by reference.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub PaymentsAfricaFintechRecurring BillingMarketplacesPayoutsMobile MoneyStripeArazzoWorkflows

Provider

paystack

Workflows

create-recipient-and-initiate-transfer
Register a payout recipient, send a transfer, then verify its status.
Creates a NUBAN transfer recipient, initiates a transfer to its recipient code, and verifies the outcome by reference, branching on success.
3 steps inputs: account_number, amount, bank_code, currency, name, reason, reference outputs: recipientCode, transferCode, verifiedStatus
1
createRecipient
Create a NUBAN transfer recipient from the supplied bank details.
2
initiateTransfer
Initiate a transfer from the Paystack balance to the new recipient.
3
verifyTransfer
Verify the transfer by reference and branch on whether it succeeded.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Paystack Create Recipient and Initiate Transfer
  summary: Create a transfer recipient from bank details, initiate a transfer to it, then verify the transfer by reference.
  description: >-
    The core payout flow. A transfer recipient is created from a bank account,
    a transfer is initiated from the Paystack balance to that recipient, and the
    transfer is then verified by its reference. A branch inspects the verified
    status to separate successful payouts from those still pending or failed.
    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: transferApi
  url: ../openapi/paystack-transfer-api-openapi.yml
  type: openapi
- name: transferRecipientApi
  url: ../openapi/paystack-transfer-recipient-api-openapi.yml
  type: openapi
workflows:
- workflowId: create-recipient-and-initiate-transfer
  summary: Register a payout recipient, send a transfer, then verify its status.
  description: >-
    Creates a NUBAN transfer recipient, initiates a transfer to its recipient
    code, and verifies the outcome by reference, branching on success.
  inputs:
    type: object
    required:
    - name
    - account_number
    - bank_code
    - amount
    properties:
      name:
        type: string
        description: Recipient's name.
      account_number:
        type: string
        description: Recipient's bank account number.
      bank_code:
        type: string
        description: Recipient's bank code from the List Banks endpoint.
      currency:
        type: string
        description: Currency for the receiving account (defaults to NGN).
      amount:
        type: string
        description: Amount to transfer in the smallest currency unit, as a string.
      reason:
        type: string
        description: Narration shown for the transfer.
      reference:
        type: string
        description: Unique lowercase identifier for the transfer.
  steps:
  - stepId: createRecipient
    description: Create a NUBAN transfer recipient from the supplied bank details.
    operationId: transferrecipient_create
    requestBody:
      contentType: application/json
      payload:
        type: nuban
        name: $inputs.name
        account_number: $inputs.account_number
        bank_code: $inputs.bank_code
        currency: $inputs.currency
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      recipientCode: $response.body#/data/recipient_code
  - stepId: initiateTransfer
    description: Initiate a transfer from the Paystack balance to the new recipient.
    operationId: transfer_initiate
    requestBody:
      contentType: application/json
      payload:
        source: balance
        amount: $inputs.amount
        recipient: $steps.createRecipient.outputs.recipientCode
        reason: $inputs.reason
        reference: $inputs.reference
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      transferCode: $response.body#/data/transfer_code
      reference: $response.body#/data/reference
      transferStatus: $response.body#/data/status
  - stepId: verifyTransfer
    description: Verify the transfer by reference and branch on whether it succeeded.
    operationId: transfer_verify
    parameters:
    - name: reference
      in: path
      value: $steps.initiateTransfer.outputs.reference
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      verifiedStatus: $response.body#/data/status
    onSuccess:
    - name: transferSucceeded
      type: end
      criteria:
      - context: $response.body
        condition: $.data.status == "success"
        type: jsonpath
    - name: transferPending
      type: end
      criteria:
      - context: $response.body
        condition: $.data.status != "success"
        type: jsonpath
  outputs:
    recipientCode: $steps.createRecipient.outputs.recipientCode
    transferCode: $steps.initiateTransfer.outputs.transferCode
    verifiedStatus: $steps.verifyTransfer.outputs.verifiedStatus

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/paystack-create-recipient-and-initiate-transfer-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.