Skip to content

Payment Settings Documentation

Menu Location: Settings > Payment Settings (or Payment Gateway Configuration)

Access Level: Administrator and above

Last Updated: 2026-03-01

Overview

The Payment Settings page allows you to configure and manage payment gateway integrations, including Stripe, Authorize.net, and other payment processors. This page is critical for ensuring secure payment processing, managing merchant accounts, and troubleshooting payment issues.

Primary Functions:

  • Configure payment gateway credentials
  • Manage Stripe and Authorize.net settings
  • Test payment processing connections
  • View payment gateway status
  • Configure payment methods accepted
  • Set up recurring billing parameters
  • Troubleshoot payment failures

Page Layout

Header Section

  • Active Payment Gateway: Shows currently configured processor
  • Connection Status: Live/Test mode indicator
  • Test Connection Button: Verify gateway connectivity
  • Save Settings Button: Apply configuration changes

Payment Gateway Tabs

  • Stripe Settings - Stripe configuration
  • Authorize.net Settings - Authorize.net configuration
  • Other Gateways - Additional payment processors
  • General Settings - Universal payment settings

Configuration Sections

Each gateway tab contains:

  • API Credentials input fields
  • Test Mode toggle
  • Accepted payment methods
  • Recurring billing settings
  • Webhook configuration
  • Transaction fee settings

Stripe Configuration

Required Credentials

Publishable Key:

  • Public key for client-side card collection
  • Safe to expose in website code
  • Different keys for test and live mode

Secret Key:

  • Private server-side API key
  • Never exposed to customers
  • Required for processing transactions

Webhook Secret:

  • Validates webhook authenticity
  • Prevents fraudulent webhook calls
  • Auto-generated by Stripe

Configuration Steps

  1. Log in to Stripe Dashboard
  2. Navigate to Developers > API Keys
  3. Copy Publishable Key
  4. Copy Secret Key
  5. Paste into Payment Settings page
  6. Toggle Test Mode (for testing) or Live Mode (for production)
  7. Click "Test Connection"
  8. Verify successful connection
  9. Save settings

Webhook Setup

Purpose: Receive payment event notifications

Setup:

  1. In Stripe Dashboard: Developers > Webhooks
  2. Click "Add Endpoint"
  3. Enter webhook URL (provided on settings page)
  4. Select events to listen for:
    • payment_intent.succeeded
    • payment_intent.payment_failed
    • charge.refunded
    • customer.subscription.updated
  5. Copy Webhook Signing Secret
  6. Paste into Payment Settings
  7. Save

Test Mode vs Live Mode

Test Mode:

  • Use test API keys
  • No real money processed
  • Use test card numbers
  • Test transactions don't affect live data

Live Mode:

  • Use live API keys
  • Real transactions processed
  • Real cards charged
  • Affects actual bank accounts

Best Practice: Test thoroughly in test mode before going live

Authorize.net Configuration

Required Credentials

API Login ID:

  • Your Authorize.net account login ID
  • Found in Authorize.net dashboard

Transaction Key:

  • Secret key for API access
  • Generate in Account > Security Settings

Signature Key:

  • For webhook signature validation
  • Optional but recommended

