Keep travel in the flow.
A booking workflow reaches a payment step.
Review a card payment with clear purchase limits. NGN artwork is decorative.
YOUR AI. YOUR TERMS.
Bring your own AI assistant. Taska Plug connects it to payments through MCP.
In development · MCP payment connection layer. Bank transfers and virtual cards are intended for launch.
One payment layer. Different workflows.
Choose a scene, or let the story play.
ONE PLUG. CONNECTED WORKFLOWS.
Explore how payments could connect to your AI workflow. Choose a connection to explore its payment flow.
Stablecoins are planned; availability and supported integrations are unconfirmed.
YOUR WORKFLOW. WITH PAYMENTS BUILT IN.
A supplier invoice. A travel booking. A payment step in your own process. Plug is being designed to fit the workflow, with clear permission before money moves.
A booking workflow reaches a payment step.
Review a card payment with clear purchase limits. NGN artwork is decorative.
Payment details sit between the workflow and its next task.
Keep the recipient, amount and permission together.
A customer says paid. The workflow needs more than a message.
Match a receipt to its customer payment.
A payment request should not become a blank cheque.
Set clear limits and review terms for each payment request.
Cross-border workflows need explicit payment terms.
Stablecoin payments are planned. Assets, networks, fees and availability are not confirmed. Roadmap artwork only.
BUILT FOR YOUR WORKFLOW.
Bank transfers and virtual-card payments are intended for launch. Stablecoin support remains planned.
Sending and receiving bank transfers, with virtual-card payments for compatible workflows. In development; supported integrations and availability will be confirmed before release.
Stablecoin sending and receiving are planned. Supported assets, networks, markets, fees and launch timing are not confirmed.
BRING THE ASSISTANT YOU USE.
Taska Plug is being built as a payment connection layer and MCP server, not a separate chatbot or model. Your compatible assistant stays the conversation interface; Plug provides the intended payment tools and permission boundaries.
Early-access setup · supported assistants, account and wallet options will be confirmed before launch.
Start with an MCP-enabled assistant or workflow that supports the required tools. Compatibility will need to be confirmed.
The intended setup links Taska with an eligible account or wallet through an authorized connection flow.
Define recipients, amounts, scope and limits. MCP tool support does not itself grant permission to move money.
Check the requested payment and its mandate before approving or declining. Keep uncertain outcomes pending until they are resolved.
A FEW CLEAR ANSWERS
No approved answer is available yet.
No approved answer is available yet.
No approved answer is available yet.