Discussions
Using Sygna APIs in a non‑finance context (fashion ecom) – best practices?
Hi, I’m Alex and I mostly work on small online projects around secondhand fashion and online thrift store clothes, so I’m new to travel rule and VASP integrations but curious about using Sygna’s standards in a broader ecosystem.
I have a couple of questions:
Are there recommended best practices or minimal implementation patterns for a very small platform that might someday add a wallet/credits feature but currently only handles regular ecommerce payments?
Is there any lightweight way to start experimenting with Sygna’s APIs (sandbox examples, test flows, sample apps) without needing a full compliance setup from day one?
Finally, are there common architectural “gotchas” you see when developers later bolt on compliance and data‑exchange standards to an existing app, especially something originally built just for selling online thrift store clothes?
Any pointers to specific docs, examples, or reference implementations that fit a small, non‑financial‑native project would be really appreciated.
