# Developer Guide

Set up your development access and prepare to build with Deluxe APIs.

This guide walks you through obtaining Sandbox access, requesting API credentials, and preparing your development environment before building with Deluxe APIs.

### Before You Begin

The Deluxe Sandbox environment allows developers to explore APIs, build integrations, and validate use cases before requesting production access.

Sandbox access is intended for development and testing only. All credentials, data, and transactions in the Sandbox are non-production and should not be used for live business activity.

#### Who Can Request Sandbox Access?

Sandbox access is available to:

- ISVs
- Technology partners
- Solution providers
- Development teams evaluating Deluxe APIs
- Organizations building future integrations with Deluxe Merchant Services


A commercial agreement with Deluxe is not required to access the Sandbox environment.

#### What You'll Need

Before requesting access, ensure you have:

- A valid email address
- A basic understanding of your intended integration use case
- Technical resources available to begin development and testing


Having this information available helps streamline the onboarding process.

#### What You Can Do in Sandbox

The Sandbox environment allows you to:

- Explore available APIs
- Review API documentation and specifications
- Test authentication and API connectivity
- Develop and validate integration workflows
- Evaluate API capabilities before moving to production


Sandbox environments use test credentials and non-production data.

Access to the Sandbox does not provide access to production APIs or production credentials.

### Get API Credentials and Sandbox Access

Sandbox credentials are issued by the Deluxe Implementations Team.

To request Sandbox access and API credentials, complete the Deluxe Contact Form.
  
Include:

- Business name
- Account information
- Intended use of the integration


You will receive the following values:

| Credential | Format | Purpose |
|  --- | --- | --- |
| Client ID | String | Identifies your application. Used to obtain OAuth bearer tokens. |
| Client Secret | String | Paired with the Client ID to obtain OAuth bearer tokens. |
| Access Token (`partnerToken`) | GUID | Identifies the merchant the request is made on behalf of. Sent as the `partnerToken` header on API requests. |


#### Scope

Sandbox credentials work only in the Sandbox environment.

Production credentials are issued separately once your integration has been tested and reviewed by your implementation specialist.

The Access Token is merchant-specific. If you process on behalf of multiple merchants, each merchant receives a unique Access Token.

#### Security

- Store the Client ID and Client Secret server-side only, in a secrets manager or environment variables.
- Never include credentials in client-side code, mobile applications, or source control.
- Generate and use bearer tokens server-side only.
- If a Client Secret is exposed, contact the Implementations Team to request new credentials.


### Verify Your Access

After obtaining credentials and completing authentication setup, verify your access by submitting a test payment in Sandbox.

See [**Authenticate**](/products/merchant-services/developer-resources/developer-guide/authenticate) for a complete example request and expected response.