paygent-core

Paygent API requests require SJIS-win/Windows-31J encoding conversion to handle Shift_JIS character codes. This core standardizes parameter construction and encoding transformations to prevent data corruption during WooCommerce gateway transmission.

Centralizing Paygent authentication involves managing merchant_id, connect_id, and connect_password from WordPress options, then generating and appending an SHA-256 hash (hc) for request verification. This approach eliminates duplicate credential management across multiple gateways.

Paygent webhook reception processes incoming notifications at the /wp-json/paygent/v1/check endpoint, handling trading_id mapping and _paygent_order_id references. The system applies common authorization and hash verification logic to validate incoming payment status updates across telegram_kind payment methods.

Yes, Paygent refund and cancel flows use a standardized two-step structure across all payment methods: information inquiry followed by status confirmation, then executing the cancel or refund action. This shared processing framework works across various telegram_kind payment types in WooCommerce.

Yes, PaygentB2BModule integration is fully compatible with WooCommerce 9.0+ and WordPress 6.7+ environments. The core logic enforces these version constraints while managing Paygent request and response parameter construction, encoding conversions, and debug handling.

Paygent hash verification failures often stem from inconsistent SHA-256 hash generation or incorrect parameter ordering during request construction. Centralizing the hc hash attachment and standardizing authentication setup prevents these mismatches across different gateway implementations.