[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F8A8ADQVDEXBREZ5K1STCV":3,"skill-same:01M7F8A8ADQVDEXBREZ5K1STCV":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M7F8A8ADQVDEXBREZ5K1STCV","managing-cross-border-payment-analysis",null,"Structures cross-border payment evaluation with corridor analysis, pricing, and regulatory requirements. Use when analyzing cross-border payments, evaluating remittance services, or assessing international payment solutions.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fmanaging-cross-border-payment-analysis\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: managing-cross-border-payment-analysis\nlanguage: en\ndescription: Structures cross-border payment evaluation with corridor analysis, pricing, and regulatory requirements. Use when analyzing cross-border payments, evaluating remittance services, or assessing international payment solutions.\ntags:\n  - management\n  - financial-technology\n  - regulatory\n  - valuation\nmetadata:\n  author: casemark\n  practice_areas:\n    - Fintech\n    - Payments\n    - Digital Banking\n  document_types:\n    - Management Report\n  skill_modes:\n    - Management\n    - Coordination\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Ffinance\u002Fmanaging-cross-border-payment-analysis\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Managing Cross Border Payment Analysis\n\nStructures cross-border payment evaluation with corridor analysis, pricing, and regulatory requirements.\n\n## When To Use\n\n- Evaluating a new cross-border payment corridor for product launch or expansion\n- Benchmarking remittance pricing against competitors for a specific send\u002Freceive pair\n- Assessing regulatory feasibility of entering a new market or partnering with a local payout provider\n- Reviewing an existing corridor's economics (FX spread, fees, settlement costs) for margin optimization\n- Performing due diligence on an international payment provider or correspondent banking relationship\n\n## Inputs To Gather\n\n- **Corridor definition**: Send country, receive country, currency pair (e.g., USD→PHP), estimated monthly volume and average transaction size\n- **Customer segment**: Consumer remittance, SMB trade payments, enterprise treasury, or marketplace payouts\n- **Current pricing data**: Competitor fee schedules, published FX rates, and any available interchange or scheme fees\n- **Regulatory landscape**: Licenses held or required in send and receive jurisdictions [VERIFY per jurisdiction]\n- **Settlement infrastructure**: Correspondent bank relationships, local payment rails (ACH, RTGS, mobile money), and payout network coverage\n- **Risk parameters**: Sanctions screening obligations, fraud rates on corridor, chargeback exposure, and AML typologies specific to the corridor\n\n## Workflow\n\n1. **Define corridor scope**\n   - Specify origin\u002Fdestination countries, currency pair, and directionality (one-way vs. bidirectional)\n   - Identify customer segment and use case (remittance, B2B invoice, payroll, marketplace settlement)\n   - Set volume assumptions: projected monthly transactions, average ticket size, peak\u002Ftrough seasonality\n\n2. **Map regulatory requirements**\n   - Identify required licenses in the send jurisdiction (e.g., state MTLs in the US, EMI in EU, PSP license in UK) [VERIFY]\n   - Identify required licenses or partnerships in the receive jurisdiction (e.g., authorized dealer bank, mobile money operator approval) [VERIFY]\n   - Document sanctions and restricted-party screening obligations (OFAC, EU consolidated list, UN sanctions) [VERIFY]\n   - Note data localization, reporting thresholds (e.g., CTR at $10K USD equivalent), and consumer disclosure rules [VERIFY]\n\n3. **Analyze pricing and economics**\n   - Break down total cost to customer: upfront fee + FX markup + any intermediary charges\n   - Benchmark against at least three competitors on the same corridor using published rates or mystery-shop data\n   - Calculate unit economics per transaction: revenue (fee + FX spread) minus direct costs (scheme fees, correspondent charges, payout partner fees, compliance cost allocation)\n   - Model margin sensitivity to FX volatility — flag corridors where spread exceeds 150 bps or where local currency is illiquid\n\n4. **Evaluate settlement and payout infrastructure**\n   - Map available payout methods: bank deposit, mobile wallet, cash pickup, card credit\n   - Assess settlement speed: same-day, T+1, T+2 — and identify bottlenecks (cut-off times, correspondent bank processing windows)\n   - Evaluate pre-funding requirements and float implications on working capital\n   - Identify single points of failure (sole correspondent bank, single payout aggregator)\n\n5. **Assess operational and compliance risk**\n   - Score corridor on AML risk (high\u002Fmedium\u002Flow) based on FATF mutual evaluation, Transparency International CPI, and historical SARs filing rates\n   - Identify fraud typologies prevalent on the corridor (identity fraud, mule networks, structuring)\n   - Review partner due diligence: KYC\u002FKYB on payout agents, ongoing monitoring cadence, contractual audit rights\n   - Flag any pending regulatory changes that could affect corridor viability [VERIFY]\n\n6. **Compile corridor assessment report**\n   - Summarize go\u002Fno-go recommendation with supporting rationale\n   - Present pricing comparison table, unit economics model, and sensitivity analysis\n   - Include regulatory checklist with license status and timeline to compliance\n   - Outline implementation roadmap: partner onboarding, technical integration, testing, and launch milestones\n\n## Output\n\nThe deliverable is a **Cross-Border Payment Corridor Assessment Report** containing:\n\n- **Executive summary**: Corridor viability rating (green\u002Famber\u002Fred), key economics, and recommended action\n- **Regulatory matrix**: License-by-license status table for send and receive jurisdictions with estimated timelines\n- **Pricing benchmark**: Side-by-side comparison of total cost to customer across competitors\n- **Unit economics model**: Per-transaction P&L with assumptions clearly stated\n- **Settlement architecture diagram**: Flow of funds from send to receive, with intermediaries, cut-off times, and pre-funding nodes\n- **Risk scorecard**: AML risk tier, fraud exposure estimate, and operational concentration risk\n- **Implementation roadmap**: Phased plan with dependencies, milestones, and estimated launch date\n\n## Quality Checks\n\n- All regulatory requirements are jurisdiction-specific and tagged [VERIFY] where statutes, thresholds, or license names may change\n- Pricing benchmarks use data no older than 90 days; any stale data is flagged\n- Unit economics model includes all cost layers — no hidden costs omitted (nostro\u002Fvostro charges, FX hedging costs, compliance overhead)\n- Settlement flow accounts for weekends, holidays, and cut-off times in both jurisdictions\n- Sanctions and AML obligations reference the correct regime for each jurisdiction, not generic global statements\n- Competitor analysis compares like-for-like (same send amount, same payout method) rather than headline rates\n- Report clearly distinguishes confirmed data from estimates or assumptions\n","# Managing Cross Border Payment Analysis\n\nStructures cross-border payment evaluation with corridor analysis, pricing, and regulatory requirements.\n\n## When To Use\n\n- Evaluating a new cross-border payment corridor for product launch or expansion\n- Benchmarking remittance pricing against competitors for a specific send\u002Freceive pair\n- Assessing regulatory feasibility of entering a new market or partnering with a local payout provider\n- Reviewing an existing corridor's economics (FX spread, fees, settlement costs) for margin optimization\n- Performing due diligence on an international payment provider or correspondent banking relationship\n\n## Inputs To Gather\n\n- **Corridor definition**: Send country, receive country, currency pair (e.g., USD→PHP), estimated monthly volume and average transaction size\n- **Customer segment**: Consumer remittance, SMB trade payments, enterprise treasury, or marketplace payouts\n- **Current pricing data**: Competitor fee schedules, published FX rates, and any available interchange or scheme fees\n- **Regulatory landscape**: Licenses held or required in send and receive jurisdictions [VERIFY per jurisdiction]\n- **Settlement infrastructure**: Correspondent bank relationships, local payment rails (ACH, RTGS, mobile money), and payout network coverage\n- **Risk parameters**: Sanctions screening obligations, fraud rates on corridor, chargeback exposure, and AML typologies specific to the corridor\n\n## Workflow\n\n1. **Define corridor scope**\n   - Specify origin\u002Fdestination countries, currency pair, and directionality (one-way vs. bidirectional)\n   - Identify customer segment and use case (remittance, B2B invoice, payroll, marketplace settlement)\n   - Set volume assumptions: projected monthly transactions, average ticket size, peak\u002Ftrough seasonality\n\n2. **Map regulatory requirements**\n   - Identify required licenses in the send jurisdiction (e.g., state MTLs in the US, EMI in EU, PSP license in UK) [VERIFY]\n   - Identify required licenses or partnerships in the receive jurisdiction (e.g., authorized dealer bank, mobile money operator approval) [VERIFY]\n   - Document sanctions and restricted-party screening obligations (OFAC, EU consolidated list, UN sanctions) [VERIFY]\n   - Note data localization, reporting thresholds (e.g., CTR at $10K USD equivalent), and consumer disclosure rules [VERIFY]\n\n3. **Analyze pricing and economics**\n   - Break down total cost to customer: upfront fee + FX markup + any intermediary charges\n   - Benchmark against at least three competitors on the same corridor using published rates or mystery-shop data\n   - Calculate unit economics per transaction: revenue (fee + FX spread) minus direct costs (scheme fees, correspondent charges, payout partner fees, compliance cost allocation)\n   - Model margin sensitivity to FX volatility — flag corridors where spread exceeds 150 bps or where local currency is illiquid\n\n4. **Evaluate settlement and payout infrastructure**\n   - Map available payout methods: bank deposit, mobile wallet, cash pickup, card credit\n   - Assess settlement speed: same-day, T+1, T+2 — and identify bottlenecks (cut-off times, correspondent bank processing windows)\n   - Evaluate pre-funding requirements and float implications on working capital\n   - Identify single points of failure (sole correspondent bank, single payout aggregator)\n\n5. **Assess operational and compliance risk**\n   - Score corridor on AML risk (high\u002Fmedium\u002Flow) based on FATF mutual evaluation, Transparency International CPI, and historical SARs filing rates\n   - Identify fraud typologies prevalent on the corridor (identity fraud, mule networks, structuring)\n   - Review partner due diligence: KYC\u002FKYB on payout agents, ongoing monitoring cadence, contractual audit rights\n   - Flag any pending regulatory changes that could affect corridor viability [VERIFY]\n\n6. **Compile corridor assessment report**\n   - Summarize go\u002Fno-go recommendation with supporting rationale\n   - Present pricing comparison table, unit economics model, and sensitivity analysis\n   - Include regulatory checklist with license status and timeline to compliance\n   - Outline implementation roadmap: partner onboarding, technical integration, testing, and launch milestones\n\n## Output\n\nThe deliverable is a **Cross-Border Payment Corridor Assessment Report** containing:\n\n- **Executive summary**: Corridor viability rating (green\u002Famber\u002Fred), key economics, and recommended action\n- **Regulatory matrix**: License-by-license status table for send and receive jurisdictions with estimated timelines\n- **Pricing benchmark**: Side-by-side comparison of total cost to customer across competitors\n- **Unit economics model**: Per-transaction P&L with assumptions clearly stated\n- **Settlement architecture diagram**: Flow of funds from send to receive, with intermediaries, cut-off times, and pre-funding nodes\n- **Risk scorecard**: AML risk tier, fraud exposure estimate, and operational concentration risk\n- **Implementation roadmap**: Phased plan with dependencies, milestones, and estimated launch date\n\n## Quality Checks\n\n- All regulatory requirements are jurisdiction-specific and tagged [VERIFY] where statutes, thresholds, or license names may change\n- Pricing benchmarks use data no older than 90 days; any stale data is flagged\n- Unit economics model includes all cost layers — no hidden costs omitted (nostro\u002Fvostro charges, FX hedging costs, compliance overhead)\n- Settlement flow accounts for weekends, holidays, and cut-off times in both jurisdictions\n- Sanctions and AML obligations reference the correct regime for each jurisdiction, not generic global statements\n- Competitor analysis compares like-for-like (same send amount, same payout method) rather than headline rates\n- Report clearly distinguishes confirmed data from estimates or assumptions\n",{"name":5,"tags":24,"source":29,"license":15,"language":30,"metadata":31,"description":7,"imported_at":42,"source_path":43,"source_repository":44},[25,26,27,28],"management","financial-technology","regulatory","valuation","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":32,"skill_modes":33,"document_types":36,"practice_areas":38},"casemark",[34,35],"Management","Coordination",[37],"Management Report",[39,40,41],"Fintech","Payments","Digital Banking","2026-09-20","skills\u002Ffinance\u002Fmanaging-cross-border-payment-analysis\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fmanaging-cross-border-payment-analysis","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-cross-border-payment-analysis",{"tool":57,"command":58},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-cross-border-payment-analysis",{"tool":60,"command":61},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-cross-border-payment-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fmanaging-cross-border-payment-analysis\u002FSKILL.md",true,[],[66,74,81,88,95,102],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]