Environments

The SDK is published as two separate builds — one for sandbox (testing) and one for production (live payments). The environment is determined at build time, so there is no environment flag to set in your configuration.

Use the correct script tag for your environment:

• Sandbox: collana-pay.sandbox.umd.js — all provider SDKs load in test/sandbox mode
• Production: collana-pay.production.umd.js — all provider SDKs load in live mode

Provider-Specific Notes

PayPal

• Sandbox: Create a sandbox app in the PayPal Developer Dashboard. Use the sandbox clientId in options.clientId. Transactions are simulated.
• Production: Create a live app and use the production clientId. Transactions are charged.

Google Pay

• Sandbox: No real charges. Any test card number is accepted. The SDK automatically uses the Google Pay TEST environment.
• Production: Requires approval from the Google Pay Business Console. The gatewayMerchantId must be your production merchant account name.

Apple Pay

Domain validation is required in both environments:

• Sandbox: Register your domain in your Apple Developer account and use Apple sandbox certificates. Testers must have sandbox Apple ID credentials.
• Production: Register and verify your domain in production Apple Developer settings. Obtain a Merchant Identity Certificate.

Your Apple Pay validateMerchantUrl backend endpoint must work in both environments.

Amazon Pay

• Sandbox: Obtain a sandbox merchant ID and sandbox public key ID (SANDBOX- prefix) from the Amazon Pay developer console. Use region: 'EU' (or the appropriate region) and the sandbox endpoint.
• Production: Use the live merchant ID and public key ID without the SANDBOX- prefix.

Adyen

• Sandbox: Use a test API key (test_...) and test clientKey from the Adyen Customer Area. The Adyen Drop-in components point to the test gateway endpoint automatically.
• Production: Use a live API key and live clientKey. The live environment has a different endpoint URL format (live_...).

Braintree

• Sandbox: Use a sandbox_xxx_yyy tokenization key from the Braintree Control Panel sandbox account.
• Production: Use a production_xxx_yyy tokenization key from the live Braintree account.

Computop

• Sandbox / Production: The Computop gateway URL changes between environments. Configure the correct endpoint in your backend. The client-side SDK options do not differ — environment selection is handled by the Computop server configuration.

Mollie

• Sandbox: Use a test API key (test_...) from the Mollie Dashboard. Test payments are not charged.
• Production: Use a live API key (live_...).

Revolut

• Sandbox: Use a pk_sbox_... public token.
• Production: Use a pk_live_... public token.

Stripe

• Sandbox: Use a pk_test_... publishable key. Test cards from the Stripe testing docs work with the Express Checkout Element.
• Production: Use a pk_live_... publishable key.