Efí Pay (Gerencianet) · Arazzo Workflow

Efí Bill Payment by Bar Code

Version 1.0.0

Decode a boleto bar code, pay it from the account, and reconcile the status.

1 workflow 1 source API 1 provider
View Spec View on GitHub PaymentsPixBoletoSubscriptionRecurring BillingMarketplaceSplit PaymentsOpen FinanceBanking as a ServiceAccount OpeningBill PaymentsCNABBrazilFintechArazzoWorkflows

Provider

gerencianet

Workflows

bill-payment
Decode a bar code, pay the bill, and reconcile the payment status.
Authenticates, decodes the supplied bar code, requests payment for it, and reads the payment back to confirm its settlement status.
4 steps inputs: clientId, clientSecret, codBarras, paymentDate outputs: idPagamento, status, value
1
authenticate
pagamentosAuthorize
Exchange the client_id and client_secret for an OAuth2 access token using the client_credentials grant required by the Pagamentos API.
2
decodeBarCode
Decode the bar code to recover the bill amount and due date before committing to the payment.
3
requestPayment
Submit the payment request for the decoded bar code with the desired debit date. The server returns a payment id.
4
reconcilePayment
Read the payment back by its id to reconcile the final settlement status.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Efí Bill Payment by Bar Code
  summary: Decode a boleto bar code, pay it from the account, and reconcile the status.
  description: >-
    The Efí Pay Pagamentos flow for paying a boleto or concessionária bill from
    the account balance. The workflow authenticates, decodes the bar code (linha
    digitável) to recover the amount and due date, submits the payment request
    for that bar code, and reads the resulting payment back by its id to
    reconcile the settlement status. 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: efiPagamentosApi
  url: ../openapi/_original/efi-pagamentos-openapi.yml
  type: openapi
workflows:
- workflowId: bill-payment
  summary: Decode a bar code, pay the bill, and reconcile the payment status.
  description: >-
    Authenticates, decodes the supplied bar code, requests payment for it, and
    reads the payment back to confirm its settlement status.
  inputs:
    type: object
    required:
    - clientId
    - clientSecret
    - codBarras
    properties:
      clientId:
        type: string
        description: The OAuth2 client_id issued for the Efí Pay account.
      clientSecret:
        type: string
        description: The OAuth2 client_secret issued for the Efí Pay account.
      codBarras:
        type: string
        description: The boleto/concessionária bar code (linha digitável) to pay.
      paymentDate:
        type: string
        description: The desired debit date for the payment (dataPagamento), YYYY-MM-DD.
  steps:
  - stepId: authenticate
    description: >-
      Exchange the client_id and client_secret for an OAuth2 access token using
      the client_credentials grant required by the Pagamentos API.
    operationId: pagamentosAuthorize
    requestBody:
      contentType: application/json
      payload:
        grant_type: client_credentials
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      accessToken: $response.body#/access_token
  - stepId: decodeBarCode
    description: >-
      Decode the bar code to recover the bill amount and due date before
      committing to the payment.
    operationId: payDetailBarCode
    parameters:
    - name: Authorization
      in: header
      value: Bearer $steps.authenticate.outputs.accessToken
    - name: codBarras
      in: path
      value: $inputs.codBarras
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      value: $response.body#/value
      dueDate: $response.body#/dueDate
  - stepId: requestPayment
    description: >-
      Submit the payment request for the decoded bar code with the desired debit
      date. The server returns a payment id.
    operationId: payRequestBarCode
    parameters:
    - name: Authorization
      in: header
      value: Bearer $steps.authenticate.outputs.accessToken
    - name: codBarras
      in: path
      value: $inputs.codBarras
    requestBody:
      contentType: application/json
      payload:
        dataPagamento: $inputs.paymentDate
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      idPagamento: $response.body#/idPagamento
      status: $response.body#/status
  - stepId: reconcilePayment
    description: >-
      Read the payment back by its id to reconcile the final settlement status.
    operationId: payDetailPayment
    parameters:
    - name: Authorization
      in: header
      value: Bearer $steps.authenticate.outputs.accessToken
    - name: idPagamento
      in: path
      value: $steps.requestPayment.outputs.idPagamento
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      status: $response.body#/status
      value: $response.body#/valor
  outputs:
    idPagamento: $steps.requestPayment.outputs.idPagamento
    status: $steps.reconcilePayment.outputs.status
    value: $steps.reconcilePayment.outputs.value

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/gerencianet-bill-payment-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.