Daga Rarrabuwa Zuwa Layin Karyewa: Ma'aunin API da Ya Ɓace na Bankin Kamfanoni a Zamanin Agentic
Bankin dillanci ya sami ma'aunin API nasa shekaru goma da suka wuce. Bankin kamfanoni bai taɓa samu ba — kuma a shekarar 2026 wannan tanki ya daina zama abin damuwa kaɗai ya zama layin karyewa. ISO 20022 ya ba masana'antar nahawu na kowa; bai taɓa ba ta saman kowa da ke shirye don agent ba. Yanzu mai kira ya sauya. Ba shi da wani mai haɓaka software da ke da lokaci na kwata don ɓatawa a kan haɗakarwa, sai dai wani model da ke gano kayan aiki a lokacin gudanarwa yana motsa kuɗi a cikin iyakokin manufa. Rikicin da masu kula da baitulmalin kamfanoni suka sha shi cikin shiru har shekaru ashirin ana shirin ba da shi ga software da ba za ta iya sha shi ba — yayin da ake tilasta wa layin bayanan da ke ƙasa zama tsararre ko banki na son hakan ko ba haka ba. Wannan shi ne abin da rashin jagora yake kashewa, dalilin da ya sa agentoci suke mai da rarrabuwar yau mai haɗari maimakon rashin inganci kawai, da abin da ma'aunin API na bankin kamfanoni dole ne ya wajabta kafin baitulmali mai cin gashin kai ya iya faɗaɗa.
Taƙaitaccen Bayani
- Bankin kamfanoni yana da nahawu, ba saman ba. ISO 20022 ya daidaita bayanai; babu wanda ya daidaita API. Wannan ya kasance abin jurewa yayin da mai haɗakarwa na ɗan adam ke sha rikicin — model a lokacin gudanarwa ba zai iya ba.
- Mai kira ya sauya. MCP ya mai da gano kayan aiki zama shawara ta lokacin gudanarwa. Wani agent da aka ƙera don kawar da matsalar haɗakarwa ta M×N ya sadu da ita kuma a kan iyakar banki, inda kowace cibiya wani server ne na musamman da ma'anonin kansa.
- Rarrabuwa yanzu tana motsa kuɗi ba daidai ba, cikin saurin injina. Timeout ɗaya, bankuna uku, gaskiya uku masu saɓani — kwafi a A, umarni da ya makale a B, gazawa cikin shiru a C. Idempotency da error grammar mai tabbaci suna zama masu ɗaukar nauyi.
- Nannaɗe kowane banki cikin MCP server yana ƙaura da fadamar. Servers arba'in, ma'anoni arba'in, babu bene na aiki na kowa — kuma wani model da ba shi da tabbaci mai damar rubutu zuwa layukan biyan kuɗi, matsala ce ta SR 11-7 / DORA / EU AI Act kai tsaye.
- Daidaita saman naka, ko ka zama kaya. Bankunan da suka buga API na asalin ISO 20022 da ke shirye don agent yanzu suna zama abokan ma'amala na tsohuwar zaɓi don baitulmali mai cin gashin kai; sauran suna hayar dangantakar abokan cinikinsu ga duk wanda ya mallaki adapter.
Duniyoyin banki biyu, ɗayansu an daidaita shi
Duba dillanci kuma hoton yana da rikici amma ana iya kewayawa. Turai tana da UK Open Banking da NextGenPSD2 na Berlin Group, wanda fiye da kashi uku cikin huɗu na bankunan Turai suka amince da shi kuma ana ɗaukarsa a aikace a matsayin ma'auni na zahiri. Amurka tana da Financial Data Exchange, wanda yanzu ya mamaye fiye da asusun masu amfani miliyan sittin. Ostiraliya tana da Consumer Data Right. Babu ɗayansu da yake na duniya, kuma babu ɗayansu da zai yiwu ya zama na duniya — amma kowanne yarjejeniya ce ta gaskiya, mai sigar, kuma injina zai iya gwadawa, kuma inda yarjejeniyoyi suka ƙare, aggregators (Plaid, Tink, TrueLayer, Salt Edge) suna sha bambancin a bayan ma'amala ɗaya. Rarrabuwar dillanci haraji ce. Ba bango ba ce.
Bankin kamfanoni da na babban ciniki ba shi da makamancinsa. Baitulmalin ƙasashe da yawa yana kai bankunansa ta hanyar bututun fayil na host-to-host, jerin portals na musamman, tsarin sarrafa baitulmali, ko aggregator — yawanci duk huɗu a lokaci ɗaya. Wannan ba magana ce ta banza ba: bincike na McKinsey na bankin ma'amala ya rubuta wannan gado ɗin shekaru da yawa, yana bayanin yadda bankuna suke dogaro da watsa fayil na host-to-host da SFTP, yana lissafa sanannun yanayin gazawar haɗakarwar dogaro da fayil — manyan tsarin ERP da dole ne a keɓance su ga kowane kamfani, rashin iya sarrafa jujjuyawa mai sharaɗi — kuma yana ba da rahoton cewa fiye da kashi 85% na shugabannin bankin ma'amala suna niyyar zuba jari a cikin API na sarrafa kuɗi. Sha'awar API ba ta cikin shakka. Abin da ya ɓace shi ne yarjejeniya ta kowa da suke nunawa.
Domin waɗanda ake tsammani ba su ne ba. Ana kuskuren ISO 20022 a kai a kai a matsayin ma'aunin da ya ɓace, amma nahawu ne na bayanai, ba yarjejeniya ce ta API ba: pain.001 yana gaya maka yadda za a fasalta canja wurin kuɗi, ba wane endpoint ke ƙirƙirar ɗaya ba, yadda yake tabbatarwa, yadda yake shafa-shafa, ko yadda yake gaya maka ya gaza. BIAN yana ba masana'antar model na tunani na semantic na kowa, ba ma'amala da aka tilasta ba. Payment Initiation da Instant Cash Reporting API na Swift matakai ne na gaske zuwa daidaitawa, amma sun mai da hankali kan hanyar sadarwa kuma har yanzu suna tasowa, ba saman kowa ba. Tsarin openFinance na Berlin Group yana kai wa ga yanayin amfani na kamfanoni — buɗe asusu, kuɗin ciniki, biyan kuɗi na maimaituwa mai motsi — amma na Turai ne, na farkon fari, kuma na kyauta ta yarjejeniya. Tara duka kuma har yanzu ba ka da ma'aunin API na bankin kamfanoni na duniya mai ɗaure. Kana da kayan gini kuma babu shimfida.
Dalilin da ya sa rarrabuwar ta wanzu — da dalilin da ya sa hakan ke ƙarewa
Har shekaru ashirin wannan ya kasance abin jurewa, domin mai haɗakarwa ɗan adam ne kuma mai haƙuri. Kamfani yana shigar da haɗin banki kaɗan cikin watanni, wani lokaci kwata. Kowanne aiki ne: an musanya takaddun shaida, an gudanar da gwajin kobo, an yi jayayya kan takaddar taswira. Farashin gaske ne amma ana biyan sa sau ɗaya ga kowace dangantaka kuma ana rarraba shi cikin shekaru na biyan kuɗi na gaba. Lokacin da API na banki ya rasa cikakkiyar bayani — lokacin da ma'auni "ya bar sauran ga cibiyar da ke aiwatarwa", kamar yadda bankuna kansu ke koke da cewa yana yi — injiniyan ɗan adam ya karanta portal, ya fahimci niyya, ya rufe gibin. Rikici ya kasance abin jurewa domin mutum yana nan don warware shi.
Ya kuma wanzu saboda dalilan da ba a fadi sosai a bayyane ba. Fitilar da ke ƙasa tana da wuyar sauyawa da gaske: taga na daidaita jerin gwano, zagayowar dare da manyan cibiyoyin mainframe da ba a taɓa ƙera su don amsa tambaya ta lokaci na gaske ba. Kuma rarrabuwa ba haɗari kaɗai ba ce — cikin shiru, wani nau'i ne na kulle-kulle. Kowane bututun host-to-host na musamman da mai kula da baitulmali ke ginawa farashin sauyawa ne da ke tara wa mai mallaka. Banki mai wuyar haɗakarwa, a gefe, banki ne mai wuyar barin. Babu ɗayan wannan da yake makirci; sha'awa ce ta talakawa. Amma yana bayyana dalilin da ya sa masana'anta da suka amince kan nahawu na bayanai ba su taɓa amincewa kan saman ba — kuma dalilin da ya sa saman shi ne layin ƙarshe da ba a daidaita ba. Dalilin da ya sa ba zai iya ci gaba da riƙe ba shi ne ana tilasta wa layin da ke ƙasansa zama tsararre a kan ranar ƙarshe, kuma layin da ke samansa ya samu sabon mai amfani mara haƙuri.
Mai kira ya sauya
Wannan mai amfani ya iso cikin watanni goma sha takwas. Model Context Protocol, wanda Anthropic ya buɗe tushen sa a watan Nuwamba 2024 kuma ya ba da gudummawar sa ga Agentic AI Foundation na Linux Foundation a watan Disamba 2025 tare da Block da OpenAI, ya zama hanyar tsohuwar zaɓi da tsarin AI ke kai wa kayan aiki da bayanai. A farkon 2026 yana buga kimanin zazzagewar SDK miliyan casa'in da bakwai a wata; a tsakiyar shekara, bisa karatun masana'antar guda ɗaya mai jagora, kimanin kashi saba'in da takwas na ƙungiyoyin AI na kamfanoni suna gudanar da agentoci masu goyon bayan MCP a samarwa kuma fiye da kashi ɗaya bisa huɗu na Fortune 500 suna gudanar da MCP servers, waɗanda aka tabbatar ta hanyar layin izini na OAuth 2.1 na daidaito. A kai a kai, kuma daidai, ana kwatanta shi da USB-C don AI: yana rushe mafarkin haɗakarwa na M×N — kowane model an haɗa shi da hannu zuwa kowane kayan aiki — zuwa M+N. Taƙaitaccensa na kansa shi ne layin da ke da muhimmanci ga bankuna: API na shirye-shirye ne; MCP na agentoci ne. REST API yana tsammanin mai kira zai san gaba wane endpoint zai buga da kuma da wane sigogi. Agent yana tsammanin zai gano kayan aikin da ke akwai a lokacin gudanarwa kuma ya yanke shawara, da kansa, yadda da lokacin da zai yi amfani da su.
Wannan ba na tunani ba ne ga baitulmali. Tsarin ya riga ya daidaita a cikin baitulmalin bankin kamfanoni-da-saka-jari a 2026: agent yana karanta bayanan kuɗi na ISO 20022, yana kiran ƙayyadadden saitin kayan aiki, kuma yana daidaita ruwa a cikin iyakokin manufa, tare da kula da SR 11-7, DORA da EU AI Act a kewaye da shi. Nahawu na bayanai yana shirye don wannan. Saman API bai shirya ba.
Rashin daidaituwar, daidai
Cire agent zuwa abin da yake buƙata da gaske daga abokin ma'amala na banki kuma jerin gajere ne kuma marar tausayi:
- Yarjejeniya da injina zai iya ganowa — bayanin OpenAPI, ko manifesto na kayan aiki, wanda agent zai iya karantawa a lokacin gudanarwa maimakon PDF da mutum ke karantawa sau ɗaya.
- Model na tabbatarwa ɗaya — bayanin OAuth2/mTLS na daraja-ta-kuɗi (FAPI shi ne madogara mai bayyana), ba wani daban musafaha ga kowane banki ba.
- Idempotency a matsayin tabbaci — nuni na umarni na musamman da ke mai da biyan kuɗi da aka sake gwadawa zama babu-aiki, domin agent zai sake gwadawa.
- Error grammar mai tabbaci — gazawa iri ɗaya na nufin abu iri ɗaya a ko'ina, don model ya iya yin tunani a kansa.
- Sigar semantic da gano iyawa — don agent ya iya faɗi abin da abokin ma'amala zai iya yi a wannan kwata ba tare da bayanin fitarwa na ɗan adam ba.
- Payloads na ISO 20022 tsararre, izini da haƙƙoƙi, da audit trail da za a iya gano ɓarnarsa — abin, izinin, da shaidar.
Saka wannan a gaban bankin kamfanoni kamar yadda yake kuma kowane layi yana rarrabuwa zuwa yaruka N — ɗaya ga kowane banki. Agent ɗin da ya kamata ya kawar da matsalar M×N ya sadu da ita kuma a kan iyakar banki, domin kowace cibiya, a zahiri, server ne na musamman da nahawunsa na kansa don "ma'auni", ra'ayinsa na kansa na "matsayin biyan kuɗi", rawar auth ɗinsa na kansa da tunaninsa na kansa game da abin da kuskure yake. Ka'idar ta daidaita gefen agent na waya. Babu wanda ya daidaita na banki.
Yanayin gazawa, an mai da shi na zahiri
Ka mai da shi na musamman, domin nan ne abstraction ke ciza. Ka yi tunanin agent na ruwa da aka ba shi izini ya share kuɗi a cikin bankuna uku don riƙe kowane asusu a cikin iyaka da aka nufa. Yana harba umarni uku kusan iri ɗaya kuma, kamar yadda hanyoyin sadarwa suke, yana buga timeout a kan kowanne.
Bank A yana ɗaukar timeout ɗin a matsayin ba a sani ba — lafiya ne a sake gwadawa, don haka agent ɗin ya sake gwadawa, kuma umarni na asali ma ya daidaita: kwafin biyan kuɗi. Bank B yana ɗaukar timeout ɗin guda a matsayin an gabatar — kada a sake gwadawa, amma bai taɓa fitar da tabbaci da agent zai iya fassara ba, don haka umarni ya kasance cikin rashin tabbas yayin da agent, bai ga nasara ba, ya ɗaga ko sake tura shi: umarni da ya makale da matsayi da aka rubuta sau biyu. Bank C yana dawo da HTTP 200 mai murna da ƙin yarda a ɓoye a cikin jikin payload; agent yana karanta lambar matsayi, yana yin alama an gama sharewa, kuma yana ci gaba: gazawa cikin shiru da ke fitowa kawai washegari a matsayin karyewar daidaitawa da babu wanda zai iya bayyana.
Bankuna uku, yanayi ɗaya, gaskiya uku masu saɓani — kuɗi na kwafi sun fita ƙofa a A, umarni da aka daskare a B, nasara ta fatalwa a C. Mai kula da baitulmali na ɗan adam da ya kira manajojin dangantaka uku ya warware shi kafin karin abincin rana. Agent ba zai iya kiran kowa ba. Wannan shi ne ainihin dalilin da ya sa "idempotency a matsayin tabbaci" da "error grammar mai tabbaci" ba abubuwan alfarma ne na gine-gine ba: ba tare da su ba, rarrabuwar da ta kashe lokacin ɗan adam kawai yanzu tana motsa kuɗin gaske ba daidai ba, cikin saurin injina, a cikin kowane abokin ma'amala a lokaci ɗaya.
Dalilin da ya sa "nannaɗe kowane banki cikin MCP server" ba shi ne mafita ba
Amsa mai sauri ita ce ba wa kowane banki MCP server kuma a gama. Ba ta riƙe, domin tana ƙaura da rarrabuwar maimakon cire ta. Bankuna arba'in sun zama servers arba'in da ma'anoni arba'in, hanyoyin auth arba'in kuma babu ma'ana ta kowa — kuma, mafi muhimmanci, babu bene na aiki na kowa: babu tsarin latency na kowa, babu matakin samuwa da aka amince, babu tabbacin idempotency da za a iya kwatanta. Yanayin gazawar da ke sama ya wanzu ta cikin nannaɗe ba tare da lahani ba. Mafi muni, mai kira yanzu wani model ne mara tabbaci mai damar rubutu zuwa layukan biyan kuɗi, wanda ba tambaya ce ta haɗakarwa kaɗai ba amma matsala ce ta haɗarin model da juriya ta aiki da ke sauka kai tsaye a kan SR 11-7, DORA da EU AI Act. Primitives na MCP na human-in-the-loop — elicitation don tabbaci, sampling don tunani — suna da mahimmanci kuma ana maraba da su, amma tattaunawar tabbaci ba maye gurbin abokin ma'amala da ke nuna hali da za a iya hasashe ba. Ba za ka iya sarrafawa a girma abin da ba za ka iya bayyana daidai ba. Servers na musamman dubu ba ma'auni ba ne; fadama iri ɗaya ce mai fentin JSON-RPC.
Makoma biyu, da zaɓi na dabarun
Wanda ya warware wannan yana ƙayyade wanda ya mallaki dangantakar kamfanoni na shekaru goma masu zuwa, kuma akwai 'yan takara biyu kawai.
A na farko, bankuna suna daidaita samansu na kansu. Suna buga API da ke shirye don agent, suna riƙe haɗin kai tsaye ga mai kula da baitulmali, kuma suna zama abokin ma'amala da agent ke ganowa kuma yake kiran. A na biyu, aggregators suna daidaita shi a madadinsu. Ƙananan platforms suna ayyana yarjejeniyar agent ta zahiri, kuma bankuna sun zama endpoints da za a iya musanya a bayanta — ana iya kai su ne kawai ta hanyar abstraction na wani. Wannan ba hasashe ba ne; labarin dillanci ne yana gudana gaba wani sashe. Aikin bankin ma'amala na McKinsey na 2025 ya bayyana platforms na sarrafa baitulmali kamar Kyriba da GTreasury, da platforms na ofishin-shugaban-kuɗi kamar Bill.com, suna sanya kansu tsakanin abokan ciniki da bankuna da ganin matsayi guda ɗaya mara nuna banki. Shi ne ainihin layin da, a dillanci, ya sa cikin shiru dogon jela ya ɓace a bayan Plaid da Tink. Bincike guda ya lura cewa masu kula da baitulmalin kamfanoni yanzu suna riƙe bankunansu ga ma'aunin apps na masu amfani, kuma za su sauya lokacin da shigarwa, haƙƙoƙi da haɗakarwar API suka baci.
Abin da ke cikin zaɓin na dabarun mai faɗi ne. Banki da ya zama endpoint a bayan yarjejeniyar agent na aggregator yana ba da abubuwa uku a lokaci ɗaya. Margin, yayin da ake mai da ayyukansa kaya kuma ana kwatanta su farashi-na-farko ta hanyar ma'amala ta wani. Mallakar abokin ciniki, yayin da dangantaka, mahallin da farashin sauyawa ke ƙaura zuwa platform. Da ƙarfin bayanai da nazari, yayin da kwararar da ya taɓa gani ƙarshe-zuwa-ƙarshe yanzu wani mai shiga tsakani ke shiga tsakani da ke ganin abokin ciniki fiye da yadda banki yake ganin sa. Daidaita saman naka ba aikin tsabtar fasaha ba ne. Bambanci ne tsakanin zama abokin ma'amala da zama kaya.
Abin da ma'aunin dole ne ya wajabta
Jagorar da ta ɓace ba baƙon abu ba ce. Kowane sashi yana wanzu a bayyane tuni — ISO 20022 don bayanai, Payment Initiation da Instant Cash Reporting API na Swift don ayyukan tunani, BIAN don semantics, openFinance na Berlin Group don tsarin izini-da-katalog, FAPI don auth na daraja-ta-kuɗi, MCP don fallasa kayan aiki, A2A don gudanar da agent-zuwa-agent. Abin da ba ya nan shi ne aikin tara su cikin yarjejeniya mai ɗaure ga sararin kamfanoni — da horon ƙayyade benaye biyu, ba ɗaya ba. Litattafan API na B2B da ke akwai, na McKinsey a ciki, suna ɗaukar API galibi a matsayin dama ta girma da gogewa. Ba ta cewa da yawa game da tabbaci, gano iyawa a lokacin gudanarwa, ko ayyuka marasa aiki da aka daidaita — ainihin tankin da agentoci ba za su iya jurewa ba. Don haka ma'aunin dole ne ya bayyana a fili game da abin da ma'amala take da yadda take nuna hali ƙarƙashin mulki.
Benen fasaha
- Yarjejeniya ta OpenAPI-na-farko da manifesto na kayan aiki na MCP na daidaito da aka samar daga gareta — ba wanda aka rubuta da hannu a gefenta ba, don kayan aikin da agent ke gani ba za su taɓa juyawa daga API da banki ke gudanarwa ba.
- Tabbatarwa da izini na daraja-FAPI a matsayin musafaha ɗaya a cikin saman.
- Idempotency da tsarin kuskure mai tabbaci — lambobi masu ƙarko, ma'ana ɗaya ga kowace gazawa, an rubuta a cikin yarjejeniyar kanta.
- Payloads na asalin ISO 20022, tsararre kuma a shirye don adireshin gauraye.
- Sigar semantic da gano iyawa a lokacin gudanarwa — agent zai iya tambaya abin da wannan abokin ma'amala zai iya yi yau, ya sami amsa ta injina.
Benen mulki da juriya
- SLO marasa aiki da aka buga kuma aka tilasta — latency, samuwa, kuzari, sarrafawa-kai-tsaye da ƙoƙarin-ɗan-adam — an bayyana su a matsayin lambobin lokaci-da-motsi na gaske, ba yaren talla ba.
- Haƙƙoƙi, izini da audit trail da za a iya gano ɓarnarsa da aka ɗaure zuwa hanyar aiwatarwa, ba na iyo a portal na waje ba.
- Kula da haɗarin model da juriya ta aiki da aka daidaita zuwa SR 11-7, DORA da EU AI Act, don kiran agent su zama abubuwan da aka mulke da mai su, ba yanayin gefe na ban mamaki ba.
Akwai darasi mai wuya da aka ɓoye a cikin gogewar dillanci a nan. Ma'aunin da injina ke aiwatarwa dole ne ya fi daidai fiye da wanda mai haɗakarwa na ɗan adam zai iya gyara cikin shiru; rashin cikakken bayani ba ƙaramin farashi ba ne da ake biya cikin sa'o'in mai haɓaka software amma yanayin gazawa mai wuya da ake biya cikin biyan kuɗi da aka aika ba daidai ba. Yana da ma'ana cewa ƙoƙarin daidaita mai iko na masana'antar — buƙatun bayanai na ISO 20022 da aka daidaita na CPMI da PMPG, wanda ake buƙatar tsarin biyan kuɗi na duniya su karɓa kafin ƙarshen 2027 ƙarƙashin shirin biyan kuɗi na ƙasa-da-ƙasa na G20, don yaƙar ainihin wannan rarrabuwa — shi ne, bisa bayanin kansa, ba ka'ida ba kuma ba ma'aunin API ba. Yana daidaita bayanai. Ma'amala har yanzu ba aikin kowa ba ne.
Hoton da ake nufa
Gina ba shi da tsoro fiye da bincike, domin layuka uku ne, ba shiri ba. API na bankin kamfanoni na daidaito yana fallasa biyan kuɗi da rahoton kuɗi a kan REST da OpenAPI, tare da payloads na asalin ISO 20022 da auth na daraja-FAPI — yarjejeniya ɗaya, nahawu ɗaya, musafaha ɗaya. Gadar MCP tana zaune a samansa kuma tana samar da manifesto na kayan aiki mai fuskantar agent kai tsaye daga wannan yarjejeniyar OpenAPI, don gano, schemas da izini a samo su daga saman maimakon a kiyaye su a layi ɗaya da shi. Kuma layin manufa da juriya yana nannaɗe kowane kiran agent da kula da ke mai da cin gashin kai lafiya: iyakokin ma'amala da abokin ma'amala, rarrabawa, abubuwan da ke haifar da human-in-the-loop (elicitation kan ayyuka masu haɗari), sa ido kan SLO kai tsaye da kill-switch mai ƙarko. Ba a buƙatar zane don fahimtar batun — ma'aunin ba sabon layin dogo ba ne, tsari ne mai horo na layukan dogo da ke akwai tuni, tare da hanyar agent da hanyar mulki da aka gina daga farkon commit maimakon a lika bayan hatsarin.
Abin da bankuna masu aminci ke yi cikin watanni 24 masu zuwa
Idan ka amince cewa mai kira ya sauya, aikin na zahiri ne kuma ya rarraba zuwa hanyoyi biyar.
- Buga saman asalin ISO 20022, OpenAPI-na-farko. Ka ɗauki hanya ɗaya mai daraja — yawanci biyan kuɗi na ƙasa-da-ƙasa da rahoton kuɗi — kuma ka fallasa ta ta hanyar bayanin OpenAPI guda ɗaya mai sigar tare da payloads na ISO 20022, da aka daidaita zuwa schemas na CBPR+ da kake da su maimakon nahawu na biyar da aka ƙirƙira. Ka mai da shi na jama'a ga abokan ciniki da agentoci na cikin gida, tare da sandbox, kuma ka ɗauki canje-canje a matsayin fitowar samfura. Nasarar shekara-ta-farko ba cikakken ɗaukar hoto ba ne; tabbatar cewa ana iya mai da hanya ɗaya mai iya-shiga-agent ƙarshe-zuwa-ƙarshe.
- Daidaita tabbatarwa da idempotency a cikinsa. Ka karɓi bayanin daraja-FAPI guda ɗaya a matsayin musafaha kaɗai, ka wajabta maɓallan idempotency a kan kowane rubutu, kuma ka mai da "sake gwada umarni guda" tabbaci da aka rubuta a cikin yarjejeniyar — yana juya "agentoci za su sake gwadawa" daga haɗari zuwa zato mai lafiya.
- Ayyana error grammar mai tabbaci da gano iyawa. Ka ba wa kowace gazawa lamba mai ƙarko da ma'anoni masu daidaituwa, ka ƙara sigar semantic, kuma ka fallasa katalog na iyawa da agent zai iya tambaya a lokacin gudanarwa, tare da tutoci a bayyane don goyon baya na wani ɓangare, kawarwa da "ba a samu ba tukuna".
- Ɗaure haƙƙoƙi, izini da audit zuwa saman guda. Ka matsar da izini da amincewa zuwa hanyar API, ka fitar da trail da za a iya gano ɓarnarsa don kowane umarni da agent ya fara — wa, me, yaushe, ƙarƙashin wane iyakar manufa — kuma ka daidaita shi a fili da SR 11-7, DORA da EU AI Act don layin na biyu ya iya amincewa da shi.
- Buga benaye marasa aiki, sannan ka gudanar da matukin agent da ake kula da shi. Ka yi alkawari kan latency, samuwa, kuzari da manufofin STP na hanyar kuma ka auna su; sannan ka kafa agent na ruwa ko share-kuɗi da ake kula da shi wanda yake amfani da wannan saman kawai, tare da iyakoki masu ƙarko, wuraren dubawa na human-in-the-loop da cikakken audit, na watanni shida zuwa goma sha biyu. Wannan ita ce aikin tilastawa da kake sarrafawa da kanka — yana tabbatar cewa agent zai iya motsa kuɗi lafiya a cikin iyakokin manufa lokacin da saman zai iya hasashe, kuma yana gaya maka da sauri inda ma'aunin ka har yanzu buri ne maimakon gaskiya.
Aikin tilastawa
Masana'antar ta riga ta tabbatar cewa za ta iya motsawa lokacin da wani abu ya tilasta ta. Sauyawar adireshin-tsararre na Swift na Nuwamba 2026 — bayan da za a ƙi adireshin da ba tsararre a biyan kuɗi na ƙasa-da-ƙasa kai tsaye, ba tare da juyawa na gaggawa ba — ta jawo kasuwa mai jinkiri zuwa bayanan ISO 20022 tsararre a ranar da aka ƙayyade, wanda buƙatar CPMI ta ƙarshen 2027 na daidaita bayanai a cikin shirin biyan kuɗi na G20 ta ƙarfafa. Lura da abin da ƙoƙarin biyu ke daidaitawa: bayanai, ba ma'amala ba. Ana tilasta wa nahawu ya zama mai tsafta. An bar saman ga hankalin kowane banki — wanda shi ne ainihin hankalin da agentoci ba za su iya aiki da shi ba. Ga agent, wannan yana nufin payloads za su zama masu daidaituwa a ƙarshe yayin da halin da ke bayansu ya kasance mai saɓani — juyewar abin da injina ke buƙata da gaske, wanda shi ne halin da za a iya hasashe na farko da bayanai masu tsafta na biyu.
Don haka wannan ita ce kuskuren da ba a tilasta ba da za a guje: jira na kwamiti na duniya ya albarkaci ma'aunin API na bankin kamfanoni kafin aiki. Bankunan da suka buga saman asalin ISO 20022 da ke shirye don agent yanzu — yarjejeniyar OpenAPI, manifesto na MCP da aka samar daga gareta, auth na daraja-ta-kuɗi, da benaye marasa aiki da za su tsaya a bayansu da gaske — za su zama abokan ma'amala na tsohuwar zaɓi don baitulmali mai cin gashin kai. Kayan aikinsu za su zama waɗanda agentoci za su iya ganowa, amincewa da su kuma su kira ba tare da ɗan adam a tsakiya ba. Bankunan da suka jira za a iya kai su ne kawai ta hanyar abstraction na aggregator, suna hayar dangantakar abokan cinikinsu ga duk wanda ya mallaki adapter.
Nahawu ba tare da jagora ba ba ma'auni ba ne. ISO 20022 ya gaya wa bankin kamfanoni yadda za a magana. Bai taɓa gaya masa inda zai je ba. Agentoci sun iso, masu iya magana kuma marasa haƙuri, kuma taswirar har yanzu ba ta nan. Zana ta yanzu shi ne aikin more muhimmanci na kayan more rayuwa a bankin ma'amala — kuma, don sau ɗaya, ba mai tsari ba ne ke saita ranar ƙarshe amma injinan da suka riga suka jira a ma'amala.
Tambayoyin da Ake Yawan Yi
Shin ISO 20022 ba shi ne ma'aunin da ya ɓace ba? A'a. ISO 20022 nahawu ne na bayanai, ba yarjejeniya ce ta API ba. pain.001 yana gaya wa tsari yadda za a fasalta canja wurin kuɗi; ba ya faɗi wane endpoint ke ƙirƙirar ɗaya ba, yadda yake tabbatarwa, yadda yake shafa-shafa, ko yadda yake ba da rahoton gazawa. Nahawu na shirye don agentoci. Saman — ma'amala da injina zai iya ganowa, mai nuna hali daidai da agent ke kiran da gaske — bai shirya ba.
Me ya sa ba za a nannaɗe kowane banki cikin MCP server kawai ba? Domin yana ƙaura da rarrabuwar maimakon cire ta. Bankuna arba'in sun zama servers arba'in da ma'anoni arba'in, hanyoyin auth arba'in kuma — mafi muhimmanci — babu bene na aiki na kowa: babu tsarin latency na kowa, babu matakin samuwa da aka amince, babu tabbacin idempotency da za a iya kwatanta. Mai kira yanzu wani model ne mara tabbaci mai damar rubutu zuwa layukan biyan kuɗi, wanda matsala ce ta haɗarin model da juriya ta aiki ƙarƙashin SR 11-7, DORA da EU AI Act. Servers na musamman dubu ba ma'auni ba ne.
Menene matakin farko mafi amfani ga banki? Buga hanya ɗaya ta asalin ISO 20022, OpenAPI-na-farko — yawanci biyan kuɗi na ƙasa-da-ƙasa da rahoton kuɗi — tare da musafaha na daraja-FAPI, idempotency a matsayin tabbaci da aka rubuta, da error grammar mai tabbaci. Sannan ka gudanar da matukin agent da ake kula da shi a kan wannan saman kawai, tare da iyakoki masu ƙarko, wuraren dubawa na human-in-the-loop da cikakken audit. Tabbatar da hanya ɗaya ƙarshe-zuwa-ƙarshe ya fi tsarin da ke ɗaukar komai kuma bai wajabta komai ba.
Wa ke warware wannan idan bankuna ba su yi ba? Aggregators. Ƙananan platforms na baitulmali da na ofishin-shugaban-kuɗi za su ayyana yarjejeniyar agent ta zahiri, kuma bankuna sun zama endpoints da za a iya musanya a bayanta — suna ba da margin, mallakar abokin ciniki da bayanai ƙarshe-zuwa-ƙarshe a lokaci ɗaya. Labarin dillanci ne, inda Plaid da Tink suka sha dogon jela, yana gudana gaba wani sashe zuwa bankin kamfanoni.
Nassoshi
- Model Context Protocol — takaddun hukuma ⧉. [An buɗe tushen MCP a Nuwamba 2024 kuma aka ba da gudummawar sa ga Agentic AI Foundation na Linux Foundation a Disamba 2025 tare da Block da OpenAI; layin gano-kayan-aiki na lokacin gudanarwa da bincike ke ginawa a kai. Adadin karɓuwa a cikin rubutun karatun masana'antar jagora ne kuma an nuna su a matsayin haka.]
- Berlin Group — NextGenPSD2 da openFinance ⧉. [Ma'aunin API na dillanci na Turai na zahiri da kai wa ga yanayin amfani na kamfanoni — an ambata don tsarin izini-da-katalog da bambanci na dillanci-da-kamfanoni.]
- Financial Data Exchange (FDX) ⧉. [Ma'aunin raba bayanai na dillanci na Amurka, an ambata don girman yarjejeniyoyin dillanci da aka daidaita da bankin kamfanoni ba shi da makamancinsa.]
- McKinsey & Company — Fahimtar Ayyukan Kuɗi ⧉. [Bincike na API na bankin ma'amala: gadon host-to-host / SFTP, niyyar zuba jari na API na sarrafa kuɗi na ~85%, da shiga tsakani na platform na baitulmali. An ambata don bincike na kasuwa; tsari da ƙarshe a nan na marubucin kansa ne.]
- Bank for International Settlements (CPMI) — Buƙatun bayanai na ISO 20022 da aka daidaita ⧉. [Buƙatar ƙarshen 2027 na daidaita bayanan biyan kuɗi — bisa bayanin kansa ba ka'ida ba kuma ba ma'aunin API ba — an ambata don batun "nahawu ba tare da saman ba".]
- Swift — ISO 20022 don cibiyoyin kuɗi ⧉. [CBPR+ da matakin adireshin-tsararre na Nuwamba 2026; Payment Initiation da Instant Cash Reporting API an ambata a matsayin ayyukan tunani, ba saman kowa ba.]
An sake dubawa na ƙarshe a Yuli 2026. Bincike na asali; an ambaci majiyoyi, ba a sake buga su ba. Adadin karɓuwa da na kasuwa karatun masana'antar jagora ne — a tabbatar da su a kan majiyoyin farko kafin a sake buga. An ba da lasisi ƙarƙashin CC-BY-4.0.
Bita ta ƙarshe .
Sake buga wannan labarin
Kwafa tsarin Medium
# From Fragmentation to Fault Line: Corporate Banking's Missing API Standard in the Agentic Era — Sebastien Rousseau > Originally published at [https://sebastienrousseau.com/ha/2026-07-07-corporate-banking-api-standard-agentic-mcp-2026/](https://sebastienrousseau.com/ha/2026-07-07-corporate-banking-api-standard-agentic-mcp-2026/) Bankin dillanci ya sami ma'aunin API nasa shekaru goma da suka wuce. Bankin kamfanoni bai taɓa samu ba — kuma yanzu da agentocin AI da Model Context Protocol suka mai da haɗakarwa zama shawara ta lokacin gudanarwa, gibin ya zama layin karyewa. Read the full article on sebastienrousseau.com: https://sebastienrousseau.com/ha/2026-07-07-corporate-banking-api-standard-agentic-mcp-2026/
Kwafa tsarin Mastodon
From Fragmentation to Fault Line: Corporate Banking's Missing API Standard in the Agentic Era — Sebastien Rousseau Bankin dillanci ya sami ma'aunin API nasa shekaru goma da suka wuce. Bankin kamfanoni bai taɓa samu ba — kuma yanzu da agentocin AI da Model Context Protocol suka mai da haɗakarwa zama shawara ta lokacin gudanarwa, gibin ya zama layin karyewa. https://sebastienrousseau.com/ha/2026-07-07-corporate-banking-api-standard-agentic-mcp-2026/
Kwafa an tsara don LinkedIn
From Fragmentation to Fault Line: Corporate Banking's Missing API Standard in the Agentic Era — Sebastien Rousseau Bankin dillanci ya sami ma'aunin API nasa shekaru goma da suka wuce. Ga abubuwan da ya kamata a lura da su na dabarun: - Duniyoyin banki biyu, ɗayansu an daidaita shi. Duba dillanci kuma hoton yana da rikici amma ana iya kewayawa. - Dalilin da ya sa rarrabuwar ta wanzu — da dalilin da ya sa hakan ke ƙarewa. Har shekaru ashirin wannan ya kasance abin jurewa, domin mai haɗakarwa ɗan adam ne kuma mai haƙuri. - Mai kira ya sauya. Wannan mai amfani ya iso cikin watanni goma sha takwas. - Rashin daidaituwar, daidai. Cire agent zuwa abin da yake buƙata da gaske daga abokin ma'amala na banki kuma jerin gajere ne kuma marar tausayi:. Menene hanyar ƙungiyar ku wajen magance ƙalubalen da aka kawo a wannan rubuce-rubucen? → https://sebastienrousseau.com/ha/2026-07-07-corporate-banking-api-standard-agentic-mcp-2026/ #ApiNaBankinKamfanoni #Iso20022 #ModelContextProtocol #Mcp #AgenticAi Sebastien Rousseau | CC-BY-4.0
Buga wannan labari
From Fragmentation to Fault Line: Corporate Banking's Missing API Standard in the Agentic Era — Sebastien Rousseau
Bankin dillanci ya sami ma'aunin API nasa shekaru goma da suka wuce. Bankin kamfanoni bai taɓa samu ba — kuma yanzu da agentocin AI da Model Context Protocol suka mai da haɗakarwa zama shawara ta lokacin gudanarwa, gibin ya zama layin karyewa.
BibTeX
@online{rousseau2026from,
author = {Rousseau, Sebastien},
title = {{From Fragmentation to Fault Line: Corporate Banking's Missing API Standard in the Agentic Era — Sebastien Rousseau}},
year = {2026},
url = {https://sebastienrousseau.com/ha/2026-07-07-corporate-banking-api-standard-agentic-mcp-2026/},
urldate = {2026}
}RIS
TY - GEN AU - Rousseau, Sebastien TI - From Fragmentation to Fault Line: Corporate Banking's Missing API Standard in the Agentic Era — Sebastien Rousseau PY - 2026 UR - https://sebastienrousseau.com/ha/2026-07-07-corporate-banking-api-standard-agentic-mcp-2026/ ER -
Vancouver
Rousseau S. From Fragmentation to Fault Line: Corporate Banking's Missing API Standard in the Agentic Era — Sebastien Rousseau. sebastienrousseau.com. 2026 Jul 7. Available from: https://sebastienrousseau.com/ha/2026-07-07-corporate-banking-api-standard-agentic-mcp-2026/
Chicago
Rousseau, Sebastien. "From Fragmentation to Fault Line: Corporate Banking's Missing API Standard in the Agentic Era — Sebastien Rousseau." sebastienrousseau.com. July 7, 2026. https://sebastienrousseau.com/ha/2026-07-07-corporate-banking-api-standard-agentic-mcp-2026/.
APA
Rousseau, S. (2026, July 7). From Fragmentation to Fault Line: Corporate Banking's Missing API Standard in the Agentic Era — Sebastien Rousseau. sebastienrousseau.com. https://sebastienrousseau.com/ha/2026-07-07-corporate-banking-api-standard-agentic-mcp-2026/
Sake buga wannan labari
From Fragmentation to Fault Line: Corporate Banking's Missing API Standard in the Agentic Era — Sebastien Rousseau
Bankin dillanci ya sami ma'aunin API nasa shekaru goma da suka wuce. Bankin kamfanoni bai taɓa samu ba — kuma yanzu da agentocin AI da Model Context Protocol suka mai da haɗakarwa zama shawara ta lokacin gudanarwa, gibin ya zama layin karyewa.
An lasisin wannan labari a karkashin Creative Commons Attribution 4.0 International. Sake bugawa na bukatar nuna asalin URL na asali.
From Fragmentation to Fault Line: Corporate Banking's Missing API Standard in the Agentic Era — Sebastien Rousseau Bankin dillanci ya sami ma'aunin API nasa shekaru goma da suka wuce. Bankin kamfanoni bai taɓa samu ba — kuma yanzu da agentocin AI da Model Context Protocol suka mai da haɗakarwa zama shawara ta lokacin gudanarwa, gibin ya zama layin karyewa. Originally published at https://sebastienrousseau.com/ha/2026-07-07-corporate-banking-api-standard-agentic-mcp-2026/ by Sebastien Rousseau. Licensed under CC-BY-4.0.