Configuration Steps

  1. Log in to Authorize.net Merchant Interface
  2. Go to Account > Security Settings > API Credentials
  3. Create new Transaction Key (existing key won't display again)
  4. Copy API Login ID
  5. Copy Transaction Key
  6. Paste into Payment Settings page
  7. Select environment (Sandbox or Production)
  8. Test connection
  9. Save settings

Sandbox vs Production

Sandbox:

  • Test environment
  • No real transactions
  • Use test credentials
  • Test all scenarios

Production:

  • Live environment
  • Real money processed
  • Use production credentials
  • Customer transactions

Common Use Cases

Use Case 1: Initial Payment Gateway Setup

Goal: Configure Stripe for first time

Steps:

  1. Create Stripe account at stripe.com
  2. Complete business verification
  3. Navigate to API keys in Stripe dashboard
  4. Copy test publishable and secret keys
  5. In admin: Open Payment Settings
  6. Select Stripe tab
  7. Toggle Test Mode ON
  8. Paste test keys
  9. Click "Test Connection"
  10. Verify success message
  11. Process test transaction
  12. When ready to go live:
    • Copy live keys from Stripe
    • Toggle Test Mode OFF
    • Paste live keys
    • Test again
    • Save

Use Case 2: Switch Payment Gateways

Goal: Change from Authorize.net to Stripe

Steps:

  1. Set up new gateway (Stripe) alongside existing
  2. Test new gateway thoroughly in test mode
  3. Notify customers of change (if needed)
  4. Choose cutoff date for migration
  5. Switch primary gateway to Stripe
  6. Update customer payment methods if needed
  7. Keep old gateway active for refunds/disputes
  8. Monitor transactions closely for first week
  9. Disable old gateway after transition period

Use Case 3: Troubleshoot Failed Payments

Goal: Diagnose why payments are failing

Steps:

  1. Check gateway connection status
  2. Click "Test Connection" button
  3. If fails:
    • Verify API credentials are correct
    • Check if keys expired or were regenerated
    • Verify test/live mode matches keys
    • Check gateway account is in good standing
  4. Review gateway dashboard for:
    • Account holds
    • Verification issues
    • Service outages
  5. Check webhook configuration
  6. Test with different payment method
  7. Review error logs
  8. Contact gateway support if needed

Use Case 4: Enable New Payment Method

Goal: Start accepting PayPal

Steps:

  1. Set up PayPal business account
  2. Get PayPal API credentials
  3. In Payment Settings: navigate to PayPal tab
  4. Enter client ID and secret
  5. Configure PayPal settings
  6. Test in sandbox mode
  7. Process test transactions
  8. Switch to live mode
  9. Update checkout page to show PayPal option
  10. Monitor transactions

Use Case 5: Update Expired API Keys

Goal: Replace expiring credentials

Steps:

  1. Log in to payment gateway dashboard
  2. Generate new API keys
  3. Copy new keys
  4. In admin: Open Payment Settings
  5. Replace old keys with new ones
  6. Click "Test Connection"
  7. Verify success
  8. Save settings
  9. Monitor next few transactions
  10. Delete old keys from gateway dashboard

Security Best Practices

Credential Management

  1. Never share API keys publicly
  2. Rotate keys annually or after staff changes
  3. Use different keys for test and production
  4. Restrict API key permissions to minimum needed
  5. Monitor for unauthorized access to gateway dashboard

PCI Compliance

  1. Never store credit card numbers in your database
  2. Use payment gateway hosted forms for card collection
  3. Implement SSL/HTTPS on all pages
  4. Regular security audits
  5. Limit staff access to payment settings

Monitoring

  1. Check gateway dashboard daily for issues
  2. Set up email alerts for failed payments
  3. Monitor transaction success rates
  4. Review fraud detection settings
  5. Track refund and chargeback rates

Troubleshooting

Connection Test Fails

Check:

  1. API credentials are correct (copy/paste carefully)
  2. No extra spaces in credential fields
  3. Test/Live mode matches credential type
  4. Gateway account is active and verified
  5. Internet connectivity
  6. Firewall not blocking API calls

Payments Failing But Connection OK

Investigate:

  1. Check customer card details are valid
  2. Review decline codes in gateway dashboard
  3. Verify customer has sufficient funds
  4. Check if fraud filters too strict
  5. Verify billing address matches card
  6. Test with different card

Webhooks Not Working

Check:

  1. Webhook URL is correct and accessible
  2. Webhook secret matches gateway
  3. SSL certificate is valid
  4. Server can receive POST requests
  5. Events are selected in gateway
  6. Review webhook logs in gateway dashboard

Double Charging Customers

Immediate Action:

  1. Stop payment processing
  2. Investigate cause
  3. Issue refunds for duplicates
  4. Fix underlying issue
  5. Notify affected customers
  6. Document incident

Prevention:

  • Implement idempotency keys
  • Add duplicate transaction checks
  • Disable double-click on submit buttons
  • Billing Payments - View payment transaction history
  • Customer Detail - Customer payment methods
  • Orders - Orders requiring payment
  • System Settings - General system configuration

Quick Reference Card

Task Action/Location
Add Stripe keys Stripe tab → Enter keys → Save
Test connection Click "Test Connection" button
Switch to live mode Toggle Live Mode → Update keys → Test → Save
Enable PayPal PayPal tab → Enter credentials → Configure
View connection status Check status indicator at top
Troubleshoot failures Test connection → Check gateway dashboard
Update webhook Enter webhook URL → Copy secret → Save
Change primary gateway Select gateway → Set as primary → Save

FAQs

What's the difference between test mode and live mode?

Test mode uses test API keys and doesn't process real money. Live mode uses production keys and processes actual payments. Always test in test mode first.

Can I use multiple payment gateways?

Yes, you can configure multiple gateways and offer customers choice at checkout, or use different gateways for different purposes.

How often should I rotate API keys?

Annually, or immediately after a staff member with access leaves, or if you suspect keys may have been compromised.

What happens if my gateway credentials expire?

All payments will fail. You must update with new credentials immediately. Monitor expiration dates and update proactively.

Can customers see my API keys?

Publishable keys are visible (safe). Secret keys should never be exposed to customers or in client-side code.

What if I accidentally save wrong API keys?

Fix immediately. Enter correct keys, test connection, save. Your site won't process payments until corrected.

Should I tell customers when switching gateways?

Usually not necessary unless it affects their payment methods or requires them to re-enter card information.

How do I know if my payment gateway is down?

Check status indicator, test connection, review gateway status page, check their Twitter for outage announcements.

Can I process refunds from this page?

No, refunds are processed from Billing Payments or Customer Detail pages. This page is for gateway configuration only.

What's a webhook and why do I need it?

Webhooks notify your system of payment events (success, failure, refund). Essential for automated payment processing and customer notifications.

End of Documentation

For additional help, contact your system administrator or Kiva Logic support.