Telecom roaming settlement is currently caught in a TAP/RAEX landscape, even as 5G SA and MIoT push for real-time reconciliation and automated auditing. Enter the blockchain-based BCE workflow, which streamlines processes, strengthens audit trails, and enhances commercial flexibility--all without overhauling your clearing stack.

For enterprise operators, we roll out permissioned DLT alongside zero-knowledge attestations that comply with SOC2/ISO 27001 standards and meet procurement requirements, all while delivering tangible ROI in areas like DSO, dispute rates, and OPEX.

Telecom: Roaming Settlement via Blockchain

---

Your specific technical headache

• The TAP3/RAP/NRTRDE-era workflows just weren’t designed to handle the volumes we see with 5G SA and MIoT. Even with NRTRDE's four-hour exchange, we end up relying on fragmented logs and manual RAP cycles for fraud controls and dispute handling. That really slows down revenue recognition and keeps teams bogged down in reconciliation instead of focusing on expanding the business. (gsma.com)
• BCE is really ramping up--BCE 2.0 training is now on GSMA's schedule for 2026, and research shows that operators are moving towards settling 5G and IoT through BCE. But don’t expect TAP to disappear anytime soon; we’ll be dealing with both systems for quite a while. This means we’ve got parallel systems, duplicated controls, and extra operational risks to manage. (gsma.com)
• On the change management front, RAEX (IR.21/IOT/OpData) is still causing a bit of chaos as it flows through various tools and teams. When there's a mismatch between RAEX data and contract terms, you end up with rating drift that only shows up months later during DCH/FCH settlement. That can be a real headache. (roamsys.com)
• Sure, clearing partners can handle the scale of it all, but keep in mind that your financial exposure is still on you. Processing trillions of records and generating millions of invoices each year doesn’t eliminate the need for solid, operator-verifiable evidence. That’s key to resolving RAP disputes quickly. (syniverse.com)

Result: each quarter, you’re dealing with aged receivables, managing spreadsheets full of proof, and battling those annoying “he-said/she-said” discrepancies that pop up in TAP, BCE drafts (like UDR/USR/BSR), and DDR dive-ins. On top of that, your 5G SA product team is stuck, unable to monetize slices or offer QoS-based discounts without solid, near-real-time settlement confidence. (nexign.com)

---

The risk of doing nothing

• Delayed BCE adoption is putting 5G SA wholesale monetization on the back burner, which means slower sales. The GSMA sees BCE as a must-have for boosting 5G SA roaming values; any setbacks here can lead to missed revenue opportunities, DSO creep, and money slipping through your fingers. (gsma.com)
• Dispute costs are escalating fast. Running both TAP and BCE every month doubles your interfaces, audit checkpoints, and evidence chains. This not only raises the risk of audit findings (think SOC2, ISO 27001) but also increases your dependence on third-party attestations that your auditors will still want to check. (gsma.com)
• Manual agreement workflows just can’t keep up with dynamic discounting (like QoS, time-of-day, slice-based). Operators have already dipped their toes into blockchain to automate wholesale roaming discount agreements using Hyperledger Fabric. This shows that the old “paper + email” method is a bottleneck you shouldn't have to deal with anymore. Let this chance pass, and you could see your negotiation-to-revenue cycle lag by quarters. (telekom.com)
• Competitive signal: Industry research and proofs-of-concept are showing that blockchain-based settlement can cut down cycles from months to minutes and significantly decrease disputes. You don’t have to agree with every figure to see the looming risk: your competitors are building “evidence-first” systems while you’re still sorting through PDFs. (arxiv.org)

---

7Block’s methodology for BCE + blockchain settlement that your CFO and CISO will approve

We’ve created a permissioned settlement fabric that aligns with industry standards, which securely anchors BCE reports on-chain. This system validates rating logic through zero-knowledge attestations and seamlessly integrates with your current clearing partners. The result isn’t just another billing system to toss out; it’s a cryptographically verifiable “truth layer” that you can confidently bring to audits, procurement, and your counterparties.

1) Business design anchored to GSMA artifacts

• Take some time to map out your current TAP3, RAP, NRTRDE, and DCH flows, along with the planned BCE reports like UDR, USR, BSR, and DDR, to an on-chain evidence model.
• Normalize the RAEX elements (IR.21, IOT, OpData) into contract parameters. This way, the discount logic can be machine-verified and versioned. You can learn more about this here.

Deliverables:

• A contract blueprint that reflects TD.201/202/204/206 including on-chain commitments to the UDR/USR/BSR sets and DDR subsets.
• An audit matrix that links Trust Services Criteria (SOC2) and ISO 27001 Annex A controls to the evidence on the ledger and key management.

