Appearance
Introduction
The Spayon Payment Gateway API enables vendors to accept payments securely and efficiently. This guide covers everything a full-stack developer needs: authentication, session creation, callback handling, signature verification, and admin panel configuration.
Environments
Spayon provides two completely isolated environments. Use Staging for development and testing — credentials and data are never shared with Production.
| Component | Production | Staging |
|---|---|---|
| Admin Panel | admin.spayon.io | angular-app-marketplace-staging.s3-website.eu-north-1.amazonaws.com |
| API Base URL | api.spayon.io | staging-spayon-api.eu-north-1.elasticbeanstalk.com |
| Protocol | HTTPS only | HTTP |
| Data Format | JSON | JSON |
| API Version | Unversioned | Unversioned |
Staging is isolated
Staging credentials are completely separate from Production. They cannot be used interchangeably. Do not use the Staging environment for live transactions.
How It Works
The integration follows a straightforward flow:
- Your server authenticates and receives a Bearer token
- Your server creates a payment session for a specific product and customer
- You redirect the user to the hosted Spayon payment page
- After payment, Spayon calls back your server with the result (signed with HMAC-SHA256)
- The user is redirected to your Return URL
See Integration Flow for the full step-by-step breakdown.