Payment Configs

The Payment Configs page allows administrators to manage detailed payment gateway settings by provider and environment. This is where you enter the actual connection information required to process payments.

Use Payment Providers to register the payment company, such as Stripe or Authorize.Net. Use Payment Configs to configure the detailed payment settings, such as API keys, transaction keys, webhook secrets, environment, domain URL, capture mode, 3DS, and additional metadata.

Overview

Payment Configs are environment-specific payment settings. A single payment provider can have multiple configs, such as one for TEST and another for LIVE.

Config List

The Config List displays payment configurations by provider, environment, display name, merchant key, 3DS status, capture mode, active status, and last updated date.

Top Actions

Config Table

Config Edit

The Config Edit page is used to create or update the detailed payment gateway settings. It is divided into Core, Keys, Advanced, and Summary sections.

Core Section

The Core section defines the provider, environment, active status, merchant key, and display name.

Provider

Select the payment provider to configure. When a provider is selected, the system may automatically show only the fields required for that provider.

Default rules are applied for common providers such as Stripe and Authorize.Net.

Environment

Environment controls whether this configuration is used for testing or live payment processing.

IsActive

If IsActive is set to true, the configuration is available for use. If it is set to false, the configuration is disabled.

Keys Section

The Keys section stores provider-specific authentication and connection values. The labels may change depending on the selected provider.

For Stripe, common key fields may include pk/sk/whsec. For Authorize.Net, common key fields may include LoginId and TransactionKey.

ApiKeyPublic

Enter the public key, publishable key, or API Login ID provided by the payment gateway.

ApiKeySecret

Enter the secret key, private key, or transaction key provided by the payment gateway. This value must be protected and should not be exposed publicly.

WebhookSecret

Enter the webhook signature secret if your payment provider uses webhook verification. This helps confirm that webhook requests are sent from the real payment provider.

EndpointBaseUrl

Enter the base domain used by the payment flow.

Example:
https://your-domain.com
https://your-ngrok-domain.ngrok-free.dev

For local testing, a temporary public URL such as an ngrok domain may be used. For production, use your real website domain with HTTPS.

Advanced Section

The Advanced section controls payment policy, risk, capture, 3DS, settlement, metadata, and internal notes.

Currency

Select the currency used by this payment configuration.

Example:
USD - US Dollar

RiskLevel

RiskLevel is an internal value used to classify the risk policy for this configuration. A lower value usually means lower risk, and a higher value means stricter review may be required.

SettlementDays

SettlementDays defines the expected number of days before funds are settled. This value may depend on the payment provider and merchant account settings.

Enable3DS

Enable3DS controls whether 3D Secure authentication is used. If the field is disabled, the selected provider or environment may not support 3DS in the current configuration.

CaptureMode

CaptureMode controls when a payment is captured.

MetaJson

MetaJson stores additional configuration values that do not have separate input fields. This field must be valid JSON.

{
    "hostedPaymentPageId": "12345678",
    "returnPath": "/ShowPage/iCheckout/Return",
    "cancelPath": "/ShowPage/iCheckout/Cancel",
    "transactionType": "authCaptureTransaction",
    "showReceipt": true
}

Common MetaJson Fields

MetaJson must be valid JSON. If the JSON format is invalid, the payment configuration may not work correctly.

Summary Panel

The Summary panel provides a quick overview of the current configuration state. It shows the selected provider, provider code, environment, and active status.

Use this panel to confirm the selected provider and environment before saving.

Recommended Workflow

1. Open Admin > Payment > Configs.
2. Click + New to create a new configuration, or click Edit to update an existing one.
3. Select the Provider.
4. Select the Environment, such as TEST or LIVE.
5. Set IsActive.
6. Enter MerchantKey and DisplayName.
7. Enter the provider-specific keys in the Keys section.
8. Enter EndpointBaseUrl.
9. Configure Currency, RiskLevel, SettlementDays, 3DS, and CaptureMode.
10. Enter valid MetaJson if additional provider settings are required.
11. Review the Summary panel.
12. Click Save.
13. Test the payment flow before using the configuration in LIVE mode.

Common Use Cases

Important Notes

• Payment Configs store sensitive connection information. Access should be limited to trusted administrators.
• Always test payment settings in TEST mode before enabling LIVE mode.
• Use HTTPS for production EndpointBaseUrl.
• Do not store secret keys in Notes. Use the designated key fields.
• Confirm that MetaJson is valid JSON before saving.
• Do not delete configs that are connected to existing transactions unless you understand the impact.
• If multiple configs exist for the same provider, use clear DisplayName values.

Troubleshooting

Best Practices

• Create separate TEST and LIVE configs.
• Use clear DisplayName values such as Authorize.Net (Test) and Authorize.Net (Live).
• Keep inactive old configs instead of deleting them if transaction history exists.
• Rotate keys periodically according to your payment provider�s security policy.
• Review config values after changing domains, checkout URLs, or webhook settings.
• Limit access to this page because it contains sensitive payment configuration data.

Payment Configs are required for real payment processing. A Provider only defines the payment company; a Config defines how iBoard connects to that company for a specific environment.