paygent-carrier

Implements Paygent carrier payments in WooCommerce with career_type routing and telegram_kind workflows for subscriptions.

3|2|Updated Jun 9, 2021
One-click install
npx skills add https://github.com/artisanworkshop/Japanized-for-WooCommerce --skill paygent-carrier-artisanworkshop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paygent-carrier
Source: https://github.com/artisanworkshop/Japanized-for-WooCommerce/tree/main/.claude/skills/paygent-carrier
Command: npx skills add https://github.com/artisanworkshop/Japanized-for-WooCommerce --skill paygent-carrier-artisanworkshop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

WooCommerceでauかんたん決済・d払い・ソフトバンクまとめて支払い(B)/ワイモバイルまとめて支払いのキャリア決済を、Paygent経由で都度課金と継続課金(定期購入)として安定稼働させるための統合手順と設計ポイントを整理します。

Core Features & Use Cases

  • 都度課金ゲートウェイ(paygent_mb): career_type によるキャリア判定と、telegram_kind(申込/売上/取消/認証等)に基づく決済処理を行います(例: checkoutで career_type を受け取り申込100→redirectで認証→結果反映)。
  • 継続課金ゲートウェイ(WooCommerce Subscriptions連携): Subscriptionsのフックで telegram_kind(120/121/122/124/125/126 等)を処理し、継続課金IDをメタに保存して月次の売上要求を実行します。
  • ステータス・取消ロジックの統一: payment_status(20/21/32/40/44/60/62 等)や取消可能ステータスをキャリア別に扱い、取消要求(102)や売上要求(101)を仕様に沿って運用します。
  • 技術仕様の参照性: references のドキュメントでフロー(process_payment→申込→OpenID取得→redirect→コールバック→結果確認)やパラメータ(amountpc_mobile_typeopen_id、return_url/cancel_url 等)を明確化します。

Quick Start

「SKILLの仕様(career_type、telegram_kind、必須パラメータ、ステータス遷移、継続課金120/121/122フロー)に沿って、WooCommerceの決済処理設計と実装・改修方針を具体化して」と依頼してください。

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 carrier payments like auかんたん決済 and d払い into WooCommerce?

Paygent carrier payments integrate into WooCommerce by routing career_type values (4/5/6) and telegram_kind codes through a gateway_id paygent_mb, handling checkout selection, redirects, and callback-driven status transitions for one-time charges.

Does Paygent carrier payment support WooCommerce Subscriptions for recurring charges?

Paygent carrier payments support WooCommerce Subscriptions by processing telegram_kind codes (120/121/122/124/125/126) through Subscriptions hooks, saving recurring charge IDs to meta, and executing monthly sales requests automatically.

What is the correct redirect flow for Paygent carrier payment checkout in WooCommerce?

The Paygent carrier payment redirect flow processes payment via telegram_kind 100 application, obtains an OpenID, redirects for authentication, returns via callback, and confirms results using specified parameters like amount and return_url.

Why does my Paygent carrier payment integration fail due to amount parameter mapping?

Paygent carrier payment integration requires strict use of the amount parameter rather than payment_amount, alongside correct career_type values and telegram_kind codes, to ensure proper gateway_id paygent_mb processing and status transitions.

How do I handle Paygent carrier payment status transitions and cancellations in WooCommerce?

Paygent carrier payment status transitions map payment_status values (20/21/32/40/44/60/62) and handle cancellations per carrier using telegram_kind 102 cancellation requests and telegram_kind 101 sales requests according to specification.

Can I use Paygent carrier payments for both one-time and subscription charges in the same WooCommerce store?

Paygent carrier payments handle both one-time charges via gateway_id paygent_mb with telegram_kind 100-109 and subscription charges via WooCommerce Subscriptions integration with telegram_kind 120-126, allowing both in one store.