paygent-carrier

Integrate Paygent mobile carrier payments into WooCommerce with telegram kinds and routing.

Updated Sep 22, 2024
One-click install
npx skills add https://github.com/WordPressBugBounty/plugins-woocommerce-for-japan --skill paygent-carrier
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paygent-carrier
Source: https://github.com/WordPressBugBounty/plugins-woocommerce-for-japan/tree/main/woocommerce-for-japan/.claude/skills/paygent-carrier
Command: npx skills add https://github.com/WordPressBugBounty/plugins-woocommerce-for-japan --skill paygent-carrier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about paygent-carrier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate Paygent mobile carrier payments into WooCommerce?▼

Paygent mobile carrier payments integrate into WooCommerce by mapping checkout career_type values (04/05/06) to numeric types (4/5/6) and using specific telegram_kind values for authorization, capture, and cancellation flows.

Does Paygent carrier payment support WooCommerce Subscriptions billing?▼

Yes, Paygent carrier payment supports WooCommerce Subscriptions by using telegram_kind 120-126 for subscription billing and persisting the running_id parameter across recurring cron tasks.

Why does my Paygent carrier payment use the wrong amount parameter in WooCommerce?▼

Paygent carrier payments require using the Paygent amount parameter instead of the default WooCommerce payment_amount to ensure the request payload matches the expected gateway specification.

What redirect URLs are required for Paygent au, d払い, and SoftBank carrier checkout?▼

Paygent carrier checkout requires return_url, cancel_url, and pc_mobile_type parameters, plus optional open_id, to manage redirect_url and redirect_html outcomes for au, d払い, and SoftBank/Y!mobile flows.

Can I use Paygent carrier payments with PHP 8.1 and older WordPress versions?▼

No, Paygent carrier payments require WooCommerce 9.0+, WordPress 6.7+, and PHP 8.2+ to ensure compatibility with the gateway integration and subscription cron task handling.

How does career_type mapping work for Paygent carrier payment cancellation?▼

Career_type mapping converts POST values (04/05/06) into numeric carrier types (4/5/6) and applies carrier-specific cancelable status sets to maintain consistent order state during cancellation.