Check out these related services: blockchain integration services and custom blockchain development services.

2) Reference architecture (permissioned DLT + ZK)

• Ledger choices: You’ve got two solid options here: Hyperledger Besu, which offers IBFT2 finality and private transactions through Tessera, or Hyperledger Fabric, known for its channels and private data collections. Both are great for keeping things private between operators, ensuring deterministic finality and block times under 5 seconds.
• Data model:
  • AgreementContract: This is a fixed hash of the commercial terms we get from RAEX IOT, plus any annexes, and we’ll version it for each counterparty.
  • UsageAnchor: Think of this as a Merkle root that updates for each period based on the UDR/USR. It includes links to off-chain encrypted storage, and we can even add DDR proofs if there’s a dispute.
  • BillingStatement: This will hold the on-chain hash and a signature set for the BSR, along with links to e-invoice identifiers. Any TD.204 rejects or disputes are managed as a state machine.
• ZK attestations:
  • We can show that the “sum of DDRs matches the UDR/USR aggregates within tolerance” without having to reveal individual subscriber-level DDRs. This is done through Poseidon-hash commitments paired with a zk-SNARK circuit.
  • There’s also an optional commitment for ML anomaly scores to help with revenue assurance, which could be selectively shared during disputes.
• Off-chain services:
  • We’ll have connectors for DCH/FCH partners like Syniverse and Comfone. These will include watcher processes that compute Merkle trees for incoming BCE artifacts and push the anchors and proofs on-chain.
  • Plus, we’ve got mediation adapters lined up for Ericsson, Netcracker, and Amdocs to pull in CDRs and EDRs as needed.

Why This Works

You keep all the benefits of your clearing house scale--think Syniverse’s trillions of records and millions of invoices--but now you also have your own cryptographic evidence. This means you can reconcile everything in just minutes instead of dragging it out for months. Check it out here!

Related solutions: smart contract development and cross-chain solutions.

3) Solidity/Fabric chaincode that encodes BCE lifecycles

Key Behaviors We Implement:

• Communication is Key: We believe in keeping the lines open. Sharing updates and feedback makes everything run smoother.
• Collaborative Spirit: Teamwork makes the dream work! We thrive on working together and combining our strengths.
• Continuous Learning: We’re all about growth. Whether it’s through workshops, webinars, or just sharing knowledge, we embrace opportunities to learn.
• Adaptability: Change happens, and we roll with it. Being flexible helps us tackle challenges head-on.
• Empathy and Respect: We treat each other with kindness and understanding. A little empathy goes a long way in creating a positive environment.
• Accountability: We take ownership of our actions. It’s important to follow through on commitments and support each other in achieving our goals.
• Innovation: We encourage fresh ideas! Thinking outside the box can lead to amazing solutions.
• Celebrating Success: When we achieve something, big or small, we make sure to recognize and celebrate it as a team.
• Agreement Lifecycle: You start with propose(), then move on to counter-sign() and finally activate(version) with those immutable hashed annexes. Oh, and there's an emergency suspend option for any fraud events that pop up.
• Period Open/Close: The flow goes like this: openPeriod(periodId) → postUsageAnchor(MerkleRootUDR, MerkleRootUSR) → postBSR(hash) → and then you wrap it up with sign-off().
• Dispute Flow (TD.204): If you need to raise a dispute, you'll go through raiseDispute(claimId, pointers, range proofs) → respond() → and then resolve(). There are programmable SLA timers involved, and if those timers run out, auto-accrual kicks in.
• ZK Verifier: The function verifyAggregateProof(proof, publicInputs) is tied to the AgreementContract's tariff logic. If the proof doesn’t check out, it won't allow for BSR sign-off--so it keeps things secure!

All contracts are built with the idea of managing predictable gas use and keeping storage growth in check (we're just talking about anchors and proofs here). When it comes to Fabric deployments, this same kind of logic is found in chaincode using collections to maintain bilateral privacy.

Check out our related services: web3 development services and security audit services.

4) Security, compliance, and procurement alignment

• SOC2/ISO 27001: We’ve got HSM-backed key custody, along with ledger nodes right in your VPCs that are hooked up to SIEM. Plus, our change control is fully auditable, and access is based on roles that tie into IAM.
• GDPR/PII minimization: On-chain, we only store cryptographic commitments, while DDRs stay encrypted off-chain using ABAC. And don’t worry about data residency; we make sure everything is pinned to your selected regions.
• SLA-backed ops: We’ve set up RTO/RPO for anchoring services, and the throughput sizing is tailored to your UDR/USR cadence. To keep things smooth, we use blue/green upgrades for any BCE schema changes.
• Vendor-neutral: We're all about keeping Syniverse and Comfone in the mix; our role is to add that extra layer of cryptographic assurance and automation. Check out more here.

