## How it works

SpicePay connects your application to the payment accounts you already use. A shop keeps its checkout, payment methods and routing together, while the Control Center brings payments from all your shops into one workspace.

## Implementation

Create a payment on your server or from a payment link. SpicePay selects an eligible connector, the buyer completes checkout, and a signed webhook tells your system what happened. Your integration follows the same payment ID throughout this journey. A project groups shops for reporting; a connector links a processor account to a particular shop.

## In this area

- Terms used in these docs
- Where to start

## Platform addresses

| Service | Address |
| --- | --- |
| Control Center | [dashboard.spicepay.net](https://dashboard.spicepay.net/) |
| Payment API | `https://api.spicepay.net` |
| Hosted checkout | `https://checkout.spicepay.net` |

## Start here

- [Create a test payment](/docs/general/quickstart/)
- [Choose your integration](/docs/general/integration-methods/)
- [Create a payment with the API](/docs/payment-api/accept-payments/)
- [Install the WordPress integration](/docs/wordpress/overview/)

## Related guides

- [Connectors](/docs/general/connectors/)
- [Payment lifecycle](/docs/general/payment-lifecycle/)
- [Test and live payments](/docs/general/test-and-live/)
- [Home](/docs/dashboard/overview/)
- [Quickstart](/docs/general/quickstart/)

## Terms

| Term | In SpicePay |
| --- | --- |
| Account | Merchant workspace and team |
| Shop | Storefront with its own checkout, keys and connectors |
| Project | Collection of shops for access and reporting |
| Connector | Shop connection to your processor account |
| Payment | Purchase intent tracked by a stable payment ID |
| Control Center | Merchant dashboard for configuration and operations |