KOMOJU

Service Overview

KOMOJU is Japan's online and offline payment infrastructure. The operating entity was originally Degica and was renamed KOMOJU Co., Ltd. in March 2026. It is not positioned as a Japanese Stripe; rather it brings in every payment method Japanese consumers actually use — cards, convenience store cash, bank transfer (furikomi), carrier billing, prepaid cards and BNPL. The official figures are 65+ payment methods, 20,000+ stores using the service and 99.99% uptime.

Understanding the Japanese market structure is the precondition for understanding KOMOJU's value. The official framing is that credit and debit cards account for about 60% of purchase behaviour in Japan, bank transfer about 14% of sales, and convenience store channels allow in-person cash payment at 50,000+ store locations. Japan is therefore not a market where cards alone are enough: accepting only cards gives up a meaningful share of orders, and these methods share one trait — they are asynchronous, separating order placement from funds arrival.

The product and compliance sections are also solid. Integration forms include API, Hosted Pages, Hosted Fields, mobile SDK, Payment Links, KOMOJU Terminal, Tap to Pay and KOMOJU Card; e-commerce integrations cover Shopify, Wix, WooCommerce, Salesforce and Magento; compliance spans PCI DSS Level 1 v4.0, ISMS / ISO 27001 and Privacy Mark. Public clients include Wargaming, Daniel Wellington, Francfranc, KOALA, JUN and LEDLENSER, and a merchant testimonial cites zero chargebacks and a 94%-95% approval rate after integration.

The core judgement: KOMOJU's value is not its rate but the completeness of Japanese local methods. Japanese consumers make heavy use of konbini cash, bank transfer, carrier billing and prepaid cards, and the real engineering sits in the order state machine and reconciliation rather than the payment page. KOMOJU is also a merchant-of-record model — the official site states that using the service means it collects sales proceeds on the merchant's behalf and settles to the merchant account. For overseas brands without a Japanese entity this is essential, but it also means one extra layer in the funds chain, and settlement timing plus chargeback liability must be written into the contract.

Key Strengths

• The most complete Japanese local method coverage: 65+ payment methods bringing konbini cash, bank transfer, carrier billing, prepaid cards and BNPL into one integration layer. For the Japanese market, the provider with the fewest gaps is usually the best one.
• Konbini is a genuine requirement: 50,000+ store locations and cash payment after checkout. A meaningful share of Japanese consumers are uncomfortable entering card details online, and konbini cash is their default; skipping this tier means abandoning that segment.
• Merchant of record solves the missing-entity problem: collection works without a Japanese legal entity because the platform collects and then settles to the merchant. For overseas brands this is the dividing line between being able and unable to do business in Japan, not a convenience feature.
• 8 integration forms for different stages: from sending a Payment Link to running a Hosted Fields checkout, then a mobile SDK and KOMOJU Terminal offline. Teams can choose by stage instead of building the heaviest option first.
• Compliance aligned with Japanese requirements: PCI DSS Level 1 v4.0, ISMS / ISO 27001 and Privacy Mark cover card data security, information security management and the Japanese privacy mark, which are hard procurement gates for payment projects inside enterprises.
• Complete e-commerce plugins: ready integrations for Shopify, Wix, WooCommerce, Salesforce and Magento, so storefronts and content commerce do not integrate from scratch.

Product Ecosystem

Collection and Payment Methods

Cards as the baseline, layered with konbini, bank transfer, carrier billing, digital wallets, prepaid cards and BNPL such as Paidy. Methods are the core asset, and choosing them is the first integration decision.

Integration Forms

API, Hosted Pages, Hosted Fields, mobile SDK, Payment Links, KOMOJU Terminal, Tap to Pay and KOMOJU Card. Light scenarios use Payment Links or Hosted Pages; deeper customisation uses Hosted Fields and the API.

In-person Acceptance

KOMOJU Terminal and Tap to Pay support physical stores and mobile scenarios with unified reconciliation in the same back office. For Japanese businesses running both e-commerce and shops, this determines whether one provider can cover all channels.

E-commerce Platform Integrations

Plugins for Shopify, Wix, WooCommerce, Salesforce and Magento. A storefront already built on Shopify can enable local methods by installing a plugin without development work.

Settlement and Merchant of Record

The platform collects sales proceeds and settles to the merchant, which is the core mechanism for overseas entities. Funds flow, settlement timing and chargeback liability are all fixed at this layer, and this is the part of the contract needing the closest reading.

