{"id":6593,"date":"2026-08-18T23:08:24","date_gmt":"2026-08-18T23:08:24","guid":{"rendered":"https:\/\/www.kindgeek.com\/blog\/?p=6593"},"modified":"2026-08-18T23:11:37","modified_gmt":"2026-08-18T23:11:37","slug":"iso-20022-migration","status":"publish","type":"post","link":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration","title":{"rendered":"Why Banks and Credit Unions Are Running Out of Time on ISO 20022"},"content":{"rendered":"\n<p><a href=\"https:\/\/www.frbservices.org\/news\/press-releases\/071525-iso20022-migration-announcement\" target=\"_blank\" rel=\"noreferrer noopener\">Fedwire<\/a>, the US domestic wire system, settles more than $4.7 trillion in transfers a day, and as of July 14, 2025, every message on it must speak ISO 20022. International and regional payments are moving on synchronized timelines: <a href=\"https:\/\/www.swift.com\/news-events\/press-releases\/global-financial-community-completes-switch-iso-20022-paving-way-new-levels-cross-border-payment-speed-and-innovation-around-world\" target=\"_blank\" rel=\"noreferrer noopener\">SWIFT closes its coexistence window<\/a> in November 2025, while domestic rails in the US (Fedwire, CHIPS) and UK (CHAPS) enforce strict data rules.<\/p>\n\n\n\n<p>Most banks and credit unions technically cleared the first ISO 20022 migration deadline. Whether they built infrastructure ready for the next one is a separate question. <a href=\"https:\/\/www.retailbankerinternational.com\/comment\/iso-20022-next-phase-will-test-bank-data-foundations\/\" target=\"_blank\" rel=\"noreferrer noopener\">Industry research<\/a> puts the gap in stark terms: 44% of banks say they&#8217;re not on track for the November 2026 milestone. Around a third of customer postal address records across onboarding, CRM, and payment systems are still unstructured.<\/p>\n\n\n\n<p>Much of that gap traces back to legacy MT-based systems that were built to store flat, fixed-length data and were never redesigned to hold anything richer.&nbsp; It&#8217;s a structural issue, and the cost of it is about to rise.<\/p>\n\n\n\n<p>While ISO 20022 is a global messaging framework, implementation timelines differ across jurisdictions. This guide breaks down mandatory cutovers for institutions operating across US domestic rails (Fedwire, CHIPS), UK domestic rails (CHAPS), and global cross-border networks (SWIFT CBPR+).<\/p>\n\n\n\n<div id=\"wlqa-toc-block\" style=\"max-width: 480px;\">\n  <div class=\"wlqatoc-header\">Content:<\/div>\n  <ul class=\"wlqatoc-list\">\n    <li class=\"wlqatoc-item\"><a href=\"#section-1\" class=\"wlqatoc-link\"><span class=\"wlqatoc-num\">01<\/span>ISO 20022 Migration Is a Data Transformation<\/a><\/li>\n    <li class=\"wlqatoc-item\"><a href=\"#section-2\" class=\"wlqatoc-link\"><span class=\"wlqatoc-num\">02<\/span>The ISO 20022 Deadlines Turning Compliance Into a Legacy System Problem<\/a><\/li>\n    <li class=\"wlqatoc-item\"><a href=\"#section-3\" class=\"wlqatoc-link\"><span class=\"wlqatoc-num\">03<\/span>Where ISO 20022 Migration Breaks in Legacy Architecture<\/a><\/li>\n    <li class=\"wlqatoc-item\"><a href=\"#section-4\" class=\"wlqatoc-link\"><span class=\"wlqatoc-num\">04<\/span>Exceptions and Investigations<\/a><\/li>\n    <li class=\"wlqatoc-item\"><a href=\"#section-5\" class=\"wlqatoc-link\"><span class=\"wlqatoc-num\">05<\/span>The Cost of a Patch-First ISO 20022 Strategy<\/a><\/li>\n    <li class=\"wlqatoc-item\"><a href=\"#section-6\" class=\"wlqatoc-link\"><span class=\"wlqatoc-num\">06<\/span>What Production-Ready ISO 20022 Architecture Looks Like<\/a><\/li>\n    <li class=\"wlqatoc-item\"><a href=\"#section-7\" class=\"wlqatoc-link\"><span class=\"wlqatoc-num\">07<\/span>Readiness Checklist for Banks and Credit Unions<\/a><\/li>\n    <li class=\"wlqatoc-item\"><a href=\"#section-8\" class=\"wlqatoc-link\"><span class=\"wlqatoc-num\">08<\/span>How Kindgeek Helps Financial Institutions<\/a><\/li>\n    <li class=\"wlqatoc-item\"><a href=\"#section-9\" class=\"wlqatoc-link\"><span class=\"wlqatoc-num\">09<\/span>FAQ<\/a><\/li>\n  <\/ul>\n<\/div>\n<style>\n#wlqa-toc-block{\n  overflow:hidden;\n  margin-bottom:20px;\n}\n#wlqa-toc-block .wlqatoc-header{\n  font-weight:700;\n  text-align:left;\n  padding:14px 24px;\n}\n#wlqa-toc-block .wlqatoc-list{\n  list-style:none;\n  margin:0;\n  padding:8px 0;\n}\n#wlqa-toc-block .wlqatoc-item{\n  border-bottom:1px solid rgba(2,190,190,.08);\n}\n#wlqa-toc-block .wlqatoc-item:last-child{\n  border-bottom:none;\n}\n#wlqa-toc-block .wlqatoc-link{\n  display:flex;\n  align-items:flex-start;\n  gap:16px;\n  padding:14px 24px;\n  color:#0a1a1a;\n  opacity:.85;\n  text-decoration:none;\n  line-height:1.4;\n  transition:opacity .15s ease;\n}\n#wlqa-toc-block .wlqatoc-link:hover{\n  opacity:1;\n  color:#02bebe;\n}\n#wlqa-toc-block .wlqatoc-num{\n  flex-shrink:0;\n  color:#02bebe;\n  font-weight:700;\n  opacity:.7;\n  min-width:20px;\n  padding-top:1px;\n}\n<\/style>\n\n\n\n<a id=\"section-1\"><\/a>\n\n\n\n<h2 class=\"wp-block-heading\">ISO 20022 Migration Is a Data Transformation<\/h2>\n\n\n\n<p>The first ISO 20022 deadline could be met with a message-format upgrade. The two deadlines that follow require a change to how payment data is modeled and stored, which is a larger scope of work.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The Limits of Translator-Only Gateways<\/h3>\n\n\n\n<p>A translation layer in front of a legacy core does what it&#8217;s built to do: it converts an incoming pacs.008 or camt.056 into something the core can read, and converts the core&#8217;s output back into ISO 20022 on the way out. That&#8217;s enough to pass a connectivity test. It doesn&#8217;t preserve what the message carries.<\/p>\n\n\n\n<p>Structured party identification, full remittance detail, purpose codes, and unique end-to-end references all get compressed the moment they hit a core still built around fixed-length MT fields. The message arrives rich. What the bank&#8217;s systems retain is a truncated, MT-shaped version of it.<\/p>\n\n\n\n<p>A structured beneficiary address with distinct street, city, and postal-code elements, for instance, is often flattened straight back into a single free-text line the moment it touches the core.<\/p>\n\n\n\n<p>Fully unstructured postal addresses are prohibited by SWIFT starting November 14, 2026. From that date forward, messages must carry at least a hybrid address (with structured Town Name and Country) or a fully structured address, or the payment will be rejected by the network.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance on Paper Differs From Production Readiness<\/h3>\n\n\n\n<p>A bank can pass every certification test SWIFT and the Federal Reserve require and still be nowhere near ready to use the data ISO 20022 was built to carry. Certification confirms the institution can send and receive the new formats. It says nothing about whether the core banking platform stores that data in a queryable, structured way, or whether operations staff can act on it without manual lookups.<\/p>\n\n\n\n<p><a href=\"https:\/\/www.retailbankerinternational.com\/comment\/iso-20022-next-phase-will-test-bank-data-foundations\/\" target=\"_blank\" rel=\"noreferrer noopener\">Nearly half of banks report<\/a> implementing only the minimum changes to their exceptions and investigations workflows, rather than the broader operational reform ISO 20022 was designed to enable.<\/p>\n\n\n\n<a id=\"section-2\"><\/a>\n\n\n\n<h2 class=\"wp-block-heading\">How Legacy Systems Turn ISO 20022 Compliance Into an Architectural Bottleneck<\/h2>\n\n\n\n<p>The ISO 20022 migration timeline is a sequence of hard cutovers across every major payment rail a US or UK institution touches. The <a href=\"https:\/\/www.swift.com\/news-events\/press-releases\/global-financial-community-completes-switch-iso-20022-paving-way-new-levels-cross-border-payment-speed-and-innovation-around-world\" target=\"_blank\" rel=\"noreferrer noopener\">SWIFT ISO 20022 migration for cross-border payments<\/a>, <a href=\"https:\/\/www.frbservices.org\/news\/press-releases\/071525-iso20022-migration-announcement\" target=\"_blank\" rel=\"noreferrer noopener\">Fedwire&#8217;s domestic wire cutover<\/a>, and the <a href=\"https:\/\/www.bankofengland.co.uk\/paper\/2025\/ps\/expanding-mandatory-iso-20022-enhanced-data-in-chaps-from-2027\" target=\"_blank\" rel=\"noreferrer noopener\">CHAPS enhanced-data rules<\/a> each landed on their own schedule.\u00a0<\/p>\n\n\n\n<p>The requirements are identical whether you&#8217;re planning ISO 20022 for banks or ISO 20022 for credit unions.<\/p>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Region \/ Scope<\/strong><\/th><th><strong>Rail \/ Scheme<\/strong><\/th><th><strong>Deadline<\/strong><\/th><th><strong>Requirement \/ Change<\/strong><\/th><\/tr><\/thead><tbody><tr><td><strong>Global (SWIFT)<\/strong><\/td><td>SWIFT CBPR+<\/td><td>Nov 2025 <em>(completed)<\/em><\/td><td>End of MT\/ISO coexistence for cross-border payment instructions<\/td><\/tr><tr><td><strong>Global (SWIFT)<\/strong><\/td><td>SWIFT CBPR+<\/td><td>Nov 2026<\/td><td><strong>Unstructured postal addresses rejected<\/strong> (hybrid or fully structured required)<\/td><\/tr><tr><td><strong>United States<\/strong><\/td><td>Fedwire Funds<\/td><td>July 14, 2025 <em>(completed)<\/em><\/td><td>Full cutover to ISO 20022 (FAIM retired)<\/td><\/tr><tr><td><strong>United States<\/strong><\/td><td>CHIPS<\/td><td>Apr 2024 <em>(completed)<\/em><\/td><td>Migrated to ISO 20022<\/td><\/tr><tr><td><strong>United Kingdom<\/strong><\/td><td>CHAPS<\/td><td>Nov 2027<\/td><td><strong>Purpose Codes mandatory<\/strong> across direct participant payment channels<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>For institutions still running MT-based core banking platforms, each row in the table represents a separate integration project. Credit unions may face this challenge differently from large banks because many rely on external core banking providers rather than managing these platforms in-house. These providers must manage the November 2026 and 2027 cutovers across multiple client institutions at the same time.<\/p>\n\n\n\n<p>This creates <a href=\"https:\/\/www.americanbanker.com\/payments\/news\/banks-credit-unions-still-face-iso-20022-delays\" target=\"_blank\" rel=\"noreferrer noopener\">a potential bottleneck<\/a>. Smaller institutions that depend on a provider\u2019s release schedule have less control over their preparation timeline and fewer options to negotiate priority if the provider falls behind.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why MT-Based Cores Struggle With ISO 20022 Structured Data<\/h3>\n\n\n\n<p>MT messages were built around fixed, size-limited fields. That worked in the 1970s, but these fields have since been stretched to carry information they were never designed to handle. ISO 20022 takes a different approach, using structured XML elements for specific data points. For example, an address can have separate fields for the street, building number, and postal code instead of one free-text line.<\/p>\n\n\n\n<p>A core system built around MT-style tables can receive this structured data, but it often needs schema changes to store it properly. Otherwise, a translation layer may strip away the structure before the data reaches the core.&nbsp;<\/p>\n\n\n\n<p>This is why the next deadlines carry more risk than the previous ones. November 2026 is not just about accepting a new message format. Banks will also need to reject payments without structured address data, which means their own systems must generate and validate this data for outbound payments.<\/p>\n\n\n\n<a id=\"section-3\"><\/a>\n\n\n\n<h2 class=\"wp-block-heading\">Where ISO 20022 Migration Breaks in Legacy Architecture<\/h2>\n\n\n\n<p>Four failure patterns show up repeatedly in institutions that limited the first deadline&#8217;s scope to certification requirements:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data model mismatch. MT-oriented cores store addresses, names, and references as flat strings. ISO 20022 messages arrive as structured elements. Without a genuine data model change, every mapping between the two is lossy in one direction or the other.<\/li>\n\n\n\n<li>Middleware that translates format but drops context. Gateways built to pass certification tests validate syntax; preserving every structured element through to storage is a separate, often-skipped step. Purpose codes and structured remittance data are common casualties.<\/li>\n\n\n\n<li>Weak party identification and incomplete remittance data. When ultimate debtor\/creditor and full remittance information don&#8217;t make it into the core, reconciliation teams end up rebuilding context manually from whatever fragments survive translation.<\/li>\n\n\n\n<li>Manual reconciliation and exception-handling bottlenecks. Structured data is what makes automated matching possible. Strip it out at the translation layer, and headcount becomes the only lever left to close the gap, right as transaction volumes and E&amp;I case volumes are both rising.<\/li>\n<\/ul>\n\n\n\n<p>These four issues are rarely caught during certification audits. A bank can be fully certified on every rail listed above and still have all four problems in production. That is because certification checks whether messages follow the required format. It does not check how the bank stores, processes, or uses the data after receiving it.<\/p>\n\n\n\n<a id=\"section-4\"><\/a>\n\n\n\n<h2 class=\"wp-block-heading\">Exceptions and Investigations: The Real ISO 20022 Test<\/h2>\n\n\n\n<p>If the first migration deadline tested message formats, the ISO 20022 exceptions and investigations (E&amp;I) deadline tests whether an institution&#8217;s operations function works on structured data.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why ISO 20022 E&amp;I Requires More Than Message Translation<\/h3>\n\n\n\n<p><a href=\"https:\/\/www.swift.com\/products\/case-management\" target=\"_blank\" rel=\"noreferrer noopener\">SWIFT&#8217;s Case Management service<\/a>, live since November 2024, replaces the free-text MT195\/MT199 query-and-response pattern with structured camt.110 and camt.111 messages routed through a central Case Orchestrator rather than bank-to-bank.\u00a0<\/p>\n\n\n\n<p>From November 2026, every institution <a href=\"https:\/\/www.swift.com\/news-events\/news\/transforming-exceptions-and-investigations\" target=\"_blank\" rel=\"noreferrer noopener\">must be able to receive a camt.110 investigation request<\/a>. From November 2027, sending and receiving those messages through Case Management in ISO 20022 format becomes the only option. Bilateral MT exchange for E&amp;I ends entirely.<\/p>\n\n\n\n<p>A camt.110 translation is only useful if it preserves the structured data that operations teams need. The entire value of Case Management, which SWIFT credits with <a href=\"https:\/\/www.redcompasslabs.com\/insights\/iso-20022-exceptions-and-investigations-ei\/\" target=\"_blank\" rel=\"noreferrer noopener\">resolution-time reductions of up to 80%<\/a> for institutions using it properly, depends on purpose, remittance, and case reference data staying structured and machine-readable all the way into the case management workflow itself.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How Recall and Investigation Workflows Break Without Structured Data<\/h3>\n\n\n\n<p>Payment cancellations face a similar problem. Stop and Recall becomes mandatory for all cancellation types by November 2027, and it relies on the Unique End-to-End Transaction Reference (UETR) being captured, stored, and matched correctly from the moment a payment is initiated.&nbsp;<\/p>\n\n\n\n<p>If the core system does not retain the UETR as a searchable field, staff may have to reconstruct it manually for each recall request. That is exactly the kind of manual work structured messaging is designed to eliminate.<\/p>\n\n\n\n<a id=\"section-5\"><\/a>\n\n\n\n<h2 class=\"wp-block-heading\">The Cost of a Patch-First ISO 20022 Strategy<\/h2>\n\n\n\n<p>Translator-only ISO 20022 compliance carries a cost: deferred spending with interest attached.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Short-term compliance, long-term rebuild costs. <a href=\"https:\/\/www.retailbankerinternational.com\/comment\/iso-20022-next-phase-will-test-bank-data-foundations\/\" target=\"_blank\" rel=\"noreferrer noopener\">Average bank spend<\/a> on the November 2026 requirements is at roughly $20 million, rising toward $30 million at larger institutions. Institutions that patch now and rebuild later are effectively paying that bill twice.<\/li>\n\n\n\n<li>Translator-only migration creates technical debt. Every rule, mapping exception, and workaround built into a translation layer is one more thing that has to be maintained, tested against the next SWIFT release, and eventually unwound when the core finally gets rebuilt properly.<\/li>\n\n\n\n<li>Payment operations lose the automation ISO 20022 was supposed to deliver. Structured data enables straight-through processing, automated sanctions screening, and self-service reconciliation. None of that materializes if the structure gets stripped out one layer before it reaches the systems that could use it.<\/li>\n<\/ol>\n\n\n\n<a id=\"section-6\"><\/a>\n\n\n\n<h2 class=\"wp-block-heading\">What Production-Ready ISO 20022 Architecture Looks Like<\/h2>\n\n\n\n<p>Institutions that are ahead of the November 2026 and 2027 deadlines share a few concrete architectural traits:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A native ISO 20022 data model across the payment layer: structured fields for party identification, remittance, and purpose codes stored as such in the core, rather than flattened into legacy tables.<\/li>\n\n\n\n<li>Middleware built to preserve structured data end-to-end: validating and carrying every ISO 20022 element through to storage, beyond basic format conversion.<\/li>\n\n\n\n<li>Automated reconciliation and payment investigation workflows: camt.110\/111 and Stop and Recall integrated directly into operations tooling instead of routed to a manual queue.<\/li>\n\n\n\n<li>Scalable integration across SWIFT, Fedwire, CHIPS, CHAPS, and CBPR+: one data model and one set of validation rules serving every rail, instead of a separate patch for each scheme&#8217;s deadline.<\/li>\n<\/ul>\n\n\n\n<a id=\"section-7\"><\/a>\n\n\n\n<h2 class=\"wp-block-heading\">ISO 20022 Readiness Checklist for Banks and Credit Unions<\/h2>\n\n\n\n<p>Before the November 2026 cutover, CTOs and payment operations leaders should be able to answer yes to each of the following. This is the same review a software audit would surface, and it&#8217;s worth running now:<\/p>\n\n\n\n<div id=\"kg-checklist-block\">\n  <div class=\"kc-card\">\n    <div class=\"kc-header\">\n      <span class=\"kc-eyebrow\">Self-assessment<\/span>\n      <h3 class=\"kc-title\">ISO 20022 Readiness Checklist<\/h3>\n      <p class=\"kc-subtitle\">Before the November 2026 cutover, you should be able to answer yes to each of the following.<\/p>\n    <\/div>\n\n    <div class=\"kc-progress-row\">\n      <div class=\"kc-progress-track\">\n        <div class=\"kc-progress-fill\" id=\"kc-progress-fill\"><\/div>\n      <\/div>\n      <span class=\"kc-progress-label\"><span id=\"kc-progress-count\">0<\/span>\/<span id=\"kc-progress-total\">5<\/span> confirmed<\/span>\n    <\/div>\n\n    <div class=\"kc-grid\" id=\"kc-grid\">\n      <label class=\"kc-item\">\n        <input type=\"checkbox\" class=\"kc-checkbox\">\n        <span class=\"kc-box\"><\/span>\n        <span class=\"kc-text\">Can your core store native ISO 20022 data, or does it only accept a translated, flattened version?<\/span>\n      <\/label>\n      <label class=\"kc-item\">\n        <input type=\"checkbox\" class=\"kc-checkbox\">\n        <span class=\"kc-box\"><\/span>\n        <span class=\"kc-text\">Can your middleware preserve structured remittance and party data all the way to storage, beyond basic syntax validation?<\/span>\n      <\/label>\n      <label class=\"kc-item\">\n        <input type=\"checkbox\" class=\"kc-checkbox\">\n        <span class=\"kc-box\"><\/span>\n        <span class=\"kc-text\">Can your payment operations team handle E&amp;I and Stop and Recall workflows without manual workarounds once bilateral MT exchange ends?<\/span>\n      <\/label>\n      <label class=\"kc-item\">\n        <input type=\"checkbox\" class=\"kc-checkbox\">\n        <span class=\"kc-box\"><\/span>\n        <span class=\"kc-text\">Can your architecture support future cross-border and instant payment products without another ground-up rebuild?<\/span>\n      <\/label>\n      <label class=\"kc-item\">\n        <input type=\"checkbox\" class=\"kc-checkbox\">\n        <span class=\"kc-box\"><\/span>\n        <span class=\"kc-text\">Do you have a documented, tested contingency plan if a counterparty or vendor isn&#8217;t ready on the November 2026 or 2027 cutover date?<\/span>\n      <\/label>\n    <\/div>\n\n    <div class=\"kc-footer\">\n      <p class=\"kc-result\" id=\"kc-result\">Answering no to any of these marks an active legacy system risk.<\/p>\n      <button type=\"button\" class=\"kc-reset\" id=\"kc-reset\">Reset<\/button>\n    <\/div>\n  <\/div>\n<\/div>\n\n<style>\n#kg-checklist-block{\n  --kc-teal: #00BFBF;\n  --kc-teal-dark: #009999;\n  --kc-green: #9EDC57;\n  --kc-ink: #191919;\n  --kc-muted: #6B7280;\n  --kc-border: #E3E8E8;\n  --kc-bg-tint: #EAFAFA;\n  font-family: 'Manrope', -apple-system, BlinkMacSystemFont, \"Segoe UI\", Roboto, sans-serif;\n  max-width: 640px;\n  margin: 28px auto;\n  box-sizing: border-box;\n}\n#kg-checklist-block *{ box-sizing: border-box; }\n\n#kg-checklist-block .kc-card{\n  background: #ffffff;\n  border: 1px solid var(--kc-border);\n  border-radius: 16px;\n  padding: 28px 30px 24px;\n  box-shadow: 0 1px 2px rgba(16,24,24,0.04), 0 8px 24px rgba(16,24,24,0.06);\n}\n\n#kg-checklist-block .kc-eyebrow{\n  display: inline-block;\n  font-size: 12px;\n  font-weight: 700;\n  letter-spacing: .08em;\n  text-transform: uppercase;\n  color: var(--kc-teal-dark);\n  background: var(--kc-bg-tint);\n  padding: 4px 10px;\n  border-radius: 999px;\n  margin-bottom: 12px;\n}\n\n#kg-checklist-block .kc-title{\n  margin: 0 0 6px;\n  font-size: 22px;\n  line-height: 1.3;\n  font-weight: 700;\n  color: var(--kc-ink);\n}\n\n#kg-checklist-block .kc-subtitle{\n  margin: 0 0 20px;\n  font-size: 14.5px;\n  line-height: 1.55;\n  color: var(--kc-muted);\n}\n\n#kg-checklist-block .kc-progress-row{\n  display: flex;\n  align-items: center;\n  gap: 12px;\n  margin-bottom: 22px;\n}\n\n#kg-checklist-block .kc-progress-track{\n  flex: 1;\n  height: 8px;\n  background: var(--kc-bg-tint);\n  border-radius: 999px;\n  overflow: hidden;\n}\n\n#kg-checklist-block .kc-progress-fill{\n  height: 100%;\n  width: 0%;\n  background: linear-gradient(90deg, var(--kc-teal), var(--kc-green));\n  border-radius: 999px;\n  transition: width .3s ease;\n}\n\n#kg-checklist-block .kc-progress-label{\n  flex-shrink: 0;\n  font-size: 13px;\n  font-weight: 600;\n  color: var(--kc-muted);\n  white-space: nowrap;\n}\n\n#kg-checklist-block .kc-grid{\n  display: flex;\n  flex-direction: column;\n  gap: 4px;\n}\n\n#kg-checklist-block .kc-item{\n  display: flex;\n  align-items: flex-start;\n  gap: 14px;\n  cursor: pointer;\n  user-select: none;\n  padding: 12px;\n  margin: 0 -12px;\n  border-radius: 10px;\n  transition: background .15s ease;\n}\n\n#kg-checklist-block .kc-item:hover{\n  background: var(--kc-bg-tint);\n}\n\n#kg-checklist-block .kc-checkbox{\n  position: absolute;\n  opacity: 0;\n  width: 0;\n  height: 0;\n}\n\n#kg-checklist-block .kc-box{\n  flex-shrink: 0;\n  width: 22px;\n  height: 22px;\n  margin-top: 1px;\n  border: 2px solid var(--kc-teal);\n  border-radius: 6px;\n  position: relative;\n  background: #fff;\n  transition: background .15s ease, border-color .15s ease, transform .15s ease;\n}\n\n#kg-checklist-block .kc-box::after{\n  content: '';\n  position: absolute;\n  left: 6px;\n  top: 2px;\n  width: 6px;\n  height: 11px;\n  border: solid #fff;\n  border-width: 0 2px 2px 0;\n  transform: rotate(45deg) scale(0);\n  transition: transform .15s ease;\n}\n\n#kg-checklist-block .kc-checkbox:checked ~ .kc-box{\n  background: var(--kc-teal);\n  border-color: var(--kc-teal);\n}\n\n#kg-checklist-block .kc-checkbox:checked ~ .kc-box::after{\n  transform: rotate(45deg) scale(1);\n}\n\n#kg-checklist-block .kc-checkbox:focus-visible ~ .kc-box{\n  box-shadow: 0 0 0 3px rgba(0,191,191,0.25);\n}\n\n#kg-checklist-block .kc-item:active .kc-box{\n  transform: scale(0.92);\n}\n\n#kg-checklist-block .kc-text{\n  font-size: 15px;\n  line-height: 1.55;\n  color: var(--kc-ink);\n  padding-top: 1px;\n  transition: color .15s ease, opacity .15s ease;\n}\n\n#kg-checklist-block .kc-checkbox:checked ~ .kc-text{\n  color: var(--kc-muted);\n  text-decoration: line-through;\n  text-decoration-color: var(--kc-border);\n}\n\n#kg-checklist-block .kc-footer{\n  display: flex;\n  align-items: center;\n  justify-content: space-between;\n  gap: 16px;\n  margin-top: 20px;\n  padding-top: 18px;\n  border-top: 1px solid var(--kc-border);\n}\n\n#kg-checklist-block .kc-result{\n  margin: 0;\n  font-size: 13.5px;\n  line-height: 1.5;\n  color: var(--kc-muted);\n  transition: color .2s ease;\n}\n\n#kg-checklist-block .kc-result.kc-result--complete{\n  color: var(--kc-teal-dark);\n  font-weight: 700;\n}\n\n#kg-checklist-block .kc-reset{\n  flex-shrink: 0;\n  border: 1px solid var(--kc-border);\n  background: #fff;\n  color: var(--kc-muted);\n  font-family: inherit;\n  font-size: 13px;\n  font-weight: 600;\n  padding: 8px 14px;\n  border-radius: 8px;\n  cursor: pointer;\n  transition: border-color .15s ease, color .15s ease;\n}\n\n#kg-checklist-block .kc-reset:hover{\n  border-color: var(--kc-teal);\n  color: var(--kc-teal-dark);\n}\n\n@media (max-width: 480px){\n  #kg-checklist-block .kc-card{ padding: 22px 18px 20px; }\n  #kg-checklist-block .kc-title{ font-size: 19px; }\n  #kg-checklist-block .kc-footer{ flex-direction: column; align-items: stretch; text-align: center; }\n}\n<\/style>\n\n<script>\n(function(){\n  var scope = document.getElementById('kg-checklist-block');\n  if(!scope) return;\n  var boxes = scope.querySelectorAll('.kc-checkbox');\n  var fill = scope.querySelector('#kc-progress-fill');\n  var count = scope.querySelector('#kc-progress-count');\n  var total = scope.querySelector('#kc-progress-total');\n  var result = scope.querySelector('#kc-result');\n  var resetBtn = scope.querySelector('#kc-reset');\n  total.textContent = boxes.length;\n\n  function update(){\n    var checked = 0;\n    boxes.forEach(function(b){ if(b.checked) checked++; });\n    count.textContent = checked;\n    fill.style.width = (checked \/ boxes.length * 100) + '%';\n    if(checked === boxes.length){\n      result.textContent = \"You're tracking well ahead of the November 2026 cutover.\";\n      result.classList.add('kc-result--complete');\n    } else {\n      result.textContent = \"Answering no to any of these marks an active legacy system risk.\";\n      result.classList.remove('kc-result--complete');\n    }\n  }\n\n  boxes.forEach(function(b){ b.addEventListener('change', update); });\n  resetBtn.addEventListener('click', function(){\n    boxes.forEach(function(b){ b.checked = false; });\n    update();\n  });\n\n  update();\n})();\n<\/script>\n\n\n\n<p>Answering no to any of these marks an active legacy system risk. A <a href=\"https:\/\/www.kindgeek.com\/software-audit-services\">payment architecture assessment<\/a> is the fastest way to find out which gaps matter before a deadline forces the answer.<\/p>\n\n\n\n<a id=\"section-8\"><\/a>\n\n\n\n<h2 class=\"wp-block-heading\">ISO 20022 Payment Modernization: How Kindgeek Helps Financial Institutions<\/h2>\n\n\n\n<p>Kindgeek works with banks, credit unions, and payment-focused fintechs on the engineering side of ISO 20022 implementation: core banking data models, middleware, and reconciliation workflows.<\/p>\n\n\n\n<p>Payment Architecture Assessment. We review <a href=\"https:\/\/www.kindgeek.com\/digital-banking-software\">core banking platforms<\/a>, payment infrastructure, and middleware against ISO 20022&#8217;s structural requirements to identify where data gets lost between message arrival and storage.<\/p>\n\n\n\n<p>Legacy System Modernization and Middleware Redesign. For institutions running MT-shaped core banking systems, we design middleware and data model changes that preserve party identification, remittance detail, and purpose codes end-to-end, instead of translating them away.<\/p>\n\n\n\n<p>ISO 20022-Ready Payment Infrastructure Development. We build the reconciliation, E&amp;I, and Stop and Recall workflows that turn structured data into automation, reducing the manual case handling that translator-only architectures leave behind.<\/p>\n\n\n\n<p>If your institution is also navigating other 2026\u20132027 regulatory deadlines alongside ISO 20022, with <a href=\"https:\/\/www.kindgeek.com\/blog\/psd3-migration\">PSD3 and PSR compliance<\/a> chief among them in Europe, the same underlying architecture work tends to serve both.<\/p>\n\n\n\n<div style=\"background: linear-gradient(to right, #5FF4F4, #ACF459); border-radius: 16px; padding: 60px 40px; text-align: center; margin-bottom: 20px;\">\n\n  <h2 style=\"margin: 0 0 16px 0;\">Scope a payment architecture assessment before the next deadline<\/h2>\n\n  <p style=\"margin: 0 0 32px 0; max-width: 560px; margin-left: auto; margin-right: auto; line-height: 1.7;\">Our engineers have built payment infrastructure processing billions in transaction volume for regulated financial institutions.\n<\/p>\n\n  <a href=\"https:\/\/www.kindgeek.com\/contact-us\" style=\"display: inline-block; background-color: #0B0B0B; color: #fff; padding: 14px 36px; border-radius: 8px; text-decoration: none;\"><strong>Contact us<\/strong><\/a>\n\n<\/div>\n\n\n\n<a id=\"section-9\"><\/a>\n\n\n\n            <div class=\"qae-faqs-container qae-faqs-toggle-container\">\n\t\t\t\t\t\t\t<ul class=\"qe-faqs-filters-container\">\n\t\t\t\t<li class=\"active\"><a class=\"qe-faqs-filter all-faqs\" href=\"#\" data-filter=\"*\">All<\/a><\/li>\n\t\t\t\t<li><a class=\"qe-faqs-filter\" href=\"#ISO 20022 migration\" data-filter=\".ISO 20022 migration\">ISO 20022 migration<\/a><\/li>\t\t\t<\/ul>\n\t\t\t\t\t<div id=\"qaef-6602\" class=\"qe-faq-toggle iso-20022-migration\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> What is the ISO 20022 deadline banks and credit unions need to prepare for next?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>With the November 2025 SWIFT coexistence end behind us, the next major hard cutover is November 2026. That is when SWIFT completely eliminates unstructured postal addresses in CBPR+ messages, requiring at least a hybrid format (with structured Town Name and Country) or fully structured data. November 2026 also marks the deadline for all institutions to receive camt.110 investigation requests via Case Orchestrator, followed by the full E&amp;I and Stop &amp; Recall mandate in November 2027.<\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div id=\"qaef-6601\" class=\"qe-faq-toggle iso-20022-migration\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> Do credit unions need to comply with ISO 20022, or is this only for large banks?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>Yes. Any credit union that sends or receives wire transfers through Fedwire, or processes cross-border payments through a correspondent bank on SWIFT, is affected. Smaller institutions often depend on a core banking vendor to handle the technical migration, which can add time if that vendor is managing the same deadline across many clients at once.<\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div id=\"qaef-6600\" class=\"qe-faq-toggle iso-20022-migration\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> What&#8217;s the real difference between MT and ISO 20022 messages?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>MT messages use fixed-length, size-restricted text fields: a single unstructured line for an address, for example. ISO 20022 messages use structured XML elements with dedicated fields for each data point, such as street name, building number, and postal code, plus fields for purpose codes and full party identification that MT never had room for.<\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div id=\"qaef-6599\" class=\"qe-faq-toggle iso-20022-migration\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> Is a translator or middleware gateway enough to meet ISO 20022 requirements?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>It passes connectivity testing and meets the first migration deadline&#8217;s basic requirements. The deadlines that follow require rejecting unstructured data on receipt and generating fully structured data on send. A translation layer can only do that if the core system behind it stores the data in structured form.<\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div id=\"qaef-6598\" class=\"qe-faq-toggle iso-20022-migration\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> What happens if a bank or credit union misses an ISO 20022 cutover?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>Payments that don&#8217;t meet the required format are rejected outright. Missing a SWIFT ISO 20022 deadline for cross-border messages carries the same consequence as missing Fedwire&#8217;s domestically. Regulators and correspondent banks increasingly use ISO 20022 data richness to assess AML and sanctions risk, so poor data quality can trigger additional scrutiny or delays on transactions that do go through.<\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t            <\/div>\n\t\t\n","protected":false},"excerpt":{"rendered":"<p>Fedwire, the US domestic wire system, settles more than $4.7 trillion in transfers a day, and as of July 14, 2025, every&#8230;<\/p>\n","protected":false},"author":12,"featured_media":6596,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[348,350,349],"tags":[],"class_list":{"0":"post-6593","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-banking","8":"category-compliance","9":"category-payments"},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.4 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>ISO 20022 Migration: Why Banks Are Running Out of Time | Kindgeek<\/title>\n<meta name=\"description\" content=\"ISO 20022 migration is now mandatory across Fedwire, CHIPS, and SWIFT. See why translator-only compliance fails at scale, and what banks need to build instead.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"ISO 20022 Migration: Why Banks Are Running Out of Time | Kindgeek\" \/>\n<meta property=\"og:description\" content=\"ISO 20022 migration is now mandatory across Fedwire, CHIPS, and SWIFT. See why translator-only compliance fails at scale, and what banks need to build instead.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration\" \/>\n<meta property=\"og:site_name\" content=\"Kindgeek\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-18T23:08:24+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-18T23:11:37+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/08\/Content-picture-16.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Viktoriia Pyvovar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Viktoriia Pyvovar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"ISO 20022 Migration: Why Banks Are Running Out of Time | Kindgeek","description":"ISO 20022 migration is now mandatory across Fedwire, CHIPS, and SWIFT. See why translator-only compliance fails at scale, and what banks need to build instead.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration","og_locale":"en_US","og_type":"article","og_title":"ISO 20022 Migration: Why Banks Are Running Out of Time | Kindgeek","og_description":"ISO 20022 migration is now mandatory across Fedwire, CHIPS, and SWIFT. See why translator-only compliance fails at scale, and what banks need to build instead.","og_url":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration","og_site_name":"Kindgeek","article_published_time":"2026-08-18T23:08:24+00:00","article_modified_time":"2026-08-18T23:11:37+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/08\/Content-picture-16.png","type":"image\/png"}],"author":"Viktoriia Pyvovar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Viktoriia Pyvovar","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration#article","isPartOf":{"@id":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration"},"author":{"name":"Viktoriia Pyvovar","@id":"https:\/\/www.kindgeek.com\/blog\/#\/schema\/person\/b3a00b8b522b0ad9c2b65066a14367fd"},"headline":"Why Banks and Credit Unions Are Running Out of Time on ISO 20022","datePublished":"2026-08-18T23:08:24+00:00","dateModified":"2026-08-18T23:11:37+00:00","mainEntityOfPage":{"@id":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration"},"wordCount":2094,"publisher":{"@id":"https:\/\/www.kindgeek.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration#primaryimage"},"thumbnailUrl":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/08\/Content-picture-16.png","articleSection":["Banking","Compliance","Payments"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration","url":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration","name":"ISO 20022 Migration: Why Banks Are Running Out of Time | Kindgeek","isPartOf":{"@id":"https:\/\/www.kindgeek.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration#primaryimage"},"image":{"@id":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration#primaryimage"},"thumbnailUrl":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/08\/Content-picture-16.png","datePublished":"2026-08-18T23:08:24+00:00","dateModified":"2026-08-18T23:11:37+00:00","description":"ISO 20022 migration is now mandatory across Fedwire, CHIPS, and SWIFT. See why translator-only compliance fails at scale, and what banks need to build instead.","breadcrumb":{"@id":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.kindgeek.com\/blog\/iso-20022-migration"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration#primaryimage","url":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/08\/Content-picture-16.png","contentUrl":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/08\/Content-picture-16.png","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.kindgeek.com\/blog\/iso-20022-migration#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.kindgeek.com\/blog"},{"@type":"ListItem","position":2,"name":"Why Banks and Credit Unions Are Running Out of Time on ISO 20022"}]},{"@type":"WebSite","@id":"https:\/\/www.kindgeek.com\/blog\/#website","url":"https:\/\/www.kindgeek.com\/blog\/","name":"Kindgeek","description":"Blog | Kindgeek","publisher":{"@id":"https:\/\/www.kindgeek.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.kindgeek.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.kindgeek.com\/blog\/#organization","name":"Kindgeek","url":"https:\/\/www.kindgeek.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.kindgeek.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/kindgeek.com\/blog\/wp-content\/uploads\/2026\/02\/kg-logo-updated.png","contentUrl":"https:\/\/kindgeek.com\/blog\/wp-content\/uploads\/2026\/02\/kg-logo-updated.png","width":300,"height":60,"caption":"Kindgeek"},"image":{"@id":"https:\/\/www.kindgeek.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.kindgeek.com\/blog\/#\/schema\/person\/b3a00b8b522b0ad9c2b65066a14367fd","name":"Viktoriia Pyvovar","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.kindgeek.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2025\/09\/Screenshot-from-2025-09-22-11-52-54-150x150.png","contentUrl":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2025\/09\/Screenshot-from-2025-09-22-11-52-54-150x150.png","caption":"Viktoriia Pyvovar"},"description":"Content Producer at Kindgeek","url":"https:\/\/www.kindgeek.com\/blog\/author\/viktoriia-pyvovar"}]}},"_links":{"self":[{"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/posts\/6593","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/comments?post=6593"}],"version-history":[{"count":2,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/posts\/6593\/revisions"}],"predecessor-version":[{"id":6597,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/posts\/6593\/revisions\/6597"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/media\/6596"}],"wp:attachment":[{"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/media?parent=6593"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/categories?post=6593"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/tags?post=6593"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}