Sylvester, E. (Elwin) 17:14 (0 minutes ago) to me
Inspiration
Every month, diaspora families send money home for school fees, groceries, medical bills, rent, emergencies, and small business support. But the real pain is not just the transfer fee. It is the coordination around the transfer. A mother in Nairobi needs help but waits days before calling because she does not want to feel like a burden. A sender in Europe wants to help, but has to compare multiple apps, check rates manually, manage family expectations, and still wonder whether the right amount arrived through the right route.
For individuals, this is emotionally heavy. For teams, operators, diaspora organisations, and fintech support workflows, it becomes operationally messy.
Requests come in through messages. Approvals happen elsewhere. Quotes are checked manually. Exceptions are handled in private chats. Audit trails are fragmented.
We asked a simple question: What if family-support remittance could be coordinated directly inside Slack — with AI understanding the request, ARP enforcing the rules, and humans approving only when needed?
That became the Slack Agent version of St4bl. St4bl removes the shame from family remittance and turns Slack into a safe coordination layer for quotes, approvals, exceptions, and audit visibility.
Slack is the channel. AI reasons. ARP enforces. Partner rails execute.
What it does
St4bl for Slack is an AI-powered family-support and remittance workflow agent. It lets users interact with the Agent Remittance Protocol directly inside Slack using simple commands and natural-language requests.
Example: /st4bl quote KES 2,000 to mum for groceries
The Slack Agent checks:
- Is this recipient approved?
- Is the amount within the sender’s rules?
- Which rail gives the best net value after fees and FX?
- Does the request need human approval?
- Has the transfer already been staged?
- Is there an audit trail for this action?
The Slack Agent can:
- request remittance quotes
- stage transfers
- trigger approval workflows
- show policy decisions
- display audit summaries
- escalate exceptions to an operator
The Slack Agent cannot move money directly. Every action goes through ARP’s deterministic policy engine, state machine, execution locks, idempotency checks, and audit ledger. For the user, the experience is simple:
Ask in Slack. Review the route. Approve if needed. Let ARP enforce the rules.
How we built it
We built the Slack integration as a channel adapter on top of the existing Agent Remittance Protocol. The architecture is intentionally layered:
Slack → Slack Agent → MCP Client → ARP MCP Server → ARP Deterministic Core → Rail Adapters → Audit Ledger
The Slack Agent provides the conversational interface. The AI layer parses intent and explains the workflow. The MCP boundary exposes safe ARP tools. ARP enforces the financial rules. The partner rails handle execution only after ARP allows it.
The core principle is: AI reasons. MCP exposes tools. ARP enforces. Partner rails execute. The Slack workflow supports:
- Quote A Slack user asks for a quote using a command such as: /st4bl quote KES 2,000 to mum for groceries
- Intent Parsing The agent extracts the recipient, amount, currency, and purpose.
- Policy Check ARP checks sender-defined rules, including approved recipients, limits, payout methods, and approval requirements.
- Rail Quote ARP compares available rails and calculates the route that delivers the best net value to the recipient.
- Stage If the request is valid, ARP stages the transfer and creates a transfer ID.
- Approval Flow If approval is required, the Slack Agent posts an approval request with the amount, recipient, rail, estimated fees, and reason approval is needed.
- Execute Execution only happens if ARP policy allows it or a valid approval is provided.
- Audit Every request, quote, policy decision, approval, and execution result is written to the audit ledger.
St4bl for Slack is built on:
- Slack slash commands
- Slack approval workflows
- MCP-style ARP tool calls
- deterministic policy enforcement
- staged transfer state management
- idempotency keys
- execution locks
- append-only audit logging
- rail adapters for remittance routing
- AI-assisted intent parsing and explanation generation
Slack makes the workflow collaborative.
ARP makes the workflow safe.
Challenges we ran into
Making Slack safe for financial workflows
Slack is an excellent collaboration surface, but money movement requires strict boundaries. The key challenge was ensuring that a Slack command could never become an uncontrolled payment trigger. We solved this by making Slack a channel adapter only.
Slack can request a quote, stage a transfer, ask for approval, and display an audit summary. But Slack does not execute funds directly. Every financial action must pass through ARP’s deterministic policy engine and state machine. This keeps the workflow useful without making the communication channel the source of financial authority.
Separating AI reasoning from execution
AI is powerful for understanding messy human requests, but payments need deterministic enforcement. The agent can understand a message such as: “Can we send KES 2,000 to mum for groceries?” But the agent cannot decide by itself that money should move. ARP checks whether the recipient is approved, whether the amount is within limits, whether approval is required, and whether the staged transfer is valid.
The separation is simple: The AI understands. ARP decides what is allowed.
Designing human-in-the-loop approval
Some requests should not execute automatically. If a request exceeds a sender’s limit, involves a new recipient, or requires additional review, the Slack Agent creates an approval flow.
The approval message shows:
- recipient
- amount
- selected rail
- estimated fees
- estimated net received
- reason approval is required
- transfer ID
This makes Slack a natural place for human review without compromising the safety model.
Keeping the product human
The original product insight was emotional: family support should not require shame, guesswork, or repeated awkward conversations. The Slack version keeps that insight, but adds an operational layer.
For families, Slack can coordinate approvals. For operators, Slack can manage exceptions. For teams, Slack can expose auditability and shared visibility. The challenge was preserving the dignity of the original consumer use case while making the workflow useful for collaborative environments.
Accomplishments that we’re proud of
A Slack-native remittance workflow
We added Slack as a controlled surface for ARP workflows. Users can request quotes, stage transfers, trigger approvals, and inspect audit summaries without leaving Slack. This turns remittance from a private, fragmented process into a structured workflow that can be reviewed, approved, and audited.
Clear safety boundary
We are proud that the Slack Agent does not move money directly. Slack is not the execution layer. The AI is not the execution layer. ARP remains the enforcement layer. That distinction makes the system safer, easier to explain, and more suitable for real financial workflows.
Human-in-the-loop approvals
The Slack approval flow makes out-of-policy requests visible and reviewable. Instead of failing silently or pushing users into manual back-and-forth, St4bl creates a clear approval moment inside Slack. This is especially useful for support teams, diaspora organisations, community treasurers, and fintech operators managing remittance exceptions.
Auditability by default
Every major event is traceable:
- request
- parsed intent
- policy decision
- quote
- staged transfer
- approval
- rejection
- execution result
- audit summary
This makes the system suitable for environments where transparency matters.
More than a chatbot
St4bl for Slack is not a chatbot that talks about remittance. It is a workflow agent that connects Slack to a deterministic remittance protocol through safe tool boundaries. The Slack Agent coordinates. ARP enforces.
Partner rails execute only when allowed.
What we learned
Slack is powerful when it becomes the workflow surface
Financial workflows often happen across too many places: messaging apps, dashboards, spreadsheets, payment portals, and private chats. Slack gives those workflows a shared operational surface. By bringing quote requests, approval decisions, and audit summaries into Slack, the process becomes easier to coordinate and easier to trust.
AI should explain and coordinate, not control funds
The best role for AI in this system is orchestration. The agent helps users express intent, understand options, and move through the workflow. But the backend must remain deterministic. That is especially important in remittance, where mistakes can create financial, regulatory, and trust problems.
Approval is a product feature, not friction
In consumer apps, approval is often treated as friction. In financial workflows, approval creates trust. The Slack Agent makes approvals explicit, readable, and auditable. That makes users more comfortable with automation because the boundaries are visible.
The recipient still matters
Even in the Slack version, the recipient remains central. The system optimises for what the recipient actually receives, not just what the sender pays. That means comparing rails, checking fees, and factoring in recipient-side payout logic. The goal is not simply to send money. The goal is to deliver useful support safely.
What’s next for St4bl
Deepen the Slack approval workflow
The next step is to make the Slack Agent more powerful as an approval and exception-management surface. Planned improvements include:
- interactive approval buttons
- approval channel routing
- role-based approvers
- richer transfer summaries
- exception escalation
- audit search inside Slack
Connect Slack to live ARP deployments
The current Slack integration is designed as a safe channel adapter. Next, we will connect it more deeply to deployed ARP environments so teams can manage real remittance workflows through Slack while preserving deterministic enforcement. The Slack Agent will remain non-custodial and policy-controlled.
Expand operator use cases
Beyond family remittance, the Slack Agent can support:
- diaspora community fund coordination
- NGO cash-disbursement approvals
- fintech support operations
- treasury exception workflows
- remittance compliance review
- payout failure escalation
Slack becomes the shared surface for human-in-the-loop financial coordination.
Launch Treasury workflows
The next product layer is St4bl Treasury. Treasury allows senders or organisations to hold value in hard currency through regulated partner infrastructure and convert only when support is actually needed. Inside Slack, this creates workflows such as:
- request support
- check policy
- review available balance
- approve conversion
- select route
- stage transfer
- audit execution Treasury is not a separate product. It is an upgrade to the same family-support and remittance workflow.
Build the family-support layer across channels
St4bl is becoming a channel-agnostic family-support layer. Telegram works for recipients and households. Slack works for teams, operators, approvals, and exception handling. The same core remains:
- recipient request
- sender policy
- AI reasoning
- MCP tool boundary
- ARP enforcement
- partner rail execution
- auditability
One corridor. One workflow. Multiple channels. One truth: Support should be easy to request, safe to approve, and transparent to execute.
Log in or sign up for Devpost to join the conversation.