Product structure for PG Multi-Payment Service

Product structure for PG Multi-Payment Service

About product structure and connection types

Product structure

Product structure for PG Multi-Payment Service

Service Type of payment
One-time payment Member ID payment Recurring payment
Credit Card Paymentクレジットカード決済 Entry × ×
Standard
Advanced
Convenience Store Paymentコンビニ決済 - -
Pay-easyPay-easy - -
Mobile Edy PaymentEdy - -
Mobile Suica PaymentモバイルSuica - -
iD Net PaymentiDネット決済 - -
WebMoney PaymentWebMoney -
Prepaid Paymentプリペイド決済 - -
BitCoin Paymentビットコイン決済 - -
PayPalPayPal決済 - -
Account Transfer口座振替 -
Cash on Delivery代引 - -
Carrier Billingキャリア決済
Rakuten Pay楽天ペイ -
Multi-Currency Credit Card PaymentMulti-Currency Credit Card Payment -
LINE PayLINE Pay - -
Recruit Kantan PaymentRecruit Kantan Payment - -
China UnionPayChina UnionPay - -
Bank Transfer (Virtual Account)Bank Transfer (Virtual Account) - -
Apple PayApple Pay - -
PaidPaid - -
Payment via Payment SlipPayment via Payment Slip - -
Google PayGoogle Pay - -
PAYSLEPAYSLE - -

Connection types*

You can choose from three connection types to fit your system environment.

  • ・Link type
    Link (screen transition) to a payment screen offered by our company.
    The payment screen can be designed by editing a template.
  • ・Module type
    Install a payment processing module (program) in the server on your website.
    No need to conduct development for communications processing. (Java/PHP versions)
  • ・Protocol type
    Develop a program on your website according to connection specifications.
    Data exchanged using request/response communication via https communication.

*Connection types are limited by some payment methods.

Countermeasures

  • ・Payment result notification feature

Compatible devices

  • ・PC
  • ・Feature phone
  • ・Smartphone

Payment result notification feature

In the case of communication failure at the time of payment, we can asynchronously notify you about payment results (payment results notification feature). You are required to create a program to receive the content of payment notifications from us.

In addition, if the payment result notification feature fails to receive a normal response, it will send the notification again after a predetermined period of time.

Comparison table of three connection types

Item Link type Module type Protocol type
Degree of customization of the payment screen
(There are some
restrictions)

(high)

(high)
Degree of customization of processing procedurs including payment processing
(Low))

(high)

(high)
Compatibility with mobile carriers (Docomo/au/SOFTBANK)
(possible)

(possible)

(possible)
Compatiblity with carriers other than mentioned above ×
(impossible)

(possible)

(possible)
Availability of 3D Secure (identification service)
(available to use)

(available to
use)

(available to
use)
With/without module (program)
(without)

(with)

(without)
Constraints on language development
(yes)

(no)

(yes)
Development efforts of business operators
(small)

(regular)

(very big)
Contraints on platform (OS/CPU)
(no)

(no)

(no)
Availability of the management tool
(availabe to use)

(availabe to
use)

(availabe to
use)

Degree of customization of the payment screen

Link type
○(There are some restrictions)
Module type
◎(high)
Protocol type
◎(high)

Degree of customization of processing procedurs including payment processing

Link type
△(Low)
Module type
◎(high)
Protocol type
◎(high)

Compatibility with mobile carriers (Docomo/au/SOFTBANK)

Link type
◎(possible)
Module type
◎(possible)
Protocol type
◎(possible)

Compatiblity with carriers other than mentioned above

Link type
×(impossible)
Module type
◎(possible)
Protocol type
◎(possible)

Availability of 3D Secure (identification service)

Link type
◎(available to use)
Module type
◎(available to use)
Protocol type
◎(available to use)

With/without module (program)

Link type
◎(without)
Module type
△(with)
Protocol type
◎(without)

Constraints on language development

Link type
◎(yes)
Module type
△(no)
Protocol type
◎(yes)

Development efforts of business operators

Link type
◎(small)
Module type
○(regulardd>
Protocol type
△(very big)

Contraints on platform (OS/CPU)

Link type
◎(no)
Module type
◎(no)
Protocol type
◎(no)

Availability of the management tool

Link type
◎(availabe to use)
Module type
◎(availabe to use)
Protocol type
◎(availabe to use)