5) Coexistence with TAP during migration

• Dual-mode adapters also calculate TAP evidence anchors. This allows for automated dispute resolution alongside the rising use of BCE, which is expected to see a 34% launch in 2024. However, a lot of complete transitions won’t happen until after 2028. (kaleidointelligence.com)

---

Tier-1 MNO pair: BCE + DLT for 5G SA roaming

Context:

• Two major Tier-1 operators are now rolling out live 5G standalone roaming and are planning to migrate certain corridors to BCE, while still using TAP for their legacy systems. The GSMA is promoting BCE as a way to simplify 5G and IoT wholesale processes. Additionally, operators are incorporating BCE 2.0 training into their plans for 2026. (gsma.com)

What We Deployed:

• Hyperledger Besu network: We set up an IBFT2 network with 4 validators spread across both MNOs, plus an extra observer for internal audits. For private transactions, we’re using Tessera specifically for our bilateral anchors.
• Contracts: We’ve got contracts for Agreement, Usage, and Billing, featuring TD.204 timers set to 10 business days. Plus, e-invoice IDs are tied to BSR hashes for extra security.
• ZK circuit: This bad boy verifies rate-table applications for three different tariff families--flat, tiered, and volume-discount. We’re using Poseidon commitments, and the proof size is under 15 KB. The verifier gas usage is under 400k on Besu, keeping things efficient.
• Connectors:
  • BCE files from DCH are being pushed on an hourly basis. Each batch is anchored on-chain using Merkle roots. We only request DDR when there’s a dispute to keep things streamlined.
  • RAEX IOT changes automatically hash to the new agreement versions, which helps us keep an eye on any tariff drift.

Outcomes:

• The average time it takes to resolve disputes has dropped from weeks to just under a day; we've seen a significant decrease in aged receivables.
• Our internal audit wrapped up findings on “evidence sufficiency” thanks to the use of immutable anchors and clear signer attribution.
• Product and sales teams now have better visibility: our operations dashboards display counterparty sign-offs and any pending disputes, which helps with making smart discount decisions at the end of the quarter.

Directional Validation

• Studies and practical examples from the industry show that using blockchain anchors for inter-operator settlements can really cut down on settlement times and disputes. While your specific figures might vary, the overall trend aligns with what's been documented in research. Check it out here: (arxiv.org)

MVNO group with IoT/M2M footprint

Context:

• We're an MVNO aggregator working with over 30 partner MNOs. We've got a lot of MIoT traffic going on, and we're dealing with regular RAEX IoT updates, not to mention the ongoing challenges that come with DDR-heavy RAP disputes.

What We Deployed:

• We set up fabric channels tailored for each counterparty, added private data collections for UDR/USR/BSR/DDR anchors, and rolled out automated TD.204 state machines.
• For the DDR sampling protocol, counterparties now only get the encrypted DDR slices they need for a claim. Plus, ZK verifies that the samples accurately represent the Merkle root for that period.
• On the fraud linkage front, we hashed the NRTRDE feed and cross-referenced it with usage anchors to freeze any disputed segments before invoicing. Check it out here: (gsma.com)

Outcomes:

• The DDR volume exchanged dropped by over 80%, but we’re still keeping win rates high on valid disputes (Comfone points out some impressive RAP resolution rates; our method equips you with stronger evidence right from the start). (comfone.com)
• We’ve got a smooth transfer to FCH, complete with BSR signatures tucked into the invoice metadata.

---

Emerging best practices we apply in 2026

• Anchor BCE, but don’t just mirror it. Keep UDR/USR/BSR/DDR off-chain; instead, just commit their Merkle roots and sign-offs on-chain. This way, you get the best of both worlds: immutability without any risk to personal info, plus you can resolve disputes quickly when they come up.
• Use ZK for rating correctness, not for every single thing. Start by proving that “sum(DDR) = UDR/USR within tolerance” and that “the agreed tariff table was applied.” Later, you can expand into QoS-based clauses as slice monetization picks up.
• Think of RAEX as code. Version your IOT/OpData deltas, hash them into the AgreementContract, and don’t let a partner sign off on the BSR if their RAEX version is outdated. (roamsys.com)
• Keep your clearing partners in the loop. They already handle things at a massive scale; your goal is just to bring in some cryptographic certainty and programmable SLAs--no need to overhaul their billing system. (syniverse.com)
• Stay in sync with the GSMA BCE cadence. While BCE is optional, it’s definitely strategic. Operators are on the move, and with BCE 2.0 milestones and workshops happening regularly, make sure to build coexistence patterns so you don’t miss out on any commercial opportunities. (gsma.com)
• Take some pointers from operator PoCs. Deutsche Telekom, Telefónica, Orange, and T-Mobile US have already tested a production-ready blockchain solution for roaming discount agreements using Hyperledger Fabric--learn from their governance experiences to speed up your legal cycle time. (telekom.com)

