## How it works

Merchant administration and payment processing use distinct access contexts. An administrative API client must not reuse a public checkout credential.

## Implementation

A SpicePay Dashboard SDK package and administrative route contract have not been verified. Keep automated changes out of a production account until SpicePay supplies the supported API release and credential scope. The dashboard guides explain the operational areas: shops, connectors, routing, checkout, reporting and team. Use the confirmed Payment API for payment-facing integrations.

## In this area

- Credentials
- Shops and processors
- Routing and availability
- Risk and controls
- Reporting
- Account and team
- Areas without a Rust method

## Related guides

- [Dashboard API](/docs/sdks/typescript/dashboard-api/overview/)
