---
name: pulpopay
description: PulpoPay, Pulpo's fuel card and payments product. Account status and balances, cards and their balances and movements, wallet movements, fuel load checks and compliance score, spending controls, funding requests from drivers and approving them, funding or withdrawing cards, locking cards. Money is involved: reads are free, every movement of money or card change needs explicit confirmation. Use for any PulpoPay or fleet card question.
---

# PulpoPay

PulpoPay issues cards to drivers and moves money between the company account and those cards. Reading is safe. Writing here moves real money or changes card access, and none of it can be undone from this connector.

## Reading

- **Is it on, and where is it:** `pulpo_get_pulpopay_status` (enabled or not), `pulpo_get_pulpopay_account_onboarding`, `pulpo_get_pulpopay_account_settings` (limits, allowed merchants). If PulpoPay is not enabled, say so and stop.
- **Money:** `pulpo_get_pulpopay_account_balances` (total, available, used, currency), `pulpo_get_pulpopay_account_statements` (paged), `pulpo_get_pulpopay_card_balance` (by payment method id).
- **Cards:** `pulpo_get_pulpopay_customer_cards` (all cards: UUID card ids and masked numbers), `pulpo_get_pulpopay_driver_cards` (one driver's), `pulpo_get_pulpopay_physical_card`. Card ids come in two forms: the card UUID, and the numeric payment method id. Tools say which they take; do not swap them.
- **Movements:** `pulpo_list_pulpopay_movements` (filters, search, paging; amount, date, merchant, type, status, card, driver, vehicle), `pulpo_get_pulpopay_card_movements` (card UUID), `pulpo_get_pulpopay_wallet_card_movements`, `pulpo_get_pulpopay_wallet_movements` (validated plus pending). Reference codes: `pulpo_get_pulpopay_movement_types`, `pulpo_get_pulpopay_merchant_categories`, `pulpo_get_pulpopay_fuels_costs`.
- **Fuel load checks:** `pulpo_list_pulpopay_fuel_load_checks`, `pulpo_get_pulpopay_fuel_load_check` (by UUID), `pulpo_get_pulpopay_fuel_loads_score` (0 to 100 compliance score with total, passed and failed).
- **Controls:** `pulpo_get_pulpopay_controls_settings` (spending restrictions and merchant category limits).
- **Funding requests:** `pulpo_get_fund_card_requests_count` (counts by status), `pulpo_list_fund_card_requests`, `pulpo_list_fund_card_request_details`. List oldest pending first when the user wants to work the queue. Status codes are numeric: read the labels from `pulpo_list_catalog_items` with `className: "fund-card-requests-statuses"`; never guess which code means approved.
- **Scheduled funding:** `pulpo_list_scheduled_fund_cards`, `pulpo_get_scheduled_fund_card`, `pulpo_validate_scheduled_fund_card`. Catalogs `scheduled-fund-cards-frequencies`, `-operation-types`, `-statuses` via `pulpo_list_catalog_items`.
- **Payment methods** (the fleet's cards in general, not only PulpoPay): `pulpo_list_payment_methods`, `pulpo_get_payment_method_details`, `pulpo_get_payment_methods_catalog`. Archived ones are hidden unless `q` has `archived:{is:true}`.
- Documents and invoices: `pulpo_get_pulpopay_document`, `pulpo_get_pulpopay_recovered_invoices`. Do not print Base64 content.

When you summarize money, give currency, the date range, and whether pending movements are included. Never add a balance and a pending amount without saying you did.

## Before any write

- **Ask first.** This connector runs a write as soon as you call it; the confirmation is yours (the host may ask too, and it can be set to auto-approve). Show what will change: the record as the user knows it (plate, name or Pulpo ID, never an internal id), and each field as current value to new value. Wait for a plain yes to that exact action. A yes to something else does not count; if the details change, ask again.
- **Never invent IDs or values.** Take ids from tool results in this conversation. Turn names into catalog ids with `pulpo_resolve_catalog_id`. If a name does not match exactly, or several records fit, list the candidates by name and let the user choose; never pick the closest one or a default.
- **Replace vs patch.** A tool that replaces a whole record drops whatever you leave out: read the record first, merge your change into it, send everything. A tool that patches takes only the fields that change.
- **Irreversible means say so.** Deletes, archives, bulk changes and money movements cannot be undone from Pulpo or from here. Say it in the question, ask once per action, and prefer the reversible alternative when one exists (inactive status instead of delete, lock instead of withdraw).
- **After the call**, report what the tool returned. If it failed, say in plain words what failed and do not retry with different values unless the user agrees.
- **Not found is not "does not exist".** What you can see depends on the account selected, the user's role and their segments. An empty result or a 404 means "no match among what you can access in this account".

## Money and card writes: stricter than the general rules

These move money or change card access: `pulpo_pulpopay_fund_account`, `pulpo_pulpopay_transfer_funds`, `pulpo_pulpopay_fund_cards`, `pulpo_pulpopay_withdrawal_cards`, `pulpo_confirm_fund_card_request`, `pulpo_update_fund_card_request`, `pulpo_create_scheduled_fund_card`, `pulpo_disable_scheduled_fund_card`, `pulpo_pulpopay_lock_unlock_card`, `pulpo_pulpopay_change_card_nip`, `pulpo_pulpopay_reassign_card`, `pulpo_update_pulpopay_controls_settings`.

1. **The user states the amount and the cards.** Never choose an amount, a card, or a number of cards on your own, never round, and never fill a gap with a default. Read the amount back exactly, with currency.
2. **Check before you move.** `pulpo_pulpopay_card_funding_healthcheck` (payment method id and amount) validates balance and card status before funding. Read `pulpo_get_pulpopay_account_balances` and, for a transfer, the origin card's balance. If the check fails, report why and stop.
3. **Confirm with the whole picture:** from where, to where (driver name plus last four digits, never full ids), amount, currency, and resulting balances when you know them. One yes covers exactly that. For bulk funding or withdrawal, list every card and amount and the total.
4. **Funding requests:** read the request with `pulpo_list_fund_card_request_details` first. Approve or reject a single one with `pulpo_confirm_fund_card_request` (amount, numeric status, optional comment); several with `pulpo_update_fund_card_request`. An approval can fund a card, so confirm the amount. A rejection should carry a reason the driver will see. Do not approve a set bigger than what the user named.
5. **Locking and unlocking:** read the card's current state with `pulpo_get_pulpopay_customer_cards` first; saying "locked" or "unlocked" when it already is would be noise.
6. **Controls:** `pulpo_update_pulpopay_controls_settings` replaces the whole configuration. Read `pulpo_get_pulpopay_controls_settings`, apply the change to that, send everything.
7. **Card issuing and PIN:** `pulpo_pulpopay_create_card`, `pulpo_pulpopay_activate_cards` (by payment method ids) and `pulpo_pulpopay_change_card_nip` change who can spend. Verify the target card and driver first. Never echo a PIN back into the conversation after it is set, and do not store it.
8. **Fuel load check notes:** `pulpo_update_pulpopay_fuel_load_check` updates extra data; read the check first.
9. After any of these, read the new balance or state back and report it, instead of assuming it worked.

To reconcile card spending with fuel loads, `pulpo_get_fuels_by_payment_method` returns the fuel records paid with a given card (see `fuel-expenses`).