Compliance & Data
Developer Obligations
Pre-launch
Section
Compliance & Data
Documentation category
Type
Guide
Technical reference
Summary
What an approved SwssChain developer is responsible for: credential handling, permitted use, and the conditions under which access is withdrawn.
SWSS Foundation Notice

This documentation is restricted to authorised members of the SWSS Developer Community. Access is granted exclusively through SWSS DevHub, after KYB and SWSS Foundation approval.

All SwssChain GitHub repositories are private. Significant updates are currently deploying across the full SWSS Ecosystem. SDK and API specifications are subject to change at any time in accordance with security requirements and SwssChain Foundation governance decisions.

Join SWSS DevHub →Have a question? Use the Need Help? button below.
SDK Update Notice

SWSS SDK v2.1 is deploying across the ecosystem. API signatures may change during this period. Ensure your integration uses the latest schema from SWSS DevHub.

Article Content

Access to SwssChain is granted to an identified entity after KYB and SWSS Foundation approval. This page sets out what that entity is responsible for afterwards. The binding terms are the developer agreement executed at approval; this is a plain summary of it and does not replace it.

Credentials

  • Credentials identify you. An API key and the endpoints issued with it are tied to the approved account, are auditable, and are attributable in the event of misuse.
  • Never expose them. Not in client-side code, not in a browser bundle, not in a repository, not in a URL that may be logged. See Authentication and API Keys.
  • Never share or resell them. Providing onward access to a party the Foundation has not approved defeats the admission process and is grounds for withdrawal.
  • Separate keys per environment. Development, staging and production, each with its own rate allocation.
  • Rotate and revoke. A credential that may have been exposed is rotated immediately, from the DevHub dashboard.

Permitted Use

  • Integration and operation of the application described in the approved application. A materially different use is a new application, not an extension of the existing one.
  • No attempt to circumvent rate limits, endpoint scoping, or the tier your approval covers.
  • No use that would place settlement activity outside the jurisdictions the network is scoped to.
  • No representation of yourself as SWSS Fintech Limited, the SWSS Foundation, or an operator of the network.

Keeping Verification Current

Approval is granted to a verified entity, and it follows that entity. KYB that lapses, a change of control, or a change in the jurisdictions you operate from returns the account to review. Notify through SWSS DevHub before the change takes effect rather than after, a lapse discovered by the Foundation is handled less gracefully than one you declared.

Withdrawal

Access may be withdrawn for lapsed verification, for the misuse above, or where continued access would place the network outside its regulatory scope. Withdrawal stops new credential issuance and revokes existing keys; it does not alter settlement records already on chain, which are permanent by design and cannot be removed by anyone including the Foundation.

Settlement is permanent

A DEED-1 settlement cannot be deleted, reversed or amended by the Foundation, by a validator, or by you. Correction happens by a subsequent settlement that supersedes it, and both remain visible. Design your integration on the assumption that anything you settle is permanent and public.

Reporting

Security issues go through Reporting Vulnerabilities, not the public tracker. Suspected misuse of a credential, yours or another party's, is reported through SWSS DevHub immediately.

Next Steps

Frequently Asked Questions
6 questions
Can I let my own customers use my API key?

No. Onward access to a party the Foundation has not approved defeats the admission process and is grounds for withdrawal. Your application may serve them; your credential may not be handed to them.

My use case has changed since approval. Do I reapply?

A materially different use is a new application, not an extension. Raise it through SWSS DevHub before you build against it.

A key may have been exposed. What now?

Rotate it immediately from the dashboard, revoke the old one, and report the exposure through SWSS DevHub: including if you are unsure.

If my access is withdrawn, what happens to what I settled?

Nothing. Settlement records are permanent and cannot be removed by anyone, including the Foundation. Withdrawal stops new credential issuance and revokes keys.

Can a settlement be reversed if I make a mistake?

No. Correction happens by a subsequent settlement that supersedes the first, and both remain visible. Design on the assumption that anything you settle is permanent and public.

Where do I report a security issue?

Through Reporting Vulnerabilities, never the public tracker.