Website

AFTECH's Nine Cybersecurity Areas: A Test List for Any System Connected to Payments

November 13, 2026 · 5 min read · Etzal Group Team

At the opening of National Fintech Month 2026 on Wednesday 11 November 2026, Firlie Ganinduto, Secretary General of the Indonesian Fintech Association (AFTECH), asked members to make cybersecurity "highly prioritised" at board level. Katadata, reporting on 12 November, noted that AFTECH has published cybersecurity guidelines drawn up with the National Cyber and Crypto Agency (BSSN) and CISSReC, covering nine areas.

The guidelines are addressed to AFTECH members. They are not a legal obligation for every company. But if your system takes payments through a payment gateway, through QRIS (Indonesia's national QR payment standard) or through a bank API, you are in the same chain, and the nine areas work well as a frame for testing yourself.

What Katadata reported

  • Firlie Ganinduto said cyberattacks "are already happening everywhere".
  • The nine areas: security testing, advanced cyber risk management, cybersecurity audit, training and security programmes, AI governance and security, a fraud management framework, a cloud security framework, mobile and API security, and a data governance and privacy framework.
  • AFTECH works with ADIGSI and with the Cyber Incident Response Team (TTIS) formed together with BSSN.
  • Bank Indonesia data cited in the report: QRIS reaches 69.3 million users and is used by more than 47 million merchants, 96.7% of them micro, small and medium enterprises.
  • FortiGuard Labs data as of Wednesday 11 November 2026, 19:00 Jakarta time: at least 1.3 million cyberattack attempts on Indonesia in 24 hours, most of them on finance, banking and insurance with 531,000 attempts.

Two points need careful reading. The FortiGuard figure counts attempts, not breaches. And the source gives only the names of the nine areas, not the content of the guidelines. The test questions below are therefore our own, not items from AFTECH's document.

Why companies outside fintech should care

With more than 47 million QRIS merchants, most connection points to the payment system sit outside fintech companies: online shops, booking apps, ERPs that send payment instructions, customer portals that accept cards. Your payment provider may be very well run. That does not protect an API key stored in your code repository, or a webhook on your server that accepts payment notifications without checking their signature.

That is the value of the fintech cybersecurity guidelines Indonesia's industry body has issued, even for a non-fintech company: they give you a list of headings the industry has already agreed on, so you do not have to design a framework from scratch.

The nine areas as a test list

The questions below are our practical suggestions for each area.

AreaTest question for your system
Security testingWhen was the payment flow last penetration-tested by someone who did not build it, and are the findings closed
Advanced cyber risk managementIs there a written risk register with owners and deadlines, reviewed by the board
Cybersecurity auditWho checks that written controls are actually followed, and how often
Training and security programmesHave finance and customer service staff practised spotting fake requests
AI governance and securityWhat customer data is sent to AI services, and who approved it
Fraud managementIs there a rule that holds unusual transactions, and who reviews them
Cloud securityWho holds admin access, is multi-factor authentication on, is storage closed to the public
Mobile and API securityWhere are API keys stored, when were they last rotated, do webhooks verify signatures
Data governance and privacyWhat payment and personal data is kept, for how long, and on what basis

What to do yourself and what to ask of vendors

Not every area can or should be handled in-house. A sensible split for a mid-sized company:

Yours, whoever the vendor is

  • Storage and rotation of API keys and credentials.
  • Staff access rights to payment dashboards and cloud consoles.
  • Internal rules on who may issue refunds, change the settlement account or add users.
  • Staff training.

Ask the vendor, in writing

  • The latest security test or independent audit result, at least in summary.
  • How and how quickly the vendor will tell you about an incident on their side.
  • The list of subcontractors that touch your data.
  • Documentation for webhook signature checks and IP address restrictions.

Done together

  • Fraud rules. The vendor has the engine, you know which transactions are normal for your business.
  • Daily reconciliation between the vendor's records and your books. A difference seen the same day is far cheaper than one found at closing.

A realistic order of work

Tackling nine areas at once is not possible, and trying usually ends with nine documents and no change. The order we suggest:

  1. This week: API keys, admin access and multi-factor authentication. All three are cheap and close the routes used most often.
  2. This month: webhook signature checks, daily reconciliation and the letter to vendors.
  3. Next quarter: an external penetration test of the payment flow, then a risk register taken to the board.
  4. Ongoing: short training sessions and a review of AI use.

The trade-off sits in fraud management. Strict rules stop more fraud, but they also stop real customers and add review workload. Start loose with close monitoring, then tighten on the basis of your own transaction data, not the other way round.

The message about boards is also worth taking literally: a one-page status of the nine areas, with colours and owner names, discussed at the board meeting each quarter. Without it, security remains an IT matter that loses out to new features.

If you want to review the payment integration in your application or ERP against this frame, Etzal Group's enterprise software team can help, or contact us.

For the actual content of the guidelines, refer to AFTECH's official document and check its latest announcements, because this article rests only on the area names as reported.

Sources

Frequently asked questions

Are the AFTECH guidelines mandatory for every company?

No. They are addressed to AFTECH members and are not a general legal obligation. Other companies can use them as a voluntary test framework.

What are the nine areas?

Security testing, advanced cyber risk management, cybersecurity audit, training and security programmes, AI governance and security, fraud management, cloud security, mobile and API security, and data governance and privacy.

Does FortiGuard's 1.3 million figure mean 1.3 million breaches?

No. It counts attack attempts over 24 hours, not successful breaches.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Website Development

Fast, SEO-ready websites that turn visitors into customers.