Set up your account | DEUNA Docs

On this page

1. Plan your merchant structure
2. Receive account access
3. Protect your credentials
4. Verify your sandbox
Continue your integration

DEUNA onboarding

Prepare your merchant for development

Confirm your account structure, obtain access, secure each credential, and verify that your sandbox configuration is ready for an integration.

Start account setup Choose an integration

1. Plan your merchant structure#

A merchant represents an independently configured business entity or storefront in DEUNA. Its credentials, transactions, connections, payment settings, and reports are isolated from other merchants.

Create separate merchants when brands, business units, countries, or environments need independent configuration or reporting. Confirm the structure with your DEUNA Technical Account Manager (TAM) before credentials are distributed.

Operational isolationKeep storefront configuration and reporting independent.Credential isolationLimit every credential to its intended merchant and environment.Clear traceabilityInvestigate requests, payments, and operations in the correct merchant context.Independent configurationConfigure providers, routing, fraud controls, and Checkout settings per merchant.

2. Receive account access#

After commercial onboarding, your DEUNA TAM provides or coordinates the access required for each environment:

Item	Used by	Purpose
Merchant ID	Client and server integrations	Identifies the merchant configuration used by the request.
Public API key	Browser or mobile SDK	Initializes supported client-side experiences without exposing a private credential.
Private API key	Merchant backend	Authorizes server-to-server merchant operations.
Admin user	Authorized merchant operators	Provides role-based access to configuration and operations.

Authentication and API keysSee where each key belongs and how merchant requests are authorized.DEUNA AdminLearn where operators investigate orders and manage merchant operations.Roles and permissionsAssign only the Admin access required for each responsibility.

3. Protect your credentials#

Store private API keys in a secrets manager or protected server environment.
Never include a private key in browser or mobile code, public repositories, screenshots, or logs.
Keep sandbox and production values separate and label them clearly.
Give Admin users individual accounts and the minimum required role.
Plan key rotation before production launch.

4. Verify your sandbox#

Complete these checks before starting the Quickstart:

The sandbox Merchant ID and public and private keys are available to the correct team members.The sandbox private key is stored only in trusted backend infrastructure.The API base URL, SDK environment, Merchant ID, and credentials all target sandbox.At least one payment connection is enabled for the merchant and test country.A payment strategy can route the selected test payment method.The team has a public HTTPS endpoint available for webhook testing.

Continue your integration#

Choose your integrationCompare ownership, implementation effort, and customer experience.Run the QuickstartProcess a sandbox payment using the verified merchant endpoint.API integration essentialsReview environments, idempotency, timeouts, network requirements, and reconciliation.