paygent-carrier

What problem does it solve?

Paygent mobile carrier payments for au/d払い/SB+Y!mobile are complex to integrate, especially when you need correct request types, career-type mapping, redirect handling, and both one-time and subscription billing flows in WooCommerce.

Core Features & Use Cases

• Unified gateway for one-time + subscription: Supports both Paygent carrier payments (telegram_kind 100/101/102/104/109) and subscription payments (telegram_kind 120/121/122/124/125/126) under a single gateway ID.
• career_type based routing and meta consistency: Converts checkout POST career_type values (04/05/06) into required numeric carrier types (4/5/6) and aligns order meta behavior for correct authorization, cancellation, and capture flows.
• Deterministic request/response parameterization: Ensures correct usage of amount (Paygent amount vs WooCommerce payment_amount), required callback URLs, and the redirect_url/redirect_html outcomes required by carrier flows.
• Status and cancellation logic mapping: Provides payment_status transition handling and carrier-specific cancelable status sets to keep order state consistent.

Quick Start

Use the paygent-carrier skill to generate a WooCommerce gateway integration plan for carrier payments by career_type for both one-time and subscription orders.