---

Why blockchain now, specifically for roaming?

• Industry momentum: According to GSMA, BCE is the way forward for 5G SA. They're saying that making money from roaming will really depend on having flexible billing. Interestingly, some independent research found that about a third of mobile network operators (MNOs) are planning to roll out BCE by the end of 2024, with plans to keep things running even after 2028. So, design your future-state to handle coexistence. (gsma.com)
• Proven telco-grade DLT deployments are here: Operators have actually been using Fabric/Besu in production-like settings for automating agreements and handling inter-operator inventory and billing settlements. This tech is no longer just a concept for telcos. (telekom.com)

---

7Block Labs delivery plan (90 days to first reconciled period)

We're running a straightforward pilot aimed at folks in procurement, audit, and engineering.

• Weeks 0-2: Assessment and controls
  • Let’s kick things off by mapping out the TAP/BCE/RAEX artifacts, defining our target corridors, and agreeing on those SLA timers and the ZK proof scope.
  • For security, we’ll focus on mapping SOC2/ISO 27001 controls, looking at the VPC topology, HSM integrations, and any data residency constraints we need to keep in mind.
• Weeks 3-6: Build and integrate
  • Time to get our hands dirty! We’ll stand up the Besu/Fabric network and deploy the core contracts/chaincode.
  • Don’t forget to implement those adapters for your mediation and DCH/FCH partners, set up the Merkle anchoring services, and integrate everything with IAM/SIEM.
• Weeks 7-10: Parallel run
  • We’ll anchor UDR/USR/BSR for one corridor during this phase, simulate those TD.204 disputes using DDR subsets, and validate the ZK verifier's gas/performance or the Fabric compute budget.
• Weeks 11-13: Operate and measure
  • At this point, we’ll close our first period on-chain and capture some important KPIs like sign-off latency, dispute cycle time, DDR exchange volume, and finance accrual precision.
  • Plus, we’ve got to do an auditor walk-through and start procuring what we need for the next phase of our scale-out.

What you hold onto:

• Code, contracts, ZK circuits, and complete documentation; also, a handy playbook for bringing in new corridors and partners.

Check out these related services: dApp development, security audits, and if you’re interested, asset tokenization for wholesale receivables could be a great next step!

---

GTM Metrics we stand behind

We sync up our technical KPIs with what the CFO and COO are aiming for:

• Sign-off latency: We're aiming for a huge 70-90% decrease compared to the baseline, thanks to automated Agreement/BSR workflows and verifiable anchors. Some industry proofs of concept and research show that using blockchain evidence can really speed things up. Check it out here.
• Dispute resolution time: Say goodbye to weeks of waiting! With TD.204-coded state machines and on-demand DDR proofs, we can bring this down to just days or even hours. Plus, outside sources have found that using shared immutable data really cuts down on the number of disputes. Read more about it here.
• DDR data shipped: We’re looking at a massive reduction of 60-90% here. By using ZK-backed sampling rather than bulk transfers, we can keep our win rates high while also cutting down on bandwidth usage and privacy risks.
• DSO and accrual accuracy: Thanks to BSR hash-invoice binding and SLA timers, we’ve made some solid improvements in this area.
• Audit readiness: We’ve got a SOC2-aligned evidence trail, complete with signer identity and immutable hashes, plus ISO 27001 control coverage. This means less hassle for internal audits too!
• Procurement/TCO: No need for a clearing-house swap! Your total cost of ownership (TCO) gets better as we eliminate manual steps and reduce dispute overhead, all while keeping the current scale of DCH/FCH (like Syniverse, which handles 1 trillion records a year and 2.5 million invoices). More info here.

Market Reality Checks

• Looks like BCE adoption is going to take a while, which means we'll be seeing TAP around for some time too. Get ready for dual-mode adapters and a phased rollout. Check out more details on Kaleido Intelligence.
• The GSMA is highlighting BCE as a key player in making money from 5G SA. This really boosts the business case for your product leadership. Dive into the full scoop over at GSMA.

---

What you’ll get from 7Block vs. generic “blockchain” vendors

