Skip to content
ShuShuPay
日本語Contact

Payment requests. Connected to your system.

Discuss how your system can exchange payment requests and results with ShuShuPay. Portal work and server API integration, including Hosted screens, depend on the agreed scope.

Your systemShuShuPayResult delivery
Illustrative workflow

Choose the integration route

How this works

Hosted provides customer-facing screens on top of server API integration. Your server creates the order or preparation request, obtains the Hosted link and checks the result. A customer’s return or submission does not confirm the payment.

  • Portal

    Portal: browser-based work for your team

  • Hosted

    Hosted: customer-facing screens on top of server API integration

    Server API + Customer screen
  • API

    Direct API integration: requests, results and customer-facing screens in your own system

From a request to a customer update

How this works

Bank confirmation, the payment result and the merchant’s customer update are different records. Receiving a webhook does not establish that the customer has been updated.

  1. Your system or CRM creates a request
  2. ShuShuPay records the request
  3. Bank confirmation and external payment work
  4. ShuShuPay records the result
  5. CRM receives the result
  6. The merchant updates the customer
Illustrative workflow. The moving coin is not a live transaction or a confirmation.

Bank confirmation, the payment result and the merchant’s customer update are different records. Receiving a webhook does not establish that the customer has been updated.

Before integration starts

How this works

Separate Sandbox and Live keys and data. Contact us for integration documentation.

  • Environment
  • Payment workflows
  • Identifiers
  • Result delivery and retries
  • Contact person
Contact us for integration documentation

Let’s talk payments.

Tell us about the payment flow you need.

Contact