Skip to content

FousU.S. Bank Access Online

Pull your Access Online transactions into your own systems

Build a method that reads card transactions from U.S. Bank Access Online with their Approval Status, accounting codes and attachments. A workflow can check each card account every weekday for Pending transactions and missing receipts before the cycle closes.

Works with your own U.S. Bank Access Online account. Fous is an independent product.

What you can build on Access Online

  • Get card transactions

    Build this

    Reads the transaction list for one card account: approval status, dates, merchant, amount, attachment and accounting code.

    Takes
    Card account (last 4 digits), date range, approval status (optional)
    Returns
    Approval status, transaction date, posting date, merchant, amount, has attachment, accounting code, description
  • Check balance and available credit

    Build this

    Reads the dashboard for one card account: current balance, credit limit, available credit and the last 10 posted transactions.

    Takes
    Card account (last 4 digits)
    Returns
    Account name, last 4 digits, current balance, credit limit, available credit, last 10 posted transactions
  • Get a transaction's approval history

    Build this

    Opens one transaction and reads its Summary, Transaction Line Item and Approval History tabs.

    Takes
    Card account (last 4 digits), transaction date, merchant, amount
    Returns
    Merchant, amount, line items, approval history entries, current approval status
  • Reallocate and approve a transaction

    Build this

    Selects a transaction, sets its accounting code and description on the Allocations tab, saves the allocation and approves it.

    Takes
    Card account (last 4 digits), transaction date, merchant, amount, accounting code, description
    Returns
    Merchant, amount, accounting code, description, approval status

Automate Access Online with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • Pending transactions before the cycle closes

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    For each card account you name, get the card transactions in the current billing cycle.
    Step 2
    Keep the transactions whose Approval Status is still Pending.
    Step 3
    Email you the list, one section per card account.
  • Transactions without a receipt, every Monday

    Build this
    Starts
    Every Monday at 9:00
    Step 1
    For each card account, get the card transactions posted in the last 7 days.
    Step 2
    Keep the transactions with no attachment.
    Step 3
    Post each one, with card account, merchant, amount and posting date, to your Slack webhook.
  • Approved transactions, posted to your ERP

    Build this
    Starts
    Every day at 18:00
    Step 1
    For each card account, get the card transactions with Approval Status Approved.
    Step 2
    Keep the transactions that were not on the last run's list.
    Step 3
    Post each one, with its accounting code and description, to your ERP webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get card transactions” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "access.usbank.com/get_card_transactions",
    "input": {
      "card_last4": "4821",
      "from": "2026-10-21",
      "to": "2026-11-12",
      "approval_status": "Pending"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "account_name": "Acme Facilities PCard",
    "card_last4": "4821",
    "transactions": [
      {
        "approval_status": "Pending",
        "trans_date": "2026-11-06",
        "posting_date": "2026-11-09",
        "merchant": "Globex Office Supply",
        "amount": 248.6,
        "has_attachment": false,
        "accounting_code": "100-4410-2210",
        "description": null
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

Access Online’s own options

U.S. Bank publishes APIs for its card programs on its Developer Portal: one retrieves Access Online transactions, orders and attachments, another creates and maintains card accounts and spending controls. Your organization must be verified there and request production access for each API. Without that, you work in Access Online itself.

OptionWhat it coversWhat it takes
Access Online Transactions APIRetrieves transaction details, order details and transaction attachments, as zip files, for reporting and auditing.A verified organization on the U.S. Bank Developer Portal and production access requested for the API. Attachments up to 10MB.
Corporate Credit Cards APICreates, maintains and closes card accounts, sets spending controls and limits, maintains cardholder details, retrieves transactions.A Corporate Travel, One Card or Purchasing Card program on Visa or Mastercard, in USD or CAD.
Corporate Statements APISearches up to two years of corporate account statements, with balances and payments, and downloads them as PDF.A verified organization on the U.S. Bank Developer Portal and production access requested for the API.
Access Online by handTransactions, reallocation, approval, attachments and statements, one card account or program at a time on screen.An Access Online user ID under your organization's short name.

Read on November 12, 2026: Access Online Transactions API, Corporate Credit Cards API, Getting started with U.S. Bank APIs.

Signing in to Access Online

Access Online asks for your organization short name, user ID and password, and you set up authentication questions when you register. Department of Defense card users sign in through PIEE single sign-on instead. With Fous you sign in through Access Online's own sign-in with your own account, and the login is sealed with AES-256, never returned by the API or written to logs.

Worth knowing

Saved is not approved
A reallocation stays Pending after Save Allocations until you click Approve. Changes made on the Allocations tab are lost if you leave without saving them.
Approval locks the transaction
An approved transaction moves to the approver's queue and is locked. To change it, you click Pull Back, make the change and approve it again.
Attachments: 5MB per transaction
You can attach PNG, JPG or PDF files to a transaction, and they are converted to PDF. All files on one transaction together may not exceed 5MB.
Statements follow your billing cycle
Statements are under Account Information, Cardholder Account Statement. In one state's program guide, the cycle closes on the 20th and the statement is ready the next business day.

More in Finance: payments, cards and lending

Other industries: 登記情報提供サービス, MCA21, IATA BSPlink, Mis Comprobantes, CAC Company Registration Portal, Telemaco.

Frequently asked questions

Yes, through the U.S. Bank Developer Portal. The Access Online Transactions API retrieves transactions, orders and attachments, and the Corporate Credit Cards API maintains card accounts and spending controls. Your organization has to be verified on the portal and request production access for each API.

Because saving the allocation does not send it on. The Approval Status stays Pending until you click Approve, which moves the transaction to your approver's queue.

Yes, by pulling it back. Click Pull Back on the transaction, make your changes, then approve it again to send it back to your approver's queue.

Under Account Information, then Cardholder Account Statement. Each program has its own billing cycle: in one state's program guide, the statement is ready the business day after the cycle closes on the 20th.

No. Fous is an independent product. You use it with your own Access Online account, and a method reads and does only what that account can.

Put U.S. Bank Access Online behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextCareCredit Provider CenterSynchrony Business Centere-OSCAR登記情報提供サービスHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of U.S. Bank Access Online (U.S. Bank). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.