Moving Configuration to Production

Your sandbox and production accounts are two separate accounts on the same system. They share nothing: not API keys, not users, not stored tokens, and not configuration. When your production account is created, it starts empty. This page lists what you can import from sandbox in one step and what you need to set up again.

Import Sandbox Data

The portal can copy three kinds of configuration from your sandbox account into your production account.

Log in to the PCI Booking portal with your production account. The import option is not shown when you are logged in to a sandbox account.
Go to Booker Settings > Import sandbox data.
Enter the username and password of your sandbox account and click Login.
Tick the items to import, then click Continue and confirm.

What is imported	Notes
Language settings (custom translations)	Each selected language is copied as is. Any translation already in production for that language is replaced. Where the sandbox has no override for a label, production falls back to the default text. See Custom Translations.
Stylesheet settings	Each selected stylesheet is copied by name. A production stylesheet with the same name is overwritten. See Stylesheets.
PCI Shield profile settings (target profiles and their content filters)	Each selected profile is copied by name. A production profile with the same name is overwritten. See Target Profiles.

If a profile references a client certificate, the certificate file is copied to your production account under the same name, but the copied profile is saved without the certificate attached. Open the profile in production and select the certificate again. See Client Certificates.

The import requires the Can manage resources permission on your production user. You can run it more than once, for example after changing a stylesheet in sandbox.

Set Up Again in Production

Everything not listed above must be created in the production account. Most of it is done in the portal; a few items go through our support team.

Configuration	Where	Notes
API keys and users	Portal, Manage Users and API Keys	Create your production API key first. Sandbox keys do not work against the production account.
PSP credentials	Portal or API, PSP Credentials	Use your PSP’s live credentials. Sandbox accounts route to PSP test environments, production accounts route to PSP live environments.
Payments Library credentials (Apple Pay, Google Pay, PayPal, BankPay, UPI)	Portal or API, Payments Library Credentials	Live credentials only: PayPal live client ID and secret, Google Pay production merchant ID, Apple Pay certificates registered for your production domain.
Client certificates	Portal, Client Certificates	Certificates referenced by imported profiles are copied; any others must be uploaded again.
Security settings (IP restrictions, callback URL whitelist, card display permissions)	Portal, Security Settings	Add your production server IPs and production callback URLs.
CVV store rules	Portal, CVV Retention Policy	Set the account-wide default again.
Booker settings (brand name, logo, contact and billing details)	Portal, Booker Settings
General customization and email templates	Portal, General Customization and Email Templates	Not part of the import.
Card By Link templates	Portal, Card By Link Templates	Not part of the import.
White label email domain	Portal plus support, White Label Email Domain	DNS records stay valid; the setting and the verification with support are per account.
3DS merchant details	Support, 3DS Merchant Setup	Merchant details are registered per account. Ask support to register them on the production account.
Token Replacement in Response and Tokenization on Request endpoints	Support	The dedicated endpoint, its DNS record and SSL certificate are set up per account. Tell support when you are ready to move them. See Tokenization on Request.
Third-party permissions	API, Third-Party Permissions	Associations are between production accounts and must be created again.
Virtual card provider credentials	API, Virtual Card Issuance	Live provider credentials.

What Does Not Move

Card tokens. Tokens created in sandbox stay in sandbox. A sandbox token cannot be used with a production API key, and there is no transfer. If you have real cards in sandbox that you need in production, contact support@pcibooking.net.
Transaction history and logs. Reports and logs are per account.
Sandbox usage limits. Production accounts have no monthly operation allowances.

In Your Code

The base URL does not change. Replace the sandbox API key with the production API key, and replace any sandbox-only values in your requests: PSP credential names, profile names if you renamed them, success and failure URLs pointing at test pages, and callback URLs. Then run the Go-Live Checklist. Your sandbox account stays open. Keep using it for development and for testing new features before you change production.

Testing & Going Live. Sandbox behaviour, test cards and the go-live checklist.
Create an Account. How sandbox and production accounts are created.
Authentication. How API keys work.

Start Here

Getting Started

Concepts

Guides

Capture Cards

Payments Library

Manage Tokens

Use Tokens

Account Configuration

Additional Functions

Reference

Support

Moving Configuration to Production

Import Sandbox Data

Set Up Again in Production

What Does Not Move

In Your Code

​Import Sandbox Data

​Set Up Again in Production

​What Does Not Move

​In Your Code

​Related

Import Sandbox Data

Set Up Again in Production

What Does Not Move

In Your Code

Related