The Stellar Anchor Platform is the canonical reference implementation for businesses issuing fiat-backed assets and operating deposit/withdrawal services on Stellar. It implements the full Stellar Ecosystem Proposal (SEP) stack—including SEP-6, SEP-24, SEP-31, and SEP-38—providing a production-grade API for interactive KYC, non-interactive deposit, cross-border payments, and on-chain/off-chain order book quoting. For payment operators, wallets, and exchanges, the Anchor Platform is the primary integration surface for regulated value transfer between the Stellar network and traditional banking rails.
Protocols
Anchor Platform and Business Integration SDKs
Release notes and operational guides for the Stellar Anchor Platform, covering API changes, custody integration patterns, and compliance framework updates. Anchors and payment operators use this to maintain their on/off-ramp infrastructure and ensure compatibility with the broader Stellar ecosystem.
introduction
ANCHOR INFRASTRUCTURE FOR STELLAR ON/OFF-RAMP
Introduction
The Anchor Platform and Business Integration SDKs provide the standardized infrastructure for regulated fiat on/off-ramp services on the Stellar network.
The Business Integration SDKs are the client-side counterpart, providing typed libraries in multiple languages that abstract the complexity of SEP handshakes, JWT authentication, and multi-step transaction flows. These SDKs handle the full lifecycle of an anchored transaction: initiating a deposit or withdrawal, polling for status updates, presenting interactive KYC URLs to end users, and verifying the final on-chain settlement. For wallet and application developers, the SDKs are the critical dependency that determines whether an integration with an anchor is reliable, secure, and compliant with the latest SEP specification changes.
Operationally, anchor releases introduce changes to custody integration patterns, compliance framework hooks, and API behavior that can break downstream integrations if not tracked. A change to the SEP-24 interactive flow, a new required field in the /info endpoint, or a modification to the SEP-38 quote structure can silently corrupt a wallet's deposit UX or cause an exchange's reconciliation pipeline to fail. Teams running anchor infrastructure or integrating with anchors should treat each release as a mandatory compatibility checkpoint. Chainscore Labs provides anchor upgrade readiness reviews, integration impact assessments, and SEP compliance validation to ensure that on/off-ramp infrastructure remains reliable and audit-ready across protocol and platform version changes.
ANCHOR PLATFORM AND BUSINESS INTEGRATION SDKS
Quick Facts
Operational facts about the Stellar Anchor Platform and SDKs to help payment operators and on/off-ramp providers assess integration stability and maintenance requirements.
| Area | What changes | Who is affected | Action |
|---|---|---|---|
Anchor Platform API | REST API endpoints for SEP-6, SEP-24, and SEP-31 evolve with each release; breaking changes may affect transaction and KYC flows. | Anchors, wallets, payment operators | Pin integration tests to a specific Anchor Platform version and review the changelog before upgrading. |
Custody Integration | The custody abstraction layer decouples the Anchor Platform from specific custody providers, but interface changes can break transaction signing. | Anchors using external custodians | Verify custody adapter compatibility against the target Anchor Platform release in a testnet environment. |
Compliance Framework | SEP-12 callbacks and sanctions screening integrations are updated to match evolving regulatory requirements. | Compliance officers, anchors | Re-validate your SEP-12 implementation and sanctions list provider integration after each platform upgrade. |
SEP Protocol Support | New SEP versions or optional fields may be required for ecosystem compatibility; lagging adoption can cause wallet rejections. | Wallets, exchanges, anchors | Monitor the Stellar Ecosystem Proposal repository and test against the reference Anchor Platform implementation. |
SDK Lifecycle | Official Stellar SDKs are being phased out in favor of auto-generated libraries; community SDKs may have different maintenance guarantees. | Developers, integration teams | Audit your dependency tree for deprecated SDKs and plan a migration to a supported library. |
Database Schema | Anchor Platform upgrades may include migrations that alter the database schema; failed migrations can cause data inconsistency. | DevOps, infrastructure teams | Back up the database before every upgrade and run schema migration checks in a staging environment. |
KYC/Callback Configuration | Misconfiguration of interactive webapp URLs or callback endpoints can silently break deposit and withdrawal flows. | Anchors, frontend developers | Test the full user journey, including SEP-24 interactive flows, after any configuration change. |
Transaction Reconciliation | Differences between Anchor Platform state and on-chain state can arise from incomplete Horizon ingestion or custody sync issues. | Operations teams, accountants | Implement a periodic reconciliation job comparing Anchor Platform records against Horizon and custody statements. |
technical-context
ANCHOR PLATFORM COMPONENTS
Architecture and Integration Surface
The Stellar Anchor Platform is a modular, pre-built system that standardizes how fiat on/off-ramps connect to the Stellar network, handling the complex orchestration between banking, compliance, and blockchain layers.
The Anchor Platform is not a monolithic application but a collection of services that implement the Stellar Ecosystem Proposals (SEPs) required for anchor operation. Its core components include the Anchor Platform Server, which exposes the SEP-24 (Interactive) and SEP-6 (Programmatic) deposit/withdrawal APIs, and the Business Integration SDKs, which provide a standardized interface for the platform to communicate with a partner's existing backend systems. This architecture decouples the Stellar-specific protocol logic from the anchor's proprietary banking, KYC, and custody infrastructure.
The critical integration surface is the callback interface defined by the Business Integration SDKs. When a user initiates a deposit, the Anchor Platform handles the Stellar transaction mechanics but delegates the actual movement of fiat funds to the anchor's backend via a well-defined REST API. The anchor must implement endpoints for actions like GET /customer, PUT /customer, POST /fiat-deposit, and POST /fiat-withdrawal. A failure in this integration layer—such as an idempotency bug in the POST /fiat-deposit callback—can lead to a loss of funds or a broken user experience where Stellar assets are received but the corresponding bank transfer is never initiated.
For operators, the primary operational risk is state synchronization between the Anchor Platform's transaction records and the anchor's internal ledger. The platform uses an asynchronous job queue (typically backed by a database) to manage the lifecycle of a deposit or withdrawal. Monitoring the depth and failure rate of this job queue is the most direct signal of integration health. Teams running the Anchor Platform must also manage the secure storage of Stellar signing keys used for fee sponsorship and operational accounts, and ensure their SEP-38 rate endpoints are fed with accurate, up-to-date pricing data to prevent arbitrage. Chainscore Labs can review this integration surface, focusing on callback idempotency, key management, and state reconciliation logic to prevent operational losses.
ANCHOR PLATFORM AND SDK RELEASE IMPACT
Affected Systems and Teams
Direct Operational Impact
Anchor operators are the primary consumers of these releases. Each update may change the behavior of SEP-6, SEP-24, or SEP-31 endpoints, requiring immediate integration testing.
Action Items:
- Audit custom custody integrations against new API schemas.
- Re-validate compliance framework callbacks (KYC, sanctions screening).
- Test deposit and withdrawal flows end-to-end in a staging environment before upgrading production.
- Monitor for changes to transaction status semantics that could break internal reconciliation logic.
Chainscore can perform a pre-upgrade integration review to identify breaking changes in your specific anchor deployment.
implementation-impact
ANCHOR PLATFORM LIFECYCLE
Operational Impact and Migration Patterns
Changes to the Anchor Platform and Business Integration SDKs directly affect the operational reliability of on/off-ramp services. Teams must assess API deprecations, custody integration patterns, and compliance framework updates to prevent service disruption.
01
API Deprecation and Breaking Changes
Anchor Platform releases may deprecate REST API endpoints, modify request/response schemas, or change authentication flows. Anchors must regression-test their existing integrations—particularly for SEP-6, SEP-24, and SEP-31 endpoints—against each new release. A missed deprecation can break deposit and withdrawal flows for wallet partners. Maintain a staging environment that mirrors production and run the full SEP compliance test suite before upgrading. Chainscore can perform an integration impact review to identify breaking changes before they reach production.
02
Custody Integration and Transaction Signing
The Anchor Platform abstracts custody backends, but changes to the signing interface or transaction submission logic can introduce nonce conflicts, fee miscalculations, or double-spend risks. Operators using HSM-backed or MPC-based signing must verify that new releases maintain compatibility with their custody provider's API. Test transaction submission under load, including fee-bump scenarios and Soroban resource fee estimation. A failed custody integration can halt all withdrawal processing.
03
Compliance Framework and KYC Rule Updates
Updates to the Anchor Platform's compliance engine—including changes to sanction screening, transaction monitoring rules, or KYC callback handling—can alter which transactions are flagged or rejected. Anchors must review the compliance changelog for each release and re-validate their regulatory posture. A misconfigured rule update can cause false-positive blocks on legitimate customer transactions or, worse, allow prohibited activity. Run a controlled rollout with sampled transaction monitoring before full deployment.
04
Database Migration and State Integrity
Anchor Platform upgrades may include database schema migrations that alter how transactions, customers, or compliance records are stored. Operators must back up their database before migration, test the migration path on a staging instance, and verify that all historical transaction data remains queryable after the upgrade. A failed migration can corrupt the transaction history required for audits and reconciliation. Ensure your disaster recovery plan includes a rollback procedure for the Anchor Platform database.
05
SDK Lifecycle and Client Library Compatibility
The Anchor Platform depends on Stellar SDKs for transaction building, XDR parsing, and Horizon interaction. As official SDKs reach end-of-life and transition to community-maintained or auto-generated alternatives, anchors must track which SDK versions their Anchor Platform release supports. Building on an unsupported SDK exposes the platform to unpatched vulnerabilities and protocol incompatibility. Plan SDK migration work in parallel with Anchor Platform upgrades to avoid dependency deadlock.
06
Partner Communication and Ecosystem Coordination
Wallet providers and exchange partners that integrate with an anchor's SEP endpoints need advance notice of Anchor Platform upgrades that change API behavior, rate limits, or supported features. Establish a communication cadence—including a testnet sandbox and a documented deprecation window—so partners can validate their integrations before you upgrade production. A surprise breaking change can damage business relationships and cause cascading failures across the Stellar on/off-ramp network.
ANCHOR PLATFORM AND SDK INTEGRATION RISK
Compatibility and Risk Matrix
Operational risks and compatibility concerns for teams integrating with the Stellar Anchor Platform, Business Integration SDKs, and related API surfaces.
| Area | What changes | Who is affected | Action |
|---|---|---|---|
Anchor Platform API versioning | Breaking changes to REST API endpoints, request schemas, or authentication flows between platform releases. | Anchors, wallets, and payment operators calling the platform directly. | Pin integration tests to a specific Anchor Platform release tag. Review changelogs before upgrading. Verify against canonical source. |
Custody integration interface | Changes to the abstracted custody backend interface (e.g., signing, key storage) that anchors implement. | Anchors integrating with external HSMs, MPC providers, or internal key management systems. | Audit the custody adapter implementation against the latest interface specification. Test transaction signing and key lifecycle operations after any platform upgrade. |
SEP compliance (SEP-6, SEP-24, SEP-31) | Anchor Platform behavior may drift from the canonical Stellar Ecosystem Proposal standards it implements. | Wallets and services relying on standard SEP interactions for deposit/withdrawal. | Continuously validate platform behavior against the official SEP specifications, not just against the platform's own documentation. Monitor SEP repositories for clarifications. |
Business SDK deprecation | Official Stellar SDKs (Java, Go, etc.) reaching end-of-life, shifting maintenance to community forks or auto-generated libraries. | Backend services and anchors built on deprecated SDKs for transaction building and Horizon queries. | Migrate to a supported SDK or auto-generated client. Review the SDK Deprecation Schedule. Chainscore can assist with migration planning and code review. |
XDR schema evolution | Changes to Stellar's canonical XDR definitions break auto-generated SDK code, causing silent transaction parsing failures. | Any service building or parsing transactions using a compiled SDK. | Pin SDK versions and regenerate clients from the exact XDR commit hash used by your target Stellar Core version. Implement integration tests that decode real Mainnet transactions. |
Horizon API deprecation | Horizon endpoints, query parameters, or response fields deprecated and removed, breaking data retrieval for the Anchor Platform. | Anchors using Horizon for ledger state, transaction history, or account detail. | Monitor the Horizon Deprecation and Migration Guide. Run integration tests against a testnet Horizon instance running the target version before upgrading production. |
Transaction fee and surge pricing | Dynamic fee auction and Soroban resource fees cause transactions submitted by the platform to fail or get stuck during congestion. | Anchors and automated payment operators submitting time-sensitive transactions. | Implement dynamic fee estimation based on recent ledger close data. Build retry logic with fee bumping for critical operations. Review the Stellar Fee Model guide. |
Network upgrade activation | A new protocol version activates, altering transaction validity rules or Soroban resource pricing before the Anchor Platform is updated. | All anchors and integrated services. | Run a full integration test suite against Futurenet and Testnet well before the Mainnet activation date. Chainscore offers upgrade readiness reviews to validate this process. |
ANCHOR PLATFORM OPERATIONS
Release Upgrade and Maintenance Checklist
A structured checklist for anchors and payment operators to validate readiness before upgrading the Stellar Anchor Platform or its supporting SDKs. Each item identifies a critical operational check, the risk it mitigates, and the signal that confirms safe upgrade completion.
What to check:
- Diff the OpenAPI specifications between the current and target Anchor Platform versions.
- Identify any deprecated, renamed, or newly required fields in the
/sep6,/sep24, and/sep31endpoints. - Confirm that the new version does not alter the expected behavior of callback endpoints your business server implements.
Why it matters: A breaking API change can silently corrupt transaction parsing or cause wallet integrations to fail, leading to stuck withdrawals or deposit failures.
Readiness signal: A successful run of your integration test suite against a staging deployment of the new version, with all wallet partner flows passing.
resource-links
STELLAR OPERATIONS
Canonical Resources
Primary sources for teams operating Stellar Anchor Platform services, SEP-based on/off-ramp flows, and business-facing Stellar SDK integrations. Use these resources to validate API behavior, compliance flows, release status, and client compatibility before production changes.
Chains We Build On
Looking to build on a specific blockchain?
We build smart contracts, DeFi applications, wallets, tokenization platforms, and blockchain infrastructure across the major ecosystems teams choose today. That includes Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Solana, Sui, Aptos, Hedera, Stellar, and NEAR, with support for additional EVM and non-EVM networks based on your product requirements.
EVM ecosystems
- Ethereum
- Arbitrum
- Optimism
- Polygon
- Avalanche
- Cronos
Non-EVM ecosystems
- Solana
- Sui
- Aptos
- Hedera
- Stellar
- NEAR
Additional ecosystems
- Polkadot
- Cosmos
- TON
- Cardano
- Algorand
- Tempo
Also available for Base, appchains, custom EVM networks, and cross-chain product architecture.
ANCHOR INTEGRATION FAQ
Frequently Asked Questions
Common operational and integration questions for teams running the Stellar Anchor Platform or building against its APIs.
The Anchor Platform implements the SEP-24 interactive standard for hosted deposit and withdrawal flows. The platform acts as the anchor server, exposing the /interactive endpoint. Your client application must:
- Initiate the flow by POSTing to
/transactions/deposit/interactivewith the required KYC fields and asset details. - Handle the interactive URL returned in the response. This URL must be opened in a secure browser context for the user to complete identity verification and provide off-chain payment details.
- Poll the transaction endpoint
GET /transactionusing theidorstellar_transaction_idto track status changes (pending_user_transfer_start,completed,error).
Why it matters: Incorrectly handling the interactive URL (e.g., opening it in an in-app WebView without proper session management) is a common cause of failed flows. The anchor's session cookie must be preserved.
Readiness signal: A successful end-to-end test on Testnet where a user completes KYC, submits a bank wire, and the transaction reaches completed status.
Trusted by Industry Leaders
Delivering blockchain solutions for 5+ years.
We have partnered with 50+ leading DeFi protocols, NFT ecosystems, and fintech innovators to build secure, scalable, and capital-efficient blockchain products.
Selected Partners & Clients
“I've been working with Chainscore Labs for last 3+ years, they've consistently delivered with strong ownership across multiple projects. The team is reliable and detail-oriented.”
L
Lee Erswell
CEO, Telos Foundation
how to get started
How to get started?
If you're looking for blockchain integration, ChainScore Labs has 5+ years of experience helping teams build and integrate exchanges, wallets, smart contracts, tokenization solutions, and protocol-connected products, we can help you choose the right path, integrate securely, and get to production faster. Our team consists of experienced blockchain developers and architects who can help you with your blockchain integration needs.
01
Exploration & Strategy
Define your product goals and choose the right blockchain architecture for your use case.
02
Architecture & Design
Design the smart contracts, tokenomics, and security parameters of your system.
03
Development & Integration
Build and integrate with wallets, oracles, and front-end dApps for a seamless experience.
04
Security & Launch
Comprehensive audits followed by a risk-managed mainnet deployment to protect your users.
Explore More Solutions
Discover our
blockchain development services.
We build production-grade blockchain solutions for top-tier projects across DeFi and Web3.
Book a Call
Start a build
Need a blockchain engineering team?
Send the project context and we will respond with next steps, scope questions, and a practical path to delivery.