Skip to main content
Version: 1.0.1

Channels

Payment channels connect Dimebia to external payment providers. This guide covers configuring and managing payment channels.

Overview

A payment channel represents a connection to an external payment service provider (PSP) such as Stripe, PayPal, or a bank. Channels determine how payments are processed and settled.

Supported Channels

ChannelTypeDescription
StripeOnlineCredit/debit cards, Apple Pay, Google Pay
PayPalOnlinePayPal wallet payments
Bank TransferOfflineWire transfers, ACH, SEPA
AlipayOnlineChinese payment method
WeChat PayOnlineChinese payment method
Credit CardDirectDirect credit card processing

Configure a Channel

POST /api/channel/modify

Request Body

FieldTypeRequiredDescription
idLongNoChannel ID (omit for new channel)
nameStringYesChannel name
codeStringYesUnique channel code
typeStringYesONLINE or OFFLINE
currencyStringYesSupported currency codes
countryStringYesCountry code (ISO 3166-1 alpha-2)
apiKeyStringNoAPI key for the provider
apiSecretStringNoAPI secret for the provider
webhookSecretStringNoWebhook verification secret
stateBooleanYesActive/inactive

Example

curl -X POST http://localhost:8080/api/channel/modify \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <YOUR_TOKEN>" \
-d '{
"name": "Stripe Production",
"code": "stripe_prod",
"type": "ONLINE",
"currency": "USD,EUR,GBP",
"country": "US",
"apiKey": "sk_live_...",
"apiSecret": "whsec_...",
"state": true
}'

List Channels

GET /api/channel/list

Channel Routing

Dimebia supports automatic channel routing based on:

  • Currency: Route to channels that support the transaction currency
  • Country: Route to channels available in the customer's country
  • Amount: Route high-value transactions to specific channels
  • Availability: Automatically failover to backup channels

Best Practices

  1. Test Mode: Always configure test/sandbox channels before production
  2. Webhooks: Configure webhook endpoints for real-time status updates
  3. Monitoring: Set up alerts for channel failures and high latency
  4. Fallback: Configure at least one backup channel for critical payment flows