[{"data":1,"prerenderedAt":102},["ShallowReactive",2],{"insights-id-en":3},[4,48,79],{"id":5,"title":6,"body":7,"category":37,"date":38,"description":31,"extension":39,"locale":40,"meta":41,"navigation":42,"path":43,"seo":44,"stem":45,"summary":46,"__hash__":47},"insights\u002Finsights\u002Fen\u002Fplatform-update.md","Platform and API contract updates",{"type":8,"value":9,"toc":30},"minimark",[10,15,19,23],[11,12,14],"h2",{"id":13},"reviewable-contracts","Reviewable contracts",[16,17,18],"p",{},"Merchant OpenAPI specifications are built from dedicated public endpoint groups, stripped of internal routes, and stored as reviewable snapshots. Stable versions remain immutable after publication.",[11,20,22],{"id":21},"safe-environments","Safe environments",[16,24,25,29],{},[26,27,28],"strong",{},"Try It"," can send requests only to approved Sandbox origins. Credentials remain in page memory.",{"title":31,"searchDepth":32,"depth":32,"links":33},"",3,[34,36],{"id":13,"depth":35,"text":14},2,{"id":21,"depth":35,"text":22},"announcement","2026-10-01","md","en",{},true,"\u002Fen\u002Finsights\u002Fplatform-update",{"title":6,"description":31},"insights\u002Fen\u002Fplatform-update","How the platform publishes reviewed, versioned changes to merchant API contracts.","6s7-0C9Rd5soaa9I9z4jxutjSk5GoGH5rdWW5ged11A",{"id":49,"title":50,"body":51,"category":71,"date":72,"description":31,"extension":39,"locale":40,"meta":73,"navigation":42,"path":74,"seo":75,"stem":76,"summary":77,"__hash__":78},"insights\u002Finsights\u002Fen\u002Fintegration-basics.md","Merchant integration basics",{"type":8,"value":52,"toc":67},[53,57,60,64],[11,54,56],{"id":55},"start-with-idempotency","Start with idempotency",[16,58,59],{},"Use a unique business number and retain the platform trade number. Retries must use the same request parameters.",[11,61,63],{"id":62},"verify-callbacks","Verify callbacks",[16,65,66],{},"Always verify signatures, process repeated events idempotently, and query status when a network result is unknown.",{"title":31,"searchDepth":32,"depth":32,"links":68},[69,70],{"id":55,"depth":35,"text":56},{"id":62,"depth":35,"text":63},"integration-guide","2026-09-25",{},"\u002Fen\u002Finsights\u002Fintegration-basics",{"title":50,"description":31},"insights\u002Fen\u002Fintegration-basics","Prepare idempotency, signatures, callbacks, and reconciliation before the first transaction.","x4UNDVgmQcgls9hCEftzuu8hg8xd_sgEs1XcUAEeFVA",{"id":80,"title":81,"body":82,"category":94,"date":95,"description":31,"extension":39,"locale":40,"meta":96,"navigation":42,"path":97,"seo":98,"stem":99,"summary":100,"__hash__":101},"insights\u002Finsights\u002Fen\u002Freconciliation-control.md","Reconciliation as an operational control",{"type":8,"value":83,"toc":91},[84,88],[11,85,87],{"id":86},"separate-the-facts","Separate the facts",[16,89,90],{},"Transaction state, ledger journals, settlement batches, and channel reports have distinct responsibilities. Reconciliation connects them without rewriting history.",{"title":31,"searchDepth":32,"depth":32,"links":92},[93],{"id":86,"depth":35,"text":87},"industry-insight","2026-09-18",{},"\u002Fen\u002Finsights\u002Freconciliation-control",{"title":81,"description":31},"insights\u002Fen\u002Freconciliation-control","Separate payment, ledger, settlement, and channel-report facts so discrepancies remain traceable.","Nwsc8ZdiZLs-gwYHIyju-fU3b51cW3u0trbwVsSV170",1792929326015]