Limitations

• Mainland China entities face practical barriers: Japanese local acquiring and some payment methods require a Japan-registered business or local bank account, so domestic companies usually go through merchant of record under stricter qualification and business review, with approval depending on vertical and business substance.
• Some methods depend on a local entity and account: bank transfer and konbini settlement rely heavily on Japanese account infrastructure, and without a local account the usable method set narrows sharply. Available options are not equivalent to the 65 listed.
• Methods follow the official list: the 65+ methods are enabled according to merchant type, industry and review outcome rather than all at once. Availability must be confirmed item by item, not inferred from the total.
• Merchant of record adds a funds layer: the platform collects first and settles afterwards, which means longer settlement cycles and more complex liability allocation in disputes, so reserve and delayed-settlement clauses must be confirmed upfront.
• Language and local support cost: documentation and dashboards run mainly in Japanese and English with no Chinese coverage, so communication with the local team carries language and time-zone cost and localised material usually has to be produced in-house.
• Asynchronous methods need a self-built state machine: konbini payment and bank transfer separate order placement from funds arrival, so order states, expired-unpaid handling, partial payments and refund reconciliation all have to be designed by the merchant.

Use Cases

• Overseas brands entering Japanese e-commerce (★★★★★): businesses with no Japanese entity that still need to collect from Japanese consumers. Merchant of record plus local method completeness closes both the entity gap and the method gap.
• Japanese local e-commerce and storefronts (★★★★★): businesses selling to Japanese consumers that need konbini and bank transfer channels. Missing those two tiers loses orders directly, so coverage is the most concrete value.
• Digital goods and games published in Japan (★★★★☆): games, software and content subscriptions have a large non-card audience in Japan, and konbini cash plus carrier billing reach that segment.
• Retail running online and offline (★★★★☆): businesses operating shops and e-commerce with unified reconciliation can use Terminal and Tap to Pay offline and the same back office online.
• Japan sites run by China-based teams (★★★☆☆): workable through an overseas entity plus merchant of record, but expect stricter review and longer settlement, and cross-border funds and tax handling must be confirmed independently.
• Mainland China operations (☆☆☆☆☆): KOMOJU serves Japan only, and domestic acquiring must be performed by a licensed institution. This path is entirely unusable.
• Unified acquiring across many global markets (★☆☆☆☆): the worst fit. It is a Japan-specialist solution, so global business requires other acquirers in other markets and cannot be covered by one provider.

Pricing

The table lists billing items and pricing basis only. KOMOJU does not publish a unified rate, and quotes must be confirmed against the payment-method mix, industry and volume. The cost structure of different Japanese payment methods varies widely, so no single percentage represents overall cost; the contract governs.

FAQ

• Can I collect without a Japanese company?
  Yes, through the merchant-of-record model. The official site states that using the service means the platform collects sales proceeds and settles to the merchant account, which is precisely the design for overseas brands without a Japanese entity. The trade-off is an extra layer in the funds chain, longer settlement, and a review that focuses more on business substance and vertical.

• Why is konbini payment necessary?
  Because a meaningful share of Japanese consumers do not use cards. Official figures put cards at about 60% of purchase behaviour and bank transfer at about 14% of sales, while konbini channels cover 50,000+ stores for cash payment. Accepting cards only excludes non-card users entirely, and in Japan that loss is far larger than any fee difference.

• How do I reconcile konbini and bank transfer orders?
  Both are asynchronous: the customer receives a payment number or transfer details at checkout, pays at a store or bank, and the platform sends a callback afterwards. The merchant must build an order state machine handling expired-unpaid, partial payment, duplicate payment and refunds, and reconcile regularly against platform settlement statements. Synchronous payment assumptions do not work.

• Which integration options exist?
  8 in total: API, Hosted Pages, Hosted Fields, mobile SDK, Payment Links, KOMOJU Terminal, Tap to Pay and KOMOJU Card. Ready plugins exist for Shopify, Wix, WooCommerce, Salesforce and Magento, and the fastest route to a live payment is Payment Links.

• What does it cost?
  No unified rate is published. Cost is driven by scheme interchange, Japanese local acquiring cost, industry risk level and payment-method mix, and konbini plus carrier billing follow a separate pricing logic, so pricing must be negotiated per method and confirmed in the contract.

Source: original 16IDC content. Product capabilities, supported countries and fee definitions follow the official documentation and your contract.