v1.0.0 Stable

Payment Gateway Setup

Eventiq supports both automatic and manual payment methods. This guide explains how to configure each gateway and enable it for ticket purchases.

Where to Configure

Go to: Admin → System Settings → Gateways

How to Enable a Gateway

  1. Open Gateways from System Settings.
  2. Click the Edit (pencil) icon for the gateway.
  3. Enter the required credentials.
  4. Set Status to Active.
  5. Save changes and run a test payment.
Note: Eventiq validates payments using the gateway response/return flow. No webhook configuration is required for the built-in gateways.

Supported Gateways

  • PayPal
  • Stripe
  • SSLCommerz
  • Flutterwave
  • Paystack
  • Bank (Manual)

PayPal

To enable PayPal, enter your PayPal REST API credentials:

  • Client ID
  • Client Secret

Testing: Use PayPal Sandbox credentials and accounts to verify the checkout flow.

Stripe

To enable Stripe, use your Stripe keys:

  • Secret Key

Testing: Use Stripe test cards to verify checkout.

SSLCommerz

To enable SSLCommerz, enter your store credentials:

  • Store ID
  • Store Password

Flutterwave

To enable Flutterwave, enter your API keys:

  • Public Key
  • Secret Key

Paystack

To enable Paystack, enter your Paystack credentials:

  • Public Key
  • Secret Key

Bank (Manual Payment)

Bank is a manual payment option. Customers submit payment details (e.g., transaction ID) and the admin reviews and approves the payment.

  • Add Bank name, account number, branch, and instructions shown to customers.
  • Enable the gateway and instruct users to follow the payment instructions during checkout.
  • Admin verifies the payment and confirms the order.

Common Notes

  • Currency: Ensure the selected currency is supported by the gateway.
  • Charges: Configure gateway charge/fee settings if available in the gateway edit screen.
  • HTTPS: Use SSL (HTTPS) on your domain for secure payments.

Troubleshooting

  • If payments fail, re-check credentials and mode (test/live).
  • Confirm your server allows outbound HTTPS requests.
  • Make sure your return/callback URL is reachable publicly.