UAE · ENBook a demo
BankingEngineeringAssistant

Back-End Agent

Builds services, APIs and business logic.

Back-End AgentApplication Engineering
Industry
Banking
Department
Engineering
Team
Application Engineering
Kind
Assistant
Approver
Head of Technology Operations
Code
ENG-02

It implements service endpoints and business logic around the core banking system (balance and transaction APIs, payment initiation, limit checks, fee calculation, interest accrual rules) from a ticket, keeping the API contract backward compatible and money arithmetic exact. It writes reversible migrations, adds tests and opens a pull request.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the code repository: the service code, API specification and core banking interface definitions..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  5. 05Asks a person

    Hands the work to Head of Technology Operations with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the code repository: it opens a pull request with the change. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The back-end standards: the API contract and versioning, decimal money handling and rounding rules, idempotency for payment endpoints, the end-of-day and batch windows of core banking, audit logging requirements, and secure coding rules.

Reads from

the code repository: the service code, API specification and core banking interface definitions.

Acts in

the code repository: it opens a pull request with the change.

Hands back

An object with pull_request (title, branch and description), endpoints, migrations (a list with up and down), tests_added, money_logic_checks and risks.

Asks a person when

The change alters interest, fee or balance calculations, payment initiation, authentication, the API contract, or end-of-day batch processing.

ApproverHead of Technology Operations

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Breaking changesnew_version_requiredHow breaking changes are handled.
p95 latency budget (ms)250Endpoints stay within this.
Least coverage (%)85For changed code.
Money roundingbanker's rounding to centsRounding rule for amounts.
Auth changes need SecurityOnWhen on, authentication changes need a security review.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Breaking changes follow new_version_required.
  • Amounts use decimal types with banker's rounding to cents, never floating point.
  • Payment endpoints are idempotent on a client key, and every money movement writes an audit record.
  • Keep p95 latency under 250 ms and coverage of changed code at 85 percent.
  • When on is true, authentication or authorisation changes need a security review.
  • Changes that run in the core banking end-of-day batch window are tested against a full day's volume.

See the Back-End Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Back-End Agent · Banking | Basinwright Industries