Skip to the operations

Banking

Asaas in a decision flow.

7 Asaas operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Banking
Type
Integration
Authentication
API key
Test environment
Separate sandbox host

Who they are

Brazilian payment and receivables platform for small businesses and fintechs.

Asaas issues boletos, Pix charges and card payments, chases them when they go unpaid, and settles the money into the merchant's account. It is used mainly by Brazilian small businesses and by fintechs that need a billing stack without becoming a payment institution themselves. The same account carries the charge history, which is a record of what a customer actually paid rather than what they promised.

What a flow can call

7 operations, each one a step you can place on the canvas.

  1. POST/customers

    Create a customer

    Registers the payer. cpfCnpj is the field Asaas deduplicates on, so passing it stops a second application from the same person creating a second customer.

  2. GET/customers?cpfCnpj=$data.cpf

    Find a customer

    Looks a payer up by document. Run it before creating one — Asaas rejects a duplicate rather than returning what is already there, so a flow without this step fails on every returning applicant.

  3. POST/payments

    Raise a charge

    Creates the charge the decision approved. billingType BOLETO, PIX, CREDIT_CARD or UNDEFINED, where UNDEFINED lets the payer choose.

  4. GET/payments/$data.asaas_payment_id

    Check a charge's status

    The state of one charge. This is the read a renewal decision makes: PENDING before the due date is normal, OVERDUE after it is the signal that matters.

  5. GET/payments?customer=$data.asaas_customer_id

    List a customer's charges

    Every charge raised against one payer. This is the repayment history a limit-increase decision should read — how many were paid late, and by how much, is evidence no bureau file carries about your own book.

  6. GET/finance/payment/statistics?customer=$data.asaas_customer_id&status=OVERDUE

    Read totals across charges

    Totals rather than rows — how much is outstanding, overdue or received for a filter.

  7. GET/finance/balance

    Read the account balance

    The Asaas account's own balance. Useful for an operational rule rather than a credit one — a disbursement flow that should stop before it overdraws the funding account.

Where it sits in the decision

Banking calls have a natural place in a flow.

Bank data answers the question a stated income cannot: what actually arrives, how regularly, and what leaves again. It is usually pulled once per application and then read by several nodes — affordability, income verification, any rule about balance volatility — so it is worth fetching early and deriving from, rather than calling repeatedly.

Whatever Asaas returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Asaas as a connection authenticating with an API key.
  • 02Asaas runs a separate sandbox host, so a Sandbox flow can exercise the real call without touching production.
  • 03Place a Connection node and pick an operation — “Create a customer” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Asaas in a flow.

How do I connect Asaas to a decision flow?

Add Asaas as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Asaas in a decision without ever seeing the secret.

Can I test Asaas without touching production?

Yes. Asaas runs a separate sandbox host, so a flow executing in Sandbox can make the real call against test credentials and you can read the actual response shape in the trace before anything reaches a customer. The flow does not change when it graduates — only which credentials answer.

What can a flow call on Asaas?

7 operations, including “Create a customer”, “Find a customer”, “Raise a charge”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Create a customer”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Asaas be called?

Bank data answers the question a stated income cannot: what actually arrives, how regularly, and what leaves again. It is usually pulled once per application and then read by several nodes — affordability, income verification, any rule about balance volatility — so it is worth fetching early and deriving from, rather than calling repeatedly.

Also in Banking

Ready when you are

Wire Asaas into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs