๐Ÿ“Œ Auto-generated hourly from UR ร— client Telegram groups. Last updated: 2026-06-05 16:29. TBD = not yet stated in-group.

UR ร— Client Telegram โ€” Integration Tracker & UR Action Items

Generated: 2026-06-05 16:10

๐Ÿ”” This Round โ€” Key Open Items (most urgent for UR)

ClientPriorityOpen askUR action
CyphalabsHighAfter the 6/5 mainland-China jurisdiction change, their team (based in US/China) is KYC-rejected and integration is blocked; asks whether they can be unblocked and retry KYCProduct + compliance: decide whether a waiver or alternative KYC path is possible for their testing/integration; give a clear answer
MatchainHighStrong demand for Ethereum/BSC top-up API (Mantle-only is too much friction); flagged as "must-have"Evaluate and schedule adding ETH/BSC + USDT/USDC top-up to the API
UR-TechdollarHighHas its own Sumsub; wants the share-token reuse path; waiting on UR to enable its KYC test env + confirm required Sumsub fieldsConfigure/enable their KYC testenv; reply with the user-info fields needed for Sumsub reuse
PeraspayMedTesting; already shared Sumsub APP TOKEN/Secret; waiting on onboarding configComplete onboarding config with their Sumsub creds; advance mock top-up testing
SwissPayMedPartner returned change requests on the MSA (over email)Legal + team to review feedback; send revised DocuSign
IBANIMedChose UR as card vendor; DocuSign sent, awaiting signatureSchedule kickoff (early next week); follow the signing
UPayMed$20M/mo spend volume; awaiting their feedback on the new pricing (refundable deposit vs fixed-fee)Follow up on pricing feedback; advance co-brand card commercials
โš ๏ธ Cross-client signal (recommend UR product handle centrally): the only mature KYC path today is "Partner's own Sumsub โ†’ share-token reuse"; Webview KYC is not feasible under Managed Custody (passport NFC requires a native app). This recurs across Based / IRST / Mosavi / Techdollar / Peraspay and is a primary integration blocker.

1. Client Integration Profiles (clients integrating / planning to integrate UR)

Client (group)Integration ModeCard ModeKYC ModeStatusUR Action
MatchainTBD (consumes top-up/card API)TBDTBDTesting / activeSchedule ETH/BSC top-up API + USDT/USDC top-up
Ant Wallet (Ant/Topnod)TBD (likely Managed Custody)TBD (card-info API)TBDSoft-launched to a small cohort (CRS live)Fix fiat24 card-query API error; support CRS
GoldCoin (card integration)TBD (likely Managed Custody)Card integrationTBD (CRS in progress)Live / onboarding usersHandle 6/5 China jurisdiction change impact on their users; push CRS completion
HyperTradeExternal Wallet AccessLikely Crypto Backed (EOA + card-contract allowance; mock authorize/increment)TBDTesting (testnet working), near onboardingCollect onboarding form; webhook config; confirm transaction_v2 enums
IRSTManaged CustodyTBDPending (Webview infeasible; needs native-app NFC)Testing (all APIs working on testnet)Advise on KYC approach; move to formal onboarding
UR-TechdollarManaged CustodyTBDShare-token reuse (own Sumsub)Starting integrationEnable their KYC testenv config; reply on required Sumsub fields
PeraspayManaged CustodyTBDSumsub (TOKEN/Secret shared)Testing (PartnerID 8221 on testnet)Finish onboarding config; advance mock top-up
EthenapayManaged CustodyCrypto BackedTBDIntegrating (kickoff/testing; latest activity ~April)Follow up post-kickoff; KYC + core-banking integration
BasedTBD (API, mobile)TBDUR Webview / native-app NFC (under discussion)IntegratingHelp whitelist deeplink redirect URI; confirm KYC routing
BiyaTBDTBDTBDTesting (PartnerID 8219 on testnet)Support post-mint testing; clarify same-name / third-party transfer rules
VenzoTBD (awaiting client's Account Mode choice)TBDTBDTesting (PartnerID 8215 on testnet)Await Account Mode decision; support testnet
AshTBD (API; shared Managed Custody / Crypto Backed docs)TBDTBDContact / evaluating (reviewing docs)Follow up on doc feedback; provide test account
UOKTBDTBDTBD (KYC lead Mario introduced)Early onboardingSet admin access; support sandbox; KYC onboarding
UPayDelegated (legacy)Co-brand cardTBDCommercial negotiation (pricing)Follow up on pricing feedback; advance co-brand commercials
PingMeTBD (redirect, no white-label)TBD (needs Monad top-up)TBDCommercial-agreement stage (latest activity ~March, likely stalled)Send commercial agreement; card design; confirm whether still active
MosaviTBDTBDKYC flow too long (40โ€“50 pages); wants it simplified / a licensed alternativeStalled on KYC UX / compliancePush KYC simplification / tiering; give formal feedback
MEXCTBD (EUR card)TBDTBDCommercial / earlyClarify EU marketing compliance (MiCA needs no license from them; KOL marketing OK)
SwissPayTBDTBDTBDSigning (MSA legal back-and-forth)Legal to review partner feedback; return revised DocuSign
IBANITBD (UR as card vendor)TBDTBDSigning (DocuSign sent)Arrange kickoff; follow signing
CyphalabsTBD (openapi)TBDSumsub (KYC rejected on geography)Testing, blocked by 6/5 China jurisdiction changeDecide whether to unblock / offer alternative KYC so they can continue

2. Suspected / Early BD (newly created or low-activity groups)

GroupNatureStatusUR Action
Tether <> UREarly BD (met at Money2020; sandbox shared)ContactFollow up post-meeting; decide if it becomes an integration
Chainnodes <> UR (Issuer Processor)They are building an issuer-processor platform; want input / potential partnershipContactProduct + tech intro; clarify partnership vs integration
Stargate-Tempo-URTempo-chain on/off-ramp intro (1 message)NewFollow up on Tempo ramp integration
Monad <> URChain/foundation BD (Monad top-up + expanded collaboration)BD in progressFollow up on collaboration scope; Monad top-up support

Open / Unclear [?]