figma guide

Designing breach settlement foreign claimant and international payment UI in Figma: W-8BEN collection, SWIFT routing, and cross-border verification

Design breach settlement foreign claimant and international payment UI in Figma with W-8BEN collection, SWIFT/IBAN validation, apostille document uploads, and cross-border payout tracking.

Published
Updated
Aug 27, 2026
Read time
9 min
Level
Intermediate

Quick answer

Foreign claimant UI lets non-US class members file claims and receive settlement payments across borders—without assuming US bank routing numbers or skipping treaty withholding rules. Design a country-aware claim form with address and ID formats per region, a W-8BEN or W-8BEN-E tax wizard before international PAY-*, and an administrator cross-border review queue with extended SLA badges. Connect to settlement claims, tax reporting, payment disbursement, and cross-border data transfer controls. Start from the Figma guides hub and pair with forms, file upload, and Dev Mode handoff.


Who this is for

  • Product designers building international settlement flows—not generic multi-currency checkout from ecommerce.
  • Settlement administrators processing apostilled documents and SWIFT wires at scale.
  • Class counsel defining which foreign claimants qualify and which countries are excluded from electronic payout.

Foreign claimant lifecycle overview

ForeignClaimantLifecycle — CLM-992-66102 · Claimant: Yuki Tanaka · Country: JP · Status: Cross-border review
├── Triggers:
│   ├── Country ≠ US on claim form or eligibility file
│   ├── Non-US phone prefix · Foreign address validation
│   ├── Admin flags from IP geolocation (supplement only—not sole gate)
│   └── [Call center](/designing-breach-call-center-and-agent-script-ui-in-figma/) identifies foreign claimant
├── ID namespace:
│   ├── FOR-* (foreign case) · XBR-* (cross-border verification) · PAY-INT-* (international payout)
│   └── TAX-* links to W-8BEN/W-8BEN-E not W-9
├── Status progression:
│   ├── Claim filed → Country verified → Identity docs → Tax form → Payment method → XBR review → PAY-INT-* wire/check
│   └── Sanctioned country → Block with counsel-approved message
└── Failed wire → [UCF-*](/designing-breach-settlement-unclaimed-funds-and-escheatment-ui-in-figma/) with extended dormancy for re-routing
StageAdministrator seesForeign claimant sees
Country flaggedFOR-* queueCountry-specific form fields
Identity reviewXBR-* document viewerUpload status with SLA badge
Tax formW-8BEN completenessWithholding estimate display
Payment setupIBAN/SWIFT validationBank detail wizard
PaidPAY-INT-* confirmationWire reference and receipt

Verdict: Never use US ACH fields for foreign claimants—show IBAN, SWIFT/BIC, and intermediary bank fields based on destination country.


Country-aware claim filing

ForeignClaimForm — CLM-992-66102 · Country: JP · Locale: en · Status: Submitted
├── Country selection (first step or derived from address):
│   ├── Dropdown with ISO codes · Drives all downstream field sets
│   ├── Sanctioned/blocked countries: Disabled with counsel message (not silent fail)
│   └── US territories: Separate handling per order (may use US payment rails)
├── Address fields (dynamic):
│   ├── JP: Postal code format · Prefecture · No US state dropdown
│   ├── UK: Postcode lookup optional · County optional
│   ├── CA: Province · Postal code A1A 1A1 format
│   └── Generic fallback: Free-form region + postal
├── Identity fields:
│   ├── National ID where applicable (My Number, NI, SIN) · Masked display
│   ├── Passport number optional supplement
│   └── Phone with country code picker · SMS OTP if supported in region
├── Language:
│   ├── Portal locale selector · Key notices in claimant language where translated
│   └── Admin review always in English with original doc attachment
└── Privacy: [Cross-border transfer notice](/designing-cross-border-data-transfer-and-scc-management-ui-in-figma/) at submission

Link country selection to saved addresses patterns—international formats need separate validation rules, not US-only regex.


Cross-border identity verification

CrossBorderVerification — XBR-992-0044 · CLM-992-66102 · Country: JP · Status: Docs requested
├── Document requirements (country-specific config):
│   ├── Government-issued photo ID (passport preferred)
│   ├── Proof of address (utility bill, bank statement · < 90 days)
│   ├── Apostille or consular authentication if required by counsel
│   └── Certified English translation upload slot
├── Upload flow:
│   ├── [File upload](/designing-file-upload-and-drag-drop-ui-in-figma/) · PDF/JPG · Multi-page passport
│   ├── Translation side-by-side viewer in admin console
│   └── Extended SLA badge: "International review: 15–30 business days"
├── Match logic:
│   ├── Name transliteration variants (Tanaka / 田中)
│   ├── DOB match against eligibility file
│   └── Address country must match FOR-* country (flag mismatches)
├── Fraud signals:
│   ├── VPN-only submission with US eligibility match → Manual XBR-*
│   ├── Duplicate passport hash across CLM-* → Block
│   └── Link to [eligibility portal](/designing-breach-victim-eligibility-verification-portal-ui-in-figma/) patterns
└── Actions: Approve · Request additional docs · Deny with appeal path to DIS-*

Do not reject claims solely because ID format differs from US driver’s license—use country-specific acceptable document lists.


W-8BEN and treaty withholding wizard

Foreign claimants use W-8 series forms instead of W-9 from tax reporting UI:

ForeignTaxWizard — TAX-992-66102 · Form: W-8BEN · Treaty: JP-US · Status: Complete
├── Step 1 — Claimant type:
│   ├── Individual → W-8BEN
│   ├── Entity → W-8BEN-E
│   └── Disregarded entity → W-8BEN with owner disclosure
├── Step 2 — Identification:
│   ├── Name · Country of citizenship · Permanent address (no P.O. box for tax)
│   ├── US TIN if any · Foreign TIN (My Number, etc.)
│   └── Date of birth (individuals)
├── Step 3 — Treaty claim (if applicable):
│   ├── Treaty country · Article and paragraph · Withholding rate claimed
│   ├── Limitation on benefits statement if required
│   └── System shows estimated withholding % (not tax advice disclaimer)
├── Step 4 — Certification:
│   ├── Electronic signature · Capacity to sign
│   └── TAX-* created · Release PAY-INT-* hold
├── Withholding display:
│   ├── Gross amount · Estimated withholding · Net wire amount
│   └── "Final withholding determined at payment" counsel disclaimer
└── Expiry: W-8 valid 3 years · Renewal reminder before PAY-INT-*

Block PAY-INT- above threshold until TAX- W-8 is complete**—same gate logic as domestic 1099 flows.


International payment method wizard

InternationalPayment — PAY-INT-992-66102 · CLM-992-66102 · Method: SWIFT wire · Status: Pending validation
├── Payment options (settlement-configured by country):
│   ├── SWIFT wire (most countries)
│   ├── International check (USD · mail to foreign address)
│   ├── PayPal/Venmo (only if counsel allows · usually US-only)
│   └── Blocked for sanctioned corridors
├── SWIFT wire fields:
│   ├── Beneficiary name (must match ID)
│   ├── IBAN or account number · SWIFT/BIC
│   ├── Bank name · Bank address · Country
│   ├── Intermediary bank (USD wires to some countries)
│   └── Reference/memo: CLM-* and settlement case ID
├── Validation:
│   ├── IBAN checksum · BIC format · Country-specific rules
│   ├── Name fuzzy match against XBR-* approved identity
│   └── Micro-deposit verification if partner supports (rare for settlements)
├── Fees:
│   ├── Show "Receiving bank may deduct fees" notice
│   ├── Optional: Settlement absorbs wire fee vs deduct from payment (per order)
│   └── Fee policy in plain language—not hidden in terms link only
└── Confirmation: Expected delivery 5–15 business days · Tracking reference when sent

For minor foreign claimants, guardian must complete payment wizard with blocked or court-equivalent routing in home country.


Administrator cross-border console

CrossBorderConsole — FOR-992-0044 · 12 pending XBR-* · 3 PAY-INT-* failed
├── Queues:
│   ├── XBR-* identity review · Extended SLA sort
│   ├── TAX-* W-8 missing · Blocks PAY-INT-*
│   ├── PAY-INT-* failed wire · Return reason codes (invalid IBAN, account closed)
│   └── Sanction screening hits · Counsel escalation
├── Wire failure handling:
│   ├── Return code display · Suggested fix (update BIC, verify name)
│   ├── Claimant notification email with secure link to update bank details
│   └── Retry limit before [UCF-*](/designing-breach-settlement-unclaimed-funds-and-escheatment-ui-in-figma/)
├── Batch operations:
│   ├── Export wire file for banking partner
│   ├── Reconcile SWIFT confirmations · Mark PAY-INT-* delivered
│   └── Year-end 1042-S reporting linkage (admin-only · not claimant portal)
└── Audit: for_id · xbr_id · pay_int_id · wire_ref · return_code · retry_count

Failed international wires need clear return reason codes—“Payment failed” alone forces unnecessary call center volume.


Comparison: foreign UI vs adjacent settlement surfaces

SurfaceFocusThis UI adds
Settlement claimsUS-default CLM-*Country-aware fields
Tax reportingW-9 / 1099W-8BEN / withholding
Payment disbursementACH/check USSWIFT / IBAN / intl check
Deceased claimantProbate docsApostille foreign death certs
Cross-border dataSCC complianceClaimant transfer notice

Handoff checklist (Dev Mode)

  • ForeignClaimForm — claim_id (CLM-), for_id (FOR-), country_iso, address_format_version, locale, sanction_screen_status.
  • CrossBorderVerification — xbr_id (XBR-*), for_id, claim_id, doc_refs[], translation_refs[], match_confidence, review_sla_days, approval_status.
  • ForeignTaxWizard — tax_id (TAX-*), form_type_enum (W8BEN/W8BEN-E), treaty_country, withholding_rate_claimed, certification_at.
  • InternationalPayment — pay_int_id (PAY-INT-*), claim_id, iban, swift_bic, intermediary_bic, beneficiary_name, wire_fee_policy_enum, validation_status.
  • CrossBorderConsole — for_id, queue_type_enum, wire_ref, return_code, retry_count, ucf_escalation_at.

Common mistakes

MistakeWhy it hurtsFix
US routing number field for all countriesInvalid payments · Wire failuresCountry-driven field set
Require US driver’s licenseExcludes valid foreign claimantsPassport + country ID list
Skip W-8 before international wireIRS compliance failureTAX-* gate on PAY-INT-*
No withholding estimateClaimant surprise · DisputesGross/net display
Silent block for sanctioned countriesLegal exposure without UXCounsel-approved message
English-only error on IBAN failAbandoned claimsLocale-aware validation messages
Same SLA as domestic reviewUnmet expectationsExtended SLA badge on XBR-*
Ignore wire return codesRepeated failed paymentsReturn code → fix wizard
Auto-translate legal noticesInaccurate counsel textProfessional translation flag
Store full passport in client logsPrivacy violationMask in analytics · Audit only

  1. Counsel defines eligible countries, sanction exclusions, and treaty positions before wireframes.
  2. Add country selector to CLM- filing* driving address, ID, and payment field sets.
  3. Design XBR- verification flow* with apostille and translation upload slots.
  4. Build W-8BEN wizard integrated with tax reporting TAX-* records.
  5. Design SWIFT/IBAN payment wizard with validation and wire failure retry.
  6. Configure admin cross-border console with extended SLAs and wire reconciliation.

FAQ

Can foreign claimants opt for US check in USD?

Yes if order allows · International check mailing to foreign address · Longer delivery · No IBAN required.

What about claimants in sanctioned countries?

Block electronic filing · Counsel-approved static message · Paper alternative if court order permits.

Dual citizens US + foreign?

Country of residence at filing drives form set · May file W-9 if US person for tax · XBR-* still if foreign address.

Currency of payment?

Most settlements pay USD · Show USD amount · FX conversion happens at receiving bank · Disclose in payment wizard.

Foreign deceased claimant estates?

Apostille death certificate · Foreign probate translation · Route through deceased claimant UI with extended XBR-* SLA.


Next steps

Share on X

§ Keep reading

Related guides.