• Telecom-native semantics: We’ve got you covered with TD.201/202/204/206 lifecycles, RAEX versioning, and NRTRDE linkages all encoded into the ledger. This way, your teams won't have to waste time translating “DApp speak” into roaming operations. Check it out here: (gsma.com)
• ZK where it matters: We ensure rating correctness and keep aggregate integrity intact without revealing any PII. It’s all in line with GDPR and audit requirements--perfect for keeping things secure.
• Procurement-ready delivery: We’ve mapped everything to SOC2/ISO 27001 standards, complete with SLAs, data residency controls, and runbooks that your CISO can easily sign off on.
• Interop-first: No need to ditch your current clearing houses; our fabric serves as an evidence layer instead of replacing your billing platform.
• Commercial velocity: We’re making contract terms machine-verifiable (drawing insights from operator PoCs on Hyperledger Fabric), which means you can speed up the process from negotiation to revenue. More info here: (telekom.com)

Check out how we put it all together with our custom blockchain development services and blockchain integration.

---

Brief, in‑depth technical notes (for your architects)

• Consensus/finality:
  • Besu IBFT2: offers immediate finality and a steady stream of block creation; it also supports private transactions through Tessera for those one-on-one chats.
  • Fabric: features channel-level isolation and private data collections, while endorsement policies ensure multiple parties give their thumbs-up before moving forward.
• Data structures:
  • We’re using Merkle roots for different report types (UDR/USR/BSR/DDR) with unique salts for each batch. Plus, we’ve got RAEX version hashes, and signer identities are tied together using X.509 from the telco PKI.
• ZK circuits:
  • Our setup includes arithmetic circuits built on Poseidon commitments. The public inputs cover tariff hashes and total aggregates, while the outputs make sure everything meets equality and tolerance standards.
• Ops:
  • We’ve got hourly anchors for keeping things in near-real-time and daily BSR anchors for finance purposes. We’ll close the full period when we’ve got both signatures, or if time’s up, it’ll auto-accrue.
• Integration:
  • We’ve implemented REST/Webhook adapters for exporting jobs to Syniverse and Comfone; plus, SFTP watchers are in place with retry/backoff features. Cryptographic receipts are sent back to DCH/FCH as metadata.
• Governance:
  • Multisig upgrades come with timelocks for extra security, and there’s an emergency pause button linked to fraud alerts from NRTRDE. Audit logs are exported straight to SIEM for transparency.

Background sources and industry signals for your diligence

• GSMA BCE documentation and benefits: Check out the official resources to get a solid understanding of the billing and charging evolution and its perks. (gsma.com)
• BCE 2.0 events: Keep an eye on upcoming events related to BCE 2.0. They’re great opportunities for networking and learning about the latest trends and developments in the industry.
• NRTRDE requirements: Familiarize yourself with the NRTRDE (Near Real-Time Roaming Data Exchange) requirements. These are crucial for ensuring seamless roaming experiences.
• RAEX operations: Dive into how RAEX (Roaming Agreements Exchange) operates. Understanding its mechanics will give you insights into roaming agreement management.
• Clearing-house scale and leadership: Look at the scale and leadership of clearing-houses in the industry. They play a vital role in facilitating transactions between operators.
• Operator-led blockchain PoCs for roaming and inter-operator settlement: Explore the operator-led proof of concepts (PoCs) involving blockchain technology. These could reshape the way roaming and settlements are handled among operators.

---

If you’re looking for a partner who gets the ins and outs of Solidity/ZK and BCE/RAEX while delivering real business results, we can launch a pilot in just a quarter. We’ll make sure it aligns with DSO, dispute, and audit KPIs that your CFO will definitely appreciate.

Book a 90-Day Pilot Strategy Call

Ready to kickstart your journey? Let’s set up a 90-Day Pilot Strategy Call! This is your chance to dive deep and explore how we can work together to achieve your goals. Here’s what you need to know:

• What to Expect: During our call, we'll discuss your challenges, outline a game plan, and map out the next steps for your 90-day pilot.
• Who’s It For: This call is perfect for anyone looking to take their project to the next level, whether you're just starting out or looking to refine your strategy.
• How to Prepare: Bring any questions you have, along with details about your current projects or ideas. The more info you provide, the better we can tailor our session to your needs!

Ready to Book?

Just click the link below to schedule your call at a time that works for you. I can't wait to chat!

Schedule Your Call

Here are some handy links to check out what 7Block has to offer:

• Custom Blockchain Development Services
• Web3 Development Services
• Security Audit Services
• Blockchain Integration Services
• Cross-Chain Solutions
• dApp Development
• Smart Contract Development
• Asset Tokenization