| Table of Contents |
|---|
Feature Flags
Finance_BillingIntegration
Plugins_CyberSourceBillingProviderIntegration
DevOps Configuration
EKS ConfigMap needs to be updated to add CybersourceUnifiedCheckoutTargetOrigins. The value is the customer portal URLs.
Example: CybersourceUnifiedCheckoutTargetOrigins: https://quantum-preview.customer.seamless.insure,https://pentest-a.customer.seamless.insure
CyberSource Merchant
...
Setups
We use the feature CyberSource Unified Checkout for our checkout functionality so the payment configuration should have Unified Checkout enabled in the CyberSource merchant account.
...
For more details about TMS, please visit this document pagehttps://developer.cybersource.com/docs/cybs/en-us/tms/developer/ctv/rest/tms/tms-overview.html.
...
Billing Provider
...
Setups in Finance
...
Settings
Run Environment: This is actually the API hostname. CyberSource provides a free sandbox environment for testing with the hostname apitest.cybersource.com.
...
CurrencyCode: This is used for the feature “Manage customer registered payment card”. We use the checkout widget of Unified Checkout to collect customer credit/debit cards but the Unified Checkout API requires a currency to be passed in so the currency is retrieved here.
...
Go Live
...
Setups
To transition the Cybersource account from test to live status, also referred to as go live, and process real transactions in Production, we need an activation process. Please follow this guide for the process https://support.cybersource.com/knowledgebase/Knowledgearticle/?code=000002034.