PAYHIP & STRIPE

日本語 / English

Payhip Connected to Stripe but Can’t Accept Payments? Japan Security Checklist Guide

I connected my Japanese Stripe account to Payhip to accept card payments. Payhip showed Stripe as Connected, but payment acceptance was still disabled in Stripe, so I was not ready to start selling. This was an account-activation issue before sales began, rather than a customer’s payment failing at checkout.

Stripe still required identity verification, additional information and an account review. The difficult part was Japan’s security checklist: it asked about customer-login protections and other controls operated by Payhip, which I could not answer myself.

I contacted Payhip support about those questions and used its answers to work through the declaration. After the required Stripe-side steps and review, the payment-acceptance issue was resolved. This guide explains what to check and what to ask Payhip if you encounter the same problem. It is written for Japan-based sellers; Japan’s security declaration is not a universal requirement for every seller worldwide.

Resolved — update November 20, 2026: The issue preventing live payment acceptance through Payhip has now been resolved following the Stripe-side requirements process. This guide covers how to check the restriction and use Payhip’s answers to work through Japan’s security checklist. Restored payment acceptance is separate from a completed purchase or a bank payout.

1. Check the warning in Payhip

Open Account → Settings → Payment Details. Read the warning above Stripe as well as its Connected label. Payhip’s troubleshooting documentation explains that an integration can be connected while Stripe account restrictions prevent checkout. Connection, accepting customer payments and paying funds into your bank account are separate states.

2. Open the connected Stripe account’s Account status

Check that you are viewing the account connected to Payhip and the live environment. Review each active task rather than treating all onboarding issues as one problem.

3. Ask Payhip about the controls you do not operate

I could not confidently answer questions about the platform’s customer-login controls. I searched Japanese and English documentation, blogs and discussions, but did not find a concrete answer set that let me complete my particular form. I then sent Payhip the relevant questions and available options.

Stripe’s Japan guidance permits using information obtained from a service provider, while leaving responsibility for the declaration with the merchant. The following is a summary of Payhip’s November 19 reply about my setup, not a pre-approved answer sheet for everyone.

Customer registration, login and account changes

Payhip listed suspicious-IP restrictions; two-factor or multi-factor authentication; verification at registration; login-attempt limits and throttling; behavioral analysis for suspicious activity; rate limiting; firewall protection; bot management; and other internal controls.

The Japanese options I could clearly match to the reply were suspicious-IP restrictions, login-attempt limits and throttling, and behavioral analysis. Email/SMS notifications and device fingerprinting were not explicitly confirmed, so I would not infer them.

The reply did not establish that MFA is mandatory at every customer login. Nor did registration verification establish an address or identity-document check. Payhip separately described email verification by link or code before access to purchased downloads; it explicitly distinguished this from MFA at every customer login.

Seller-account 2FA is another separate setting. Because Payhip offers customer accounts, do not select a “no customer login” exemption without checking your actual configuration.

Provider names and responsibilities

Field named in the reply Payhip’s suggested value
Outsourcing company Payhip Limited
Contractor company name Payhip
Application Service Provider name Payhip
Provider type Application Service Provider (ASP)

These are the English labels used in the response. Your Japanese form may not offer an exact equivalent. Payhip advised choosing ASP where available: it provides an external storefront platform, rather than acting as your employee. Do not invent a missing form option.

Payhip operates the storefront and its platform controls; Stripe processes payments; the seller remains responsible for their account settings and declaration.

The PCI DSS Qualified Security Assessor field

For my setup, Payhip advised selecting Not Applicable. It explained that it does not directly store, process or transmit card details and that third-party processors such as Stripe handle card payments, so it does not undergo a QSA audit for directly processing card data.

Keep this as a dated, setup-specific support answer. It does not establish an exemption for every platform, added service or payment integration. Compare the scope of your current question with your actual setup; ask Payhip or Stripe if they do not match.

4. Match the evidence to your form, then check review status

  1. Compare each current question and option with the provider’s response.
  2. Use only controls explicitly supported for your setup; ask about anything ambiguous.
  3. Review your declaration before submitting it and retain the dated support response.
  4. Check individual task completion separately from overall review and live-payment acceptance.

On November 19 my identity-document and additional-information tasks showed Completed. The additional-information detail view did not expose the submitted answers, so I could not recheck each security-checklist response. At that point the overall review was still active; the payment-acceptance issue has since been resolved. Payhip’s reply does not guarantee Stripe approval.

5. Return to Payhip after Stripe resolves the restriction

Once Stripe confirms that live-payment acceptance is enabled, revisit Payment Details. The warning in my Payhip account advised disconnecting and reconnecting Stripe after resolving the issue. Reconnecting is a follow-up step, not a way to bypass an outstanding review. Verify the account you reconnect.

Check whether the warning clears, then open the product’s purchase flow and inspect it for blocking errors. Reaching a payment form does not prove that a charge will succeed. I have not performed a charged test purchase or confirmed checkout completion.

Radar Lite is a separate decision

During setup I selected Radar Standard, then changed the live account to Radar Lite and saw the enabled confirmation. That is a previously observed part of this experience; I did not recheck the setting in today’s status inspection.

On November 19, Stripe’s Japan pricing page listed Standard at ¥8 per screened transaction and Lite without an additional charge for businesses on standard payments pricing. The ¥8 is not a Payhip connection fee. Lite does not waive ordinary payment-processing fees, and switching plans does not complete verification, the security declaration or account review. Check current pricing and your agreement.

The payment-acceptance issue is resolved

The intended sequence is: resolve outstanding Stripe requirements, confirm review and Payments status, clear Payhip’s warning, then check the purchase flow. The payment-acceptance issue has now been resolved following the Stripe-side requirements process. Payment acceptance is restored. A completed purchase and a bank payout remain separate, unverified outcomes.

Setting up the store and the article

For the setup and publishing experience, read I Set Up a Payhip Store to Sell an English Article.

Sources

Official pages reviewed November 19, 2026. The private Payhip support response received that day is summarized above; no private account or correspondence identifiers are included.