[{"data":1,"prerenderedAt":624},["ShallowReactive",2],{"site-schema":3,"article-zh-tw-financial-system-development-guide":106,"article-related-zh-tw-financial-system-development-guide":610},{"@context":4,"@graph":5},"https:\u002F\u002Fschema.org",[6,85,97],{"@type":7,"@id":8,"name":9,"alternateName":10,"description":17,"knowsAbout":18,"legalName":27,"foundingDate":28,"numberOfEmployees":29,"taxID":30,"url":31,"logo":32,"founder":33,"contactPoint":35,"address":49,"location":55,"sameAs":75},"Organization","https:\u002F\u002Fjoinx.co\u002F#organization","JoinX哲煜科技",[11,12,13,14,15,16],"JoinX","TWJOIN","哲煜科技","哲煜科技股份有限公司","TWJOIN 哲煜科技","twjoin.com","JoinX 哲煜科技（原品牌名 TWJOIN）是 2016 年在台北成立的軟體開發公司，80+ 人自有團隊，承接客製系統、APP、AI 導入與 IoT 開發，以及軟體外包與既有系統接手維運，服務 220+ 客戶、完成 520+ 專案。",[19,20,21,22,23,24,25,26],"軟體外包","客製化系統開發","APP 開發","AI 導入","AI Agent 開發","IoT APP 開發","ERP 系統整合","既有系統接手維運","JoinX Co., Ltd.","2016-04-28",80,"43774383","https:\u002F\u002Fjoinx.co","https:\u002F\u002Fjoinx.co\u002Fimages\u002Flogo-with-name.png",{"@id":34},"https:\u002F\u002Fjoinx.co\u002F#person-jack-lee",[36],{"@type":37,"contactType":38,"url":39,"telephone":40,"email":41,"areaServed":42,"availableLanguage":45},"ContactPoint","customer service","https:\u002F\u002Fjoinx.co\u002Fcontact-us","+886-2-8771-9095","service@joinx.co",[43,44],"TW","JP",[46,47,48],"zh-Hant","en","ja",{"@type":50,"streetAddress":51,"postalCode":52,"addressLocality":53,"addressRegion":54,"addressCountry":43},"PostalAddress","民生東路二段170號8樓","104","台北市中山區","台灣",[56,63,69],{"@type":57,"name":58,"address":59},"Place","JoinX 台中辦公室",{"@type":50,"streetAddress":60,"postalCode":61,"addressLocality":62,"addressRegion":54,"addressCountry":43},"台灣大道二段360號21樓C室","40453","台中市北區",{"@type":57,"name":64,"address":65},"JoinX 高雄辦公室",{"@type":50,"streetAddress":66,"postalCode":67,"addressLocality":68,"addressRegion":54,"addressCountry":43},"民族一路80號2樓之一","807","高雄市三民區",{"@type":57,"name":70,"address":71},"JoinX 東京辦公室",{"@type":50,"streetAddress":72,"postalCode":73,"addressLocality":74,"addressCountry":44},"東五反田5-22-37 Office Circle N 五反田 9樓","141-0022","東京都品川區",[76,77,78,79,80,81,82,83,84],"https:\u002F\u002Fwww.crunchbase.com\u002Forganization\u002Ftwjoin","https:\u002F\u002Fwww.facebook.com\u002FJoinX.TW","https:\u002F\u002Ftw.linkedin.com\u002Fcompany\u002F%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fwww.youtube.com\u002Fc\u002Fjoinstuido%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fmedium.com\u002Ftwjoin","https:\u002F\u002Fwww.104.com.tw\u002Fcompany\u002F1a2x6bjomb","https:\u002F\u002Fclutch.co\u002Fprofile\u002Fjoinx","https:\u002F\u002Fwww.goodfirms.co\u002Fcompany\u002Ftwjoin","https:\u002F\u002Ftwjoin.com",{"@type":86,"@id":34,"name":87,"alternateName":88,"jobTitle":89,"worksFor":90,"url":91,"sameAs":92},"Person","李秉哲","Jack Lee","創辦人暨執行長",{"@id":8},"https:\u002F\u002Fjack88.joinx.co\u002F",[93,94,95,96],"https:\u002F\u002Fwww.instagram.com\u002Fjack88.podcast\u002F","https:\u002F\u002Fwww.threads.net\u002F@jack88.podcast","https:\u002F\u002Fjoinx.co\u002Fjack88\u002F","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fjacklee-taiwan\u002F",{"@type":98,"@id":99,"url":31,"name":9,"alternateName":100,"publisher":101,"inLanguage":102},"WebSite","https:\u002F\u002Fjoinx.co\u002F#website",[11,13,9],{"@id":8},[103,104,105],"zh-Hant-TW","en-US","ja-JP",{"id":107,"title":108,"body":109,"category":579,"cover":580,"dateModified":581,"description":582,"extension":583,"faq":581,"hasCoverTitle":584,"locale":585,"meta":586,"navigation":587,"need":588,"path":589,"seo":590,"seoDescription":581,"seoTitle":581,"sources":591,"stem":600,"takeaways":601,"time":607,"type":608,"__hash__":609},"content\u002Fzh-tw\u002Farticle\u002Ffinancial-system-development-guide.md","金融業系統委外開發怎麼選？投信、銀行的資訊委外規範與廠商檢核重點",{"type":110,"value":111,"toc":561},"minimark",[112,120,125,128,206,209,213,216,266,275,279,282,365,368,372,375,415,422,425,429,432,435,447,451,454,515,522,525,530,533,537,540,544,547,551,554,558],[113,114,115,119],"p",{},[116,117,118],"strong",{},"金融業系統委外，買的不只是程式，而是一個能一起通過稽核的團隊。"," 銀行、投信、證券的官網、APP 與作業系統，每天都有客戶在用，也都受金管會的委外與資安規範約束。系統可以委外開發，但監督責任不會跟著移轉。下面整理金融機構委外前要知道的規範、常見系統類型，以及選廠商時要逐項確認的事。",[121,122,124],"h2",{"id":123},"金融業系統委外開發和一般企業有什麼不同","金融業系統委外開發和一般企業有什麼不同？",[113,126,127],{},"最大的差別是責任不會跟著委外移轉：金融機構仍要能監督廠商、取得稽核資料、確保客戶資料受保護。所以除了功能與時程，合約、資安檢測、文件與交接方式，都要在委外前就談清楚。",[129,130,131,147],"table",{},[132,133,134],"thead",{},[135,136,137,141,144],"tr",{},[138,139,140],"th",{},"項目",[138,142,143],{},"一般企業委外",[138,145,146],{},"金融機構委外",[148,149,150,162,173,184,195],"tbody",{},[135,151,152,156,159],{},[153,154,155],"td",{},"合約重點",[153,157,158],{},"功能範圍、時程、保固",[153,160,161],{},"另外要寫明資料保護、查核權、客戶權益保障與退場交接",[135,163,164,167,170],{},[153,165,166],{},"資安檢測",[153,168,169],{},"依公司政策，常在上線前做一次",[153,171,172],{},"上線前與定期都要檢測，發現的問題要逐項修正並留存佐證",[135,174,175,178,181],{},[153,176,177],{},"資料存放位置",[153,179,180],{},"依成本與效能決定",[153,182,183],{},"要確認存放地點與跨境傳輸是否符合規範",[135,185,186,189,192],{},[153,187,188],{},"文件",[153,190,191],{},"操作手冊為主",[153,193,194],{},"系統架構、程式與變更紀錄都要能提供給稽核",[135,196,197,200,203],{},[153,198,199],{},"換廠商",[153,201,202],{},"重新交接即可",[153,204,205],{},"要事先約定停止合作時的系統與資料移轉方式，服務不能中斷",[113,207,208],{},"這些要求聽起來是金融機構自己的事，但實際上大多要靠廠商配合產出：檢測報告的修正紀錄、變更的程式版本、交接用的環境說明，都是開發團隊手上的東西。",[121,210,212],{"id":211},"金融機構資訊委外要遵守哪些規範","金融機構資訊委外要遵守哪些規範？",[113,214,215],{},"銀行主要依金管會「金融機構作業委託他人處理內部作業制度及程序辦法」，證券期貨業者依各服務事業的內控處理準則與委外應注意事項。兩者都要求以風險為基礎管理委外，並保留主管機關與金融機構的查核權。",[129,217,218,231],{},[132,219,220],{},[135,221,222,225,228],{},[138,223,224],{},"規範",[138,226,227],{},"適用對象",[138,229,230],{},"對委外專案的影響",[148,232,233,244,255],{},[135,234,235,238,241],{},[153,236,237],{},"金融機構作業委託他人處理內部作業制度及程序辦法",[153,239,240],{},"銀行等金融機構",[153,242,243],{},"委外範圍要訂在內部作業規範裡；依委外的重大性與是否委託到境外，決定是否要事先向主管機關申請；使用雲端服務也納入規範",[135,245,246,249,252],{},[153,247,248],{},"證券暨期貨市場各服務事業建立內部控制制度處理準則",[153,250,251],{},"證券商、期貨商、投信投顧等服務事業",[153,253,254],{},"2023 年 8 月修正，新增「作業委託他人處理之管理」內控項目；證券商與期貨商另有委外應注意事項，資訊系統的開發與維護屬於可委外的範圍",[135,256,257,260,263],{},[153,258,259],{},"金融資安行動方案 2.0",[153,261,262],{},"金融業",[153,264,265],{},"強化資安治理與供應鏈風險管理，APP、雲端、Open API 等都是關注重點",[113,267,268,269,274],{},"實務上，這些規範會轉成委外合約的條款與專案文件。條文會隨主管機關修正而調整，委外前請以金管會公布的現行版本，以及公司內部的委外作業規範為準。生成式 AI 專案另有金管會的 AI 指引要對照，可以參考",[270,271,273],"a",{"href":272},"\u002Farticle\u002Ffinancial-industry-ai-adoption-guide\u002F","金融業 AI 導入","。",[121,276,278],{"id":277},"投信銀行常委外開發哪些系統","投信、銀行常委外開發哪些系統？",[113,280,281],{},"最常見的是面對客戶的官網與 APP、線上開戶與交易流程，以及銀行內部的作業系統。前兩類重視資訊正確與資安檢測，作業系統重視帳務正確與流程控管，評估重點不一樣。",[129,283,284,297],{},[132,285,286],{},[135,287,288,291,294],{},[138,289,290],{},"系統類型",[138,292,293],{},"常見內容",[138,295,296],{},"開發時要特別注意",[148,298,299,310,321,332,343,354],{},[135,300,301,304,307],{},[153,302,303],{},"官網與商品網站",[153,305,306],{},"基金與 ETF 資訊、淨值、配息、公告",[153,308,309],{},"數字要和資料源一致，更新時間要清楚",[135,311,312,315,318],{},[153,313,314],{},"線上開戶與身分驗證",[153,316,317],{},"開戶流程、KYC、電子化申請",[153,319,320],{},"個資保護、身分驗證流程與留存紀錄",[135,322,323,326,329],{},[153,324,325],{},"交易與申購",[153,327,328],{},"申購、買回、轉申購",[153,330,331],{},"每一步的狀態與錯誤處理，不能重複扣款或漏單",[135,333,334,337,340],{},[153,335,336],{},"金融 APP",[153,338,339],{},"iOS、Android 雙平台",[153,341,342],{},"定期資安檢測，修正後要再上架，兩個平台要同步",[135,344,345,348,351],{},[153,346,347],{},"銀行作業系統",[153,349,350],{},"支票套印、紅利點數、抽獎、送達證明",[153,352,353],{},"帳務每一筆都要算對，紀錄要能查核與追溯",[135,355,356,359,362],{},[153,357,358],{},"支付與點數介接",[153,360,361],{},"電子支付、點數兌換與核銷",[153,363,364],{},"對帳機制、異常交易處理與介接廠商的規格",[113,366,367],{},"APP 的資安檢測可以參考 OWASP 的行動應用安全驗證標準（MASVS），檢測發現的中、高風險問題要修正後才能上線。",[121,369,371],{"id":370},"選金融系統委外廠商要確認哪些事","選金融系統委外廠商要確認哪些事？",[113,373,374],{},"先確認對方能不能配合稽核與資安檢測，再看技術能力。可以直接請廠商說明過去配合金融業稽核的經驗、交付時會給哪些文件，以及停止合作時怎麼交接。",[376,377,378,385,391,397,403,409],"ol",{},[379,380,381,384],"li",{},[116,382,383],{},"金融業委外實績。"," 問做過哪些金融機構、是新建還是接手、合作多久，以及有沒有可以公開的案例。",[379,386,387,390],{},[116,388,389],{},"資安檢測怎麼做。"," 交付前是否自行做原碼掃描與弱點掃描；黑箱測試由誰執行；檢測發現的問題多久修正、怎麼留存佐證。",[379,392,393,396],{},[116,394,395],{},"原始碼與文件的交付。"," 原始碼、建置方式、主機環境與技術文件是否完整交付，版本與變更紀錄怎麼保存。",[379,398,399,402],{},[116,400,401],{},"資料放在哪裡。"," 開發、測試與正式環境的資料位置，測試時是否用到真實客戶資料。",[379,404,405,408],{},[116,406,407],{},"人員與權限。"," 誰能碰正式環境、帳號怎麼控管、人員異動時怎麼處理。",[379,410,411,414],{},[116,412,413],{},"停止合作時的安排。"," 系統、資料與文件怎麼移交，交接期間由誰維持服務。",[113,416,417,418,274],{},"報價也要看清楚範圍：資安檢測的修正、稽核文件的準備，以及上架與維運，有沒有包含在內。費用的估算方式可以參考",[270,419,421],{"href":420},"\u002Fsoftware-development-cost-guide\u002F","軟體開發費用指南",[423,424],"article-cta",{},[121,426,428],{"id":427},"接手別人寫的金融系統要注意什麼","接手別人寫的金融系統要注意什麼？",[113,430,431],{},"先求穩定，再求改版：盤點原始碼、主機環境與商店帳號，確認每個環節都能維護，再處理資安檢測發現的問題，最後才加新功能。金融系統每天都有客戶在用，不能先停下來重寫。",[113,433,434],{},"接手時常見的問題是：原始碼和正式環境的版本對不上、APP 的商店帳號在前一個廠商手上、主機與網域的權限沒有完整移交、沒有文件說明資料表的用途。這些都要在交接期間逐項確認，並留下紀錄給稽核。",[113,436,437,438,442,443,274],{},"群益投信的官網、APP 與電商系統原本由其他團隊開發，JoinX 在 2023 年接手後，先盤點原始碼、主機環境與商店帳號，讓系統穩定運作，再修正 APP 資安檢測發現的問題，並依金管會規範完成資安調整與稽核。之後才陸續重製 ETF 官網、優化線上開戶與 ETF 電子化申請，並串接全支付。詳見",[270,439,441],{"href":440},"\u002Fcase-studies\u002Fcapital\u002F","群益投信案例","。一般 APP 的接手做法，也可以參考",[270,444,446],{"href":445},"\u002Farticle\u002Fapp-revamp-takeover-guide\u002F","APP 改版與接手",[121,448,450],{"id":449},"joinx-做過哪些金融系統","JoinX 做過哪些金融系統？",[113,452,453],{},"JoinX 為投信、銀行、證券與金融基礎設施開發與維運系統。群益投信對 JoinX 的定位是「符合金管會要求標準的資訊委外開發廠商」，官網、ETF 網站與 APP 都由 JoinX 維護。",[455,456,457,465,475,485,491,497,503,509],"ul",{},[379,458,459,462,463,274],{},[116,460,461],{},"群益投信："," 官網、ETF 網站與 APP 的委外開發與維運，2023 年接手至今。詳見",[270,464,441],{"href":440},[379,466,467,470,471,274],{},[116,468,469],{},"彰化銀行："," 支票套印、信用卡紅利點數與抽獎三套系統，Web 系統以 Laravel 與 AngularJS 開發，另有 Windows 桌面應用程式。詳見",[270,472,474],{"href":473},"\u002Fcase-studies\u002Fchb\u002F","彰化銀行案例",[379,476,477,480,481,274],{},[116,478,479],{},"台北富邦銀行："," 數位送達證明系統，2026 年 4 月開始開發，以紀錄完整、可追溯為前提。詳見",[270,482,484],{"href":483},"\u002Fcase-studies\u002Ftaipei-fubon\u002F","台北富邦銀行案例",[379,486,487,490],{},[116,488,489],{},"財金資訊："," ISO 20022 快捷支付閘道試驗，涵蓋 13 種轉帳情境。",[379,492,493,496],{},[116,494,495],{},"凱基證券："," 投資教育平台，包含課程、直播、任務積分與 CRM 串接。",[379,498,499,502],{},[116,500,501],{},"復華投信："," ETF 效率投資網站。",[379,504,505,508],{},[116,506,507],{},"某銀行："," 點數介接、消費支付與核銷。",[379,510,511,514],{},[116,512,513],{},"某投信："," 系統後端開發，前端由其他設計公司負責。",[113,516,517,518,274],{},"交付前，JoinX 會自行完成原碼掃描與弱點掃描；黑箱測試由第三方執行，JoinX 可以協助聯繫，並在修補弱點後交付。開發流程採 SDD 加 TDD，需求、規格與測試都留有紀錄，稽核時可以提供。更多金融系統的做法見",[270,519,521],{"href":520},"\u002Ffintech\u002F","金融科技系統開發",[121,523,524],{"id":524},"常見問題",[526,527,529],"h3",{"id":528},"什麼是資訊委外","什麼是資訊委外？",[113,531,532],{},"資訊委外是金融機構把資訊系統的開發、維護或資料處理交給外部廠商執行。金融業的資訊委外受金管會規範，金融機構要訂定內部委外作業規範、評估委外風險，並在合約中保留查核權與資料保護條款，責任不會因為委外而移轉給廠商。",[526,534,536],{"id":535},"金融系統可以放在雲端嗎","金融系統可以放在雲端嗎？",[113,538,539],{},"可以，但要符合委外規範。金管會已把雲端服務納入委外管理，並依委外的重大性與是否委託到境外，區分要不要事先申請。實際能不能用、要走什麼程序，要依金融機構的業別、系統的重要程度與現行條文判斷，建議在架構規劃階段就讓資安與法遵單位一起確認。",[526,541,543],{"id":542},"金融-app-的資安檢測由誰做","金融 APP 的資安檢測由誰做？",[113,545,546],{},"通常分成兩部分：開發團隊在交付前自行做原碼掃描與弱點掃描，黑箱滲透測試則由第三方檢測機構執行。以 JoinX 為例，白箱掃描由我們自行完成；黑箱測試委由第三方，我們可以協助聯繫，並依檢測結果修補後交付。",[526,548,550],{"id":549},"換掉原本的系統廠商服務會中斷嗎","換掉原本的系統廠商，服務會中斷嗎？",[113,552,553],{},"規劃得當就不需要中斷。關鍵是交接期間由新舊團隊重疊一段時間，先確認原始碼、主機環境、網域與 APP 商店帳號都移交完成，新團隊能自行部署之後，再由新團隊接手維運。合約裡最好事先約定停止合作時的交接義務。",[526,555,557],{"id":556},"不是金管會監理的金融相關業者也要照這些規範做嗎","不是金管會監理的金融相關業者，也要照這些規範做嗎？",[113,559,560],{},"不一定直接適用。分期、理財顧問、支付服務等業者是否受這些辦法規範，要看業別與執照。不過這類業者常要和銀行或投信合作，對方通常會要求同等的資安與委外標準，所以開發時照金融業的做法規劃，日後串接與稽核會比較順利。",{"title":562,"searchDepth":563,"depth":563,"links":564},"",2,[565,566,567,568,569,570,571],{"id":123,"depth":563,"text":124},{"id":211,"depth":563,"text":212},{"id":277,"depth":563,"text":278},{"id":370,"depth":563,"text":371},{"id":427,"depth":563,"text":428},{"id":449,"depth":563,"text":450},{"id":524,"depth":563,"text":524,"children":572},[573,575,576,577,578],{"id":528,"depth":574,"text":529},3,{"id":535,"depth":574,"text":536},{"id":542,"depth":574,"text":543},{"id":549,"depth":574,"text":550},{"id":556,"depth":574,"text":557},"技術分享","\u002Fimages\u002Fblog\u002Ffinancial-system-development-guide.webp",null,"金融業系統委外開發和一般企業最大的不同，是合規責任不會跟著委外移轉：金融機構仍要能監督廠商、取得稽核資料，並確保停止合作時系統與資料能順利交接。選廠商時，除了技術能力，更要看對方能不能配合稽核與資安檢測、交付原始碼與文件，以及有沒有接手既有金融系統的經驗。本文整理銀行與投信適用的委外規範、常見系統類型與選廠商的檢核清單。","md",false,"zh-tw",{},true,"客製化系統","\u002Fzh-tw\u002Farticle\u002Ffinancial-system-development-guide",{"title":108,"description":582},[592,594,596,597],{"name":237,"issuer":593},"金融監督管理委員會",{"name":595,"issuer":593},"證券暨期貨市場各服務事業建立內部控制制度處理準則（2023 年 8 月修正）",{"name":259,"issuer":593},{"name":598,"issuer":599},"OWASP Mobile Application Security Verification Standard（MASVS）","OWASP Foundation","zh-tw\u002Farticle\u002Ffinancial-system-development-guide",[602,603,604,605,606],"金融機構把系統委外開發或維運，合規與監督責任仍在金融機構身上，廠商要能配合稽核、資安檢測與文件要求。","銀行委外適用金管會「金融機構作業委託他人處理內部作業制度及程序辦法」；證券期貨業者的內控處理準則在 2023 年 8 月修正，新增作業委託他人處理的管理項目。","委外合約要寫清楚委外範圍、資料保護、主管機關與金融機構的查核權，以及停止合作時的交接與資料返還方式。","選金融系統廠商，要確認對方有金融業委外實績、交付前會做原碼與弱點掃描，並能交付原始碼、環境與技術文件。","接手既有金融系統時，要先盤點原始碼、主機環境與商店帳號，讓服務穩定運作後再改版，不能先停下來重寫。","2026\u002F11\u002F06","blog","hHZDBzXiJ4EJ-6kIpQ3qNqgLzAE75VDxFMmB8UKT93E",[611,616,620],{"slug":612,"title":613,"time":614,"cover":615,"need":588},"admin-backoffice-system-development","後台管理系統開發：模組、權限、費用與驗收","2026\u002F11\u002F04","\u002Fimages\u002Fblog\u002Fadmin-backoffice-system-development.webp",{"slug":617,"title":618,"time":614,"cover":619,"need":588},"custom-system-development-types-cost-cases","客製化系統開發：適合誰、有哪些類型、費用與台灣案例","\u002Fimages\u002Fblog\u002Fcustom-system-development-types-cost-cases.webp",{"slug":621,"title":622,"time":614,"cover":623,"need":588},"education-retail-system-development-cases","教育與零售系統開發案例：酷課雲、工研院直播課程平台、比漾百貨電商","\u002Fimages\u002Fblog\u002Feducation-retail-system-development-cases.webp",1794558639718]