Browser automation for financial portals.

Automate only permitted financial portal work. Document authority for each portal and account. Portal terms and contracts still apply. Internal approval should precede implementation.

Write the permitted scope plainly. Name portals, accounts, and actions. Name prohibited actions equally clearly. Ambiguity creates dangerous operational drift.

Start with lower-mutation retrieval work. Balance reviews and statements still expose confidential data. Payment preparation needs tighter controls. Final submission deserves separate approval.

Authority can change over time. Staff roles change and contracts expire. Portal permissions can also change. Revalidate scope after every material change.

Browser automation performs defined interactions. Authentication establishes an account session. Authorization permits portal actions. Approval confirms a financial commitment.

Browser isolation changes an execution boundary. It does not replace the other controls. Playwright browser contexts isolate test state. They are not remote browsers.

NIST treats authentication and authorization separately. OWASP also separates login and transaction authorization. Scripts should preserve both distinctions. Human approval should remain visible.

Evidence forms the fifth operating control. Every consequential run needs accountable records. Logs should identify scope and outcomes. Sensitive data should remain minimized.

Each portal carries unique behavior. Authentication flows and roles differ. File formats and session lifetimes differ. Maintenance windows can also differ.

Build one inventory before writing scripts. Record the accountable business role. Record data classes and actions. Record portal support contacts.

Separate retrieval from mutation. Reading balances carries lower mutation risk. It still exposes confidential information. Reads may change sessions and audit records. Uploading documents changes portal state and data exposure.

Portal inventories reduce hidden scope. They also expose duplicate access. Operators can remove stale accounts. Security teams can prioritize reviews.

Playwright creates clean browser contexts for tests. Each context gets separate cookies and storage. Contexts improve reproducibility and failure isolation. They remain inside the running browser.

Context isolation differs from remote isolation. Chrome Site Isolation separates renderer processes. Remote browser isolation moves selected execution elsewhere. These boundaries serve different jobs.

Use separate contexts for separate roles. Do not mix administrator and operator state. Do not reuse customer-specific state broadly. Close contexts after defined work.

Context separation still needs identity controls. A context cannot grant portal permission. It cannot approve a transaction. It cannot establish compliance.

Playwright can save authenticated browser state. That state may contain cookies and headers. Playwright warns those files enable account impersonation. Source repositories are inappropriate storage.

Playwright recommends a dedicated auth directory. Its example adds that directory to gitignore. That step prevents accidental commits. It does not secure the file itself.

Operational automation needs stronger state handling. Restrict file access and retention. Use dedicated accounts where supported. Revoke state after suspected exposure.

Shared state creates accountability problems. Parallel state changes create more risk. Playwright recommends separate accounts for state-changing tests. Production policy needs independent review.

This matrix separates preparation from commitment. It assigns a sample control posture. Organizations should adapt every row. Portal capabilities and risk decide final policy.

The matrix reduces decision ambiguity. Scripts receive a defined stopping point. Humans receive a clear approval point. Evidence connects both stages.

Playwright locators find current page elements. The documentation favors user-facing attributes. Roles and labels often reflect user intent. Explicit contracts provide another option.

Avoid brittle position-based selectors. Portal layouts can change without warning. Visible labels can also change. Maintain a small selector inventory.

Playwright performs actionability checks before actions. Elements need suitable visible and stable states. Click targets must receive events. Inputs must remain editable.

Forced actions disable some checks. Avoid them for consequential workflows. A failed check should stop execution. Operators should review the changed portal.

OWASP distinguishes authentication from transaction authorization. Users should understand which action occurs. Significant transaction details need confirmation. Amount and destination often matter.

Transaction authorization should remain server-side. Each transaction needs valid approval. State transitions should follow enforced order. Browser scripts should not weaken those controls.

Automation can prepare transaction drafts. It can collect supporting evidence. An authorized person should review final details. The portal should enforce the commitment.

Approval should become invalid after detail changes. Scripts should detect those changes. The operator should restart review. Evidence should preserve the final version.

This checklist turns authority into repeatable evidence. Each step creates one reviewable artifact. Teams can stop before unsafe ambiguity. The script remains the smallest component.

Run the checklist before production use. Repeat it after portal changes. Repeat it after role changes. Repeat it after authentication changes.

Covered financial institutions need risk-based safeguards. FTC guidance addresses access controls and inventories. It also addresses application assessment. Authorized user activity needs logging.

Automation logs should identify accountable runs. Record the portal and account role. Record each state-changing action. Link approvals with final outcomes.

Do not capture everything by default. Screenshots can contain customer information. Traces can contain sensitive portal content. Retention needs explicit purpose and access.

Compliance depends on the broader program. A script cannot establish it. Legal scope needs qualified assessment. Organizational controls still determine outcomes.

Financial portals change without your schedule. Labels move and roles evolve. Authentication flows can also change. Automation should fail closed.

A timeout is operational evidence. An unexpected locator is another signal. Never retry an uncertain financial commitment. Inspect portal history first.

Maintain one change record per portal. Note selector and workflow changes. Note permission and authentication changes. Re-run approval tests afterward.

Recovery needs practiced actions. Revoke browser state when exposed. Disable automation accounts when necessary. Preserve useful evidence for review.

Legba's agent skill exposes routing to agents. It also exposes isolated browser sessions. Those capabilities remain narrowly scoped. They do not create portal authority.

The agent skill does not approve transactions. It does not establish compliance. Playwright compatibility is not claimed. Portal compatibility still needs direct testing.

The portal still controls authentication. Organizational policy still controls authorization. Documented financial controls govern transaction approval. Those boundaries remain external.

Use the skill inside documented authority. Keep stored state restricted. Preserve required user-presence steps. Stop before every financial commitment.