Skip to content

API Documentation

  • A interactive Swagger documentation is available at app.secpaid.com/swagger.
  • Its content is similar to this documentation.

Developers

We have set up a demo user on the production environment as well as on the development environment. You can use these keys for your integration tests, or you can register and use your own. Please contact us at compute@spacepitch.org for API keys and integration support.

How-to

See the How-To in order to gain information on the integration into your systems making use of the webhooks and callbacks. This makes it easer for your application to get started with SecPaid.

V2 API-Keys

Servers

Important Notes:

  1. Demo Token:
  • The token provided in this documentation (QgSmsCAYt2STTtVBvGGBKjXFEO3roySW) is for demo purposes only.
  • It does not create valid PayLinks. It does create Demo Links from our PSPs. You can cancel or authorize a demo payment in order to integrate it in your software.
  1. Obtaining Receiver Token:

  • In the development environment you ca ret the recipient token for your recipients by yourself in their (recipients account) user settings respectively.

  • If you want to test the SplitLink on the live system, contact us to obtain a receiver's token for one of your receivers after they have registered and verified at SecPaid.

  1. Best Practices:

  2. Always use HTTPS for secure communication.

  3. Store your API key securely and never expose it in client-side code.
  4. Implement proper error handling for different response codes.

  5. Consider implementing retry logic for temporary failures.

  6. Registration Required:

  • To obtain a valid API key for production use, you must register at SecPaid.
  • This process allows us to verify your identity and provide you with secure, personalized API credentials.
  1. Rate Limiting:
  • Be aware that this endpoint is subject to rate limiting.
  • If you exceed the limits, you'll receive a 429 Too Many Requests response.
  • contact us if you want to exceed those limits in your tests
  1. Error Handling:

  • Check the response codes and messages for detailed error information.

  • Common errors include invalid parameters, authentication issues, and server errors.

  1. Testing:

Use the development server (https://app.dev.secpaid.com) for testing before moving to production.

  1. Production Use:

For production use, ensure you have registered and obtained a valid API key from SecPaid. The demo token will not work in production environments.