FousDBS IDEAL
Get your DBS IDEAL accounts and payments through an API
Read an account's balance and transactions, your Payment History and the payments waiting in Approvals in DBS IDEAL with one API call each. A workflow can check every account each weekday morning and email you the new transactions.
Works with your own DBS IDEAL account. Fous is an independent product.
What you can build on IDEAL
Get account balance and transactions
Build thisOpens one account from Accounts and reads its balance and the transactions for the date range you give.
- Takes
- Account number, from date, to date
- Returns
- Account number, currency, balance, and each transaction's date, description, reference and amount
Get payment history
Build thisReads Payment History under Pay & Transfer, filtered by date range, debiting account, payment type or status, for payments made in IDEAL in the last 6 months.
- Takes
- From date, to date, account (optional), payment type (optional), status (optional)
- Returns
- Payment date, debiting account, payee, payment type, amount, currency, reference, status
List payments waiting for approval
Build thisReads the Payment/Transaction section of Approvals: the transactions your account can approve or reject.
- Takes
- Nothing
- Returns
- Transaction type, debiting account, payee, amount, currency, payment date, reference
Submit a payment to a saved payee
Build thisFills in Pay Local/ Overseas Payee for an existing payee and selects Submit, which sends the payment to your approvers.
- Takes
- Debiting account, payee, payment date, amount, currency, reference on bank statements
- Returns
- Payee, amount, currency, payment date, reference, status
Automate IDEAL 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.
New transactions on every account, each morning
Build this- Starts
- Every weekday at 8:00 Singapore time
- Step 1
- For each account you name, get the balance and the transactions since the previous business day.
- Step 2
- Keep the transactions that were not there on the last run.
- Step 3
- Email you the balances and new transactions, one section per account.
Payments waiting in Approvals, posted to Slack
Build this- Starts
- Every weekday at 9:00 and 14:00 Singapore time
- Step 1
- List the transactions in the Payment/Transaction section of Approvals.
- Step 2
- Stop when there are none, and keep the ones not there on the last run.
- Step 3
- Post each one, with payee, amount, currency and payment date, to your Slack webhook.
Payment status changes, posted to your ERP
Build this- Starts
- Every weekday at 17:30 Singapore time
- Step 1
- Get the Payment History for the last 7 days.
- Step 2
- Keep the payments whose status changed since the last run.
- Step 3
- Post payment date, payee, amount, currency, reference and status 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 account balance and transactions” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "ideal.dbs.com/get_account_transactions",
"input": {
"account_number": "072-123456-7",
"from_date": "2026-11-10",
"to_date": "2026-11-11"
}
}'
{
"status": "completed",
"data": {
"account_number": "072-123456-7",
"currency": "SGD",
"balance": 184250.72,
"transactions": [
{
"date": "2026-11-11",
"description": "FAST payment from Northwind Logistics",
"reference": "INV-20931",
"amount": 12480
},
{
"date": "2026-11-10",
"description": "GIRO payment to Globex Supplies",
"reference": "PO-5521",
"amount": -3615.5
}
]
}
}
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.
IDEAL’s own options
DBS offers two connections to your own systems, both set up with DBS rather than switched on in IDEAL: RAPID, its real-time REST API, and IDEAL Connect, a host-to-host file link. DBS says each takes 4 to 6 weeks to set up and lists no fees for either on its pages. IDEAL itself has its setup and monthly fees waived.
| Option | What it covers | What it takes |
|---|---|---|
| DBS RAPID | Balance and statement enquiry, transaction status, inward credit confirmation, remittance, ACH and real-time payments, FX booking and collections. | Through DBS's Get In Touch form or BusinessCare. REST with JSON and PGP. 4 to 6 weeks to go live. |
| IDEAL Connect | Host-to-host files: domestic and cross-border payments, and reports such as account statements and bill payments. | Through your Relationship Manager or BusinessCare. About 4 to 6 weeks including testing, with integration software of your choice. |
| IDEAL by hand | Accounts with Export to Excel (.xls) or PDF, eStatements, Payment History, Approvals and the File Exchange Center. | An IDEAL account with setup and monthly fees waived, and the IDEAL mobile app as digital token. |
Read on November 12, 2026: DBS RAPID, IDEAL Connect, DBS IDEAL online banking.
Signing in to IDEAL
IDEAL signs you in with your Organisation ID, User ID and PIN, with your email, or with a QR code, and you approve the login with a tap and swipe in the IDEAL mobile app, your digital token. With Fous you sign in once through IDEAL's own sign-in with your own account: the login is sealed with AES-256, phone approval is handled, and an expired session is signed back in.
Worth knowing
- Payment History covers 6 months
- Payment History shows payments made in IDEAL in the last 6 months. Payments made at a branch or through RAPID do not appear there: you find them in the account statement.
- Your approval policy decides who approves
- The number of approvers or approval groups a payment needs can differ by payment type, as your company's policy sets it. A submitted payment is completed only when all of them have approved it.
- One device, and a 12-hour cooling period
- The digital token works on one device at a time. For 12 hours after it is set up on a device, you cannot add or edit a payee or change contact information.
- Parent and subsidiary companies
- If you have access to several companies in a parent and subsidiary relationship, Payment History can show all of them: under Additional filters, select Organisation, then Show All.
More in Finance: corporate banking and credit
- Banno Business
- Q2 business online banking
- Absa Access
- ANZ Transactive - Global
- Axis Corporate Internet Banking
- BancaNet Empresarial
- Banorte en su Empresa
- BB Digital PJ
- BBVA Net Cash México
- Bradesco Net Empresa
- businessONLINE
- CIBC Cash Management Online
- CommBiz
- FABeAccess
- ICICI Corporate Internet Banking
- Itaú Empresas
- KlikBCA Bisnis
- Kopra by Mandiri
- Maybank2E
- NAB Connect
- OCBC Velocity
- RBC Express
- ScotiaConnect
- Standard Bank Business Online
- Sucursal Virtual Empresas
- Telecrédito
- UOB Infinity
- Westpac Corporate Online
- YONO Business
- Interbanking
- PINACLE
- SinglePoint
- Wells Fargo Vantage
Other industries: Paymode-X, 全国统一规范电子税务局, Income Tax e-Filing Portal, GetYourGuide Supplier Portal, Oficina Virtual CCSS (SICERE), EmaraTax.
Frequently asked questions
Not inside IDEAL itself, but DBS offers RAPID, a real-time REST API for balances, statements, payments and collections, and IDEAL Connect, a host-to-host file link. Both are set up with DBS on request and take 4 to 6 weeks, and DBS lists no fees for them on its pages.
Payment History shows payments made in IDEAL in the last 6 months. eStatements go back up to 7 years for business, multi-currency, foreign currency current, Autosave and digital accounts, and download as PDF.
Yes. In Accounts, select an account, set the date range and select Export to download Excel (.xls) or PDF. With Fous, a method returns the same transactions as JSON and a workflow can run it for each account on a schedule.
No. Selecting Submit sends the payment to the approvers your company's approval policy names, and all of them must approve it before it is completed. If you are an approver yourself, you can Approve and Submit in one step.
No. Fous is an independent product. You use it with your own DBS IDEAL account, and a method reads and does only what that account can.
Put DBS IDEAL 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 nextFABeAccessICICI Corporate Internet BankingItaú EmpresasPaymode-XHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of DBS IDEAL (DBS 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.