Production Environment Configuration
After passing sandbox environment test acceptance, you have obtained production environment API access permissions. Now you need to configure production environment parameters and complete merchant onboarding.
Application Security Settings
You have passed sandbox environment acceptance testing, now you can configure production environment application security settings:
-
Enter Security Configuration Page
- Go to application details page → “Payment integration” tab
- View “Security Key”, “Webhook”, and “IP Whitelist” configuration areas
-
Configure Authentication Keys
- Auth Type: Select authentication method (e.g., hmac-sha256)
- Auth Secret: Click “Auto-generate” to automatically generate key, or manually enter custom key
- Save the generated key securely, used for API request signing
-
Configure Webhook Signing (Optional)
- Sign Type: Select signing method (e.g., API KEY)
- Webhook sign secret: Click “Auto-generate” to automatically generate signing key
- Used to verify authenticity of Webhook notifications
-
Configure IP Whitelist (Optional)
- Enter IP addresses allowed to access API
- Supports adding multiple IP addresses
- Click “Add” to add to whitelist
- Securely Store Keys
- Use environment variables or key management services to store sensitive information
- Do not hardcode keys in code or commit to code repository
- It is recommended to use AWS Secrets Manager, HashiCorp Vault and other key management tools
Key Security:
- If key leakage is discovered, immediately reset the key in Copilot
- We support key rotation, old keys will be retained for a certain period to avoid affecting production transactions during switching
- It is recommended to regularly change keys to improve security
Apply for Formal Merchant
Operating Entity: Payment service provider operates for you
Contact your payment service provider to apply for a formal merchant for your application and activate payment functions:
-
Submit Merchant Information
- Business registration certificate
- Business owner identification
- Business scenario description
- Expected transaction volume
-
Activate Payment Channels
- Service provider will activate corresponding payment channels according to your business needs
- Some payment channels may require additional qualification review
- Service provider will assist you in completing channel merchant application and parameter configuration
-
Obtain Merchant Parameters
- After service provider completes configuration, you will obtain formal merchant number and payment parameters
- These parameters will be automatically synchronized to Copilot’s production environment configuration
Merchant review time varies by payment channel, usually takes 1-3 business days. You can continue to improve code and documentation during the review period.
Configure Business Parameters
Operating Entity: Payment service provider operates for you
Service provider will complete business configuration according to your business needs:
General Configuration:
- Transaction Rules: Set single transaction limit, daily transaction limit, etc.
- Refund Rules: Configure refund time limit, partial refund rules, etc.
- Risk Control Rules: Set risk transaction identification and interception strategies
- Settlement Configuration: Configure settlement cycle, settlement account, etc.
Tapro Application Exclusive Configuration (if using Tapro):
- Store Configuration: Create stores and configure store information
- Terminal Binding: Bind payment terminals to formal merchant
- Cashier Settings: Configure cashier accounts and permissions
- Tapro Function Configuration:
- Tip settings
- Tax configuration
- Settlement related settings
- Other function switches and parameters
Checklist
After completing production environment configuration, please confirm the following items:
- ✅ Obtained production environment parameters and stored securely
- ✅ Configured IP whitelist and other security policies
- ✅ Configured production parameters into your system
- ✅ Formal merchant has been activated and obtained merchant parameters
- ✅ Payment channels have been activated and connectivity tested
- ✅ (If using Tapro) Business configuration has been completed
Complete! After completing production environment configuration, you can proceed with Go-Live.
FAQ
When can production environment parameters be obtained?
After passing sandbox environment test acceptance, you can configure and obtain production environment parameters in the “Payment Integration” tab of the application details page.
Among them, the formal merchant number needs to be obtained after the service provider completes merchant registration for you. Other development parameters (such as authentication keys, Webhook signing, etc.) can be configured by yourself.
Does test environment code need to be modified?
No need to modify code logic, just switch environment variables from test parameters to production parameters.
How to reset production environment keys?
Regenerate keys in the “Payment Integration” tab of the application details page. The system supports key rotation, old keys will be retained for a period of time to ensure smooth switching.
How long does merchant review take?
Merchant review time varies by payment channel, usually takes 1-3 business days. Please consult your payment service provider for specific time.
Can multiple payment channels be used simultaneously?
Yes. You can activate multiple payment channels according to business needs, the system will automatically route to the corresponding channel according to transaction type.
Can testing be done in production environment?
Small amount real transaction testing can be done, but please note that all transactions in production environment will incur real fees. It is recommended to refund promptly after testing is complete.