52 docs tagged with "banking"

Overview of AML, CTF and KYC controls in banking.

Overview of Bank Account Types.

A comprehensive A–Z reference of terms used in banking and payments. Essential reading for anyone joining the industry.

Overview of Banking Domain Knowledge Base.

A bank is made up of many specialised teams. Understanding who does what helps you collaborate effectively, know who to escalate to, and understand where you fit in the payments ecosystem.

Complete guide to Australia's BECS Direct Entry (DE) system — file formats, transaction codes, timing windows, return codes, settlement, and engineering patterns.

Overview of BPAY — Bill Payment System.

Overview of ISO 20022 camt.053 statements.

Overview of ISO 20022 camt.054 notifications.

These two messages form the **formal payment cancellation (recall) workflow**, allowing a payment to be recalled after it has been sent — even after settlement.

**Payment cards** (debit and credit) are one of the most widely used payment methods globally. They operate on **card schemes** — networks that define rules.

How clearing works in Australian and global payment systems — DNS vs RTGS, batch netting, BECS clearing cycles, AusPayNet rules, and intraday liquidity implications.

How Confirmation of Payee works — PayID name matching, account name verification, fuzzy matching, Authorised Push Payment fraud prevention, and engineering implementation.

The **Core Banking System (CBS)** is the central software platform that manages a bank's **primary banking operations** — account management, transaction.

How correspondent banking works — Nostro/Vostro/Loro accounts, routing chains, SWIFT messaging, de-risking, and the role of correspondents in cross-border payments.

Detailed explanation of core banking credit posting, funds availability, double-entry accounting, settlement risk, holds, and exception handling.

Deep-dive into core banking debit posting — ledger mechanics, memo vs. hard post, balance contention, idempotency, locking strategies, saga compensation, and production Java/Spring implementation patterns.

Detailed explanation of debit reversals, compensating transactions, and rollback strategies in banking ledgers.

Complete guide to the debtor (paying party) in ISO 20022 payment messages — Debtor vs Originator vs Ultimate Debtor, SWIFT vs ISO fields, debtor agent, and identification.

Complete guide to direct debit in Australia — BECS DDR vs PayTo, mandate management, dishonour/return codes, timing, and engineering patterns.

Guide to FIS (Fidelity Information Services) banking platforms used in Australian banks — Profile, Systematics, WorldPay, integration patterns (API vs MQ), batch file handling, and engineering notes.

Overview of Foreign Exchange (FX) in Payments.

Overview of Fraud Detection & Prevention.

Critical engineering guide to idempotency in payment systems — duplicate detection strategies, EndToEndId, at-least-once delivery, saga compensation, and Java implementation patterns.

Complete guide to inbound payment processing — STP vs exception routing, credit hold rules, beneficiary validation, camt.054 notification, and engineering patterns.

Interest and fees are the primary ways banks **generate revenue** from accounts and products. Understanding how they work is important for product.

Overview of ISO 20022 Migration.

Intraday liquidity management for payment banks — ESA balance monitoring, RBA repo, payment queuing, liquidity stress, Basel III LCR/NSFR, and engineering patterns.

Overview of NPP — New Payments Platform.

Overview of off-us transaction handling in banking payment flows.

Overview of on-us transaction handling in banking.

Overview of Open Banking & Consumer Data Right (CDR).

Complete guide to outbound payment processing — initiation, validation, dual approval, payment factory, channel selection, and engineering patterns.

Overview of ISO 20022 pacs.002 payment status reports.

`pacs.004` is the **interbank payment return message**. It is sent by the **Creditor Bank back to the Debtor Bank** when a previously received `pacs.008`.

Overview of pacs.008 — FI-to-FI Customer Credit Transfer.

Overview of pain.001 — Customer Credit Transfer Initiation.

**No — `pain.004` is not a defined ISO 20022 message.**

Payment reversals allow **the sending side** (debtor bank or originating customer) to request that a previously submitted payment be reversed — cancelling the.

Master lookup table for ISO 20022 reason codes, BECS dishonour codes, NPP rejection codes, and SWIFT error codes used in Australian and international payment processing.

Overview of Payment Exceptions & Investigations.

Payment Hub vs Payment Gateway vs Payment Factory — architecture patterns, orchestration, channel abstraction, and Java/Spring engineering design for centralised payment processing.

If you're new to banking, the payment ecosystem can feel overwhelming. This page takes you from **zero to "I understand how a payment works"** using plain.

Detailed explanation of payment returns, pacs.004 ISO messaging, accounting, and difference from reversals.

Complete guide to PayTo — Australia's modern pull payment system built on NPP. Covers mandate lifecycle, payment initiation, PayID, agreement types, and engineering integration patterns.

Overview of Reconciliation.

Guide to regulatory reporting obligations for Australian banks — AUSTRAC TTR/IFTI/SMR, APRA reporting, RBA reporting, ASIC obligations, and engineering automation patterns.

Complete guide to Real-Time Gross Settlement (RTGS) in Australia — RITS, HVCS, ESA management, liquidity, gridlock resolution, and high-value payment engineering.

Overview of sanctions controls in payment processing.

How payment settlement works in Australia and globally — ESA accounts, RBA FSS, RTGS finality, DNS settlement risk, failed settlement handling, and Nostro/Vostro reconciliation.

Comprehensive guide to SWIFT messaging, MT vs MX formats, SWIFT gpi, UETR tracking, correspondent banking chains, and charges in cross-border payments.

Testing in banking is **high-stakes** — a defect in a payment system can result in customer funds lost, duplicate payments, regulatory breaches, or system.