.env.example•4.36 kB
# payware MCP Server Configuration
# Copy this file to .env and configure for your partner type
# =============================================================================
# PARTNER TYPE CONFIGURATION (Required)
# =============================================================================
# Specify your partner type: merchant, isv, or payment_institution
# This determines which tools are available and how authentication works
PAYWARE_PARTNER_TYPE=merchant
# =============================================================================
# COMMON CONFIGURATION (All Partner Types)
# =============================================================================
# Partner ID from payware dashboard (Required)
PAYWARE_PARTNER_ID=YOUR_PARTNER_ID
# Path to private key files - relative to project root (Required)
# Choose the appropriate private key path for your partner type and environment
PAYWARE_SANDBOX_PRIVATE_KEY_PATH=keys/sandbox-your-partner-private-key.pem
PAYWARE_PRODUCTION_PRIVATE_KEY_PATH=keys/production-your-partner-private-key.pem
# Sandbox base URL (Optional - defaults to https://sandbox.payware.eu/api)
PAYWARE_SANDBOX_URL=https://sandbox.payware.eu/api
# Production base URL (Optional - defaults to https://api.payware.eu/api)
PAYWARE_PRODUCTION_URL=https://api.payware.eu/api
# =============================================================================
# ISV-SPECIFIC CONFIGURATION (Only when PAYWARE_PARTNER_TYPE=isv)
# =============================================================================
# OAuth2 Client ID from payware dashboard (Required for ISV)
PAYWARE_OAUTH_CLIENT_ID=YOUR_CLIENT_ID
# OAuth2 Client Secret from payware dashboard (Required for ISV)
PAYWARE_OAUTH_CLIENT_SECRET=YOUR_CLIENT_SECRET
# Default merchant ID to use when not specified (Optional for ISV)
PAYWARE_DEFAULT_MERCHANT_ID=DEFAULT_MERCHANT_PARTNER_ID
# =============================================================================
# PAYMENT INSTITUTION SPECIFIC (Only when PAYWARE_PARTNER_TYPE=payment_institution)
# =============================================================================
# Additional configuration for Payment Institutions can be added here
# Currently uses same configuration as merchants
# =============================================================================
# CONFIGURATION EXAMPLES BY PARTNER TYPE
# =============================================================================
# EXAMPLE: Merchant Configuration
# PAYWARE_PARTNER_TYPE=merchant
# PAYWARE_PARTNER_ID=MERCHANT123
# PAYWARE_SANDBOX_PRIVATE_KEY_PATH=keys/sandbox-merchant-private.pem
# PAYWARE_PRODUCTION_PRIVATE_KEY_PATH=keys/production-merchant-private.pem
# EXAMPLE: ISV Configuration
# PAYWARE_PARTNER_TYPE=isv
# PAYWARE_PARTNER_ID=ISV456
# PAYWARE_SANDBOX_PRIVATE_KEY_PATH=keys/sandbox-isv-private.pem
# PAYWARE_PRODUCTION_PRIVATE_KEY_PATH=keys/production-isv-private.pem
# PAYWARE_OAUTH_CLIENT_ID=client_abc123
# PAYWARE_OAUTH_CLIENT_SECRET=secret_xyz789
# PAYWARE_DEFAULT_MERCHANT_ID=MERCHANT001
# EXAMPLE: Payment Institution Configuration
# PAYWARE_PARTNER_TYPE=payment_institution
# PAYWARE_PARTNER_ID=PI789
# PAYWARE_SANDBOX_PRIVATE_KEY_PATH=keys/sandbox-pi-private.pem
# PAYWARE_PRODUCTION_PRIVATE_KEY_PATH=keys/production-pi-private.pem
# =============================================================================
# PARTNER TYPE DESCRIPTIONS
# =============================================================================
# merchant: Direct businesses accepting payments
# - Standard JWT authentication (iss=partnerId, aud="https://payware.eu")
# - Transaction creation, status checking, history
# - Tools: create/cancel transactions, check status, view history
# isv: Independent Software Vendors serving multiple merchants
# - OAuth2 + JWT hybrid authentication
# - JWT includes: iss=isvId, aud=merchantId, sub=oauth2Token
# - Multi-merchant management capabilities
# - Tools: merchant onboarding, OAuth2 management, transaction creation for merchants
# payment_institution: Banks, e-wallets, financial institutions
# - Standard JWT authentication (same as merchants)
# - Consumer-facing payment processing and P2P capabilities
# - Tools: consumer payments, P2P transfers, cross-institution transactions