Content of this pagePayPay (Online Payment)
PayPay (Online Payment) is a payment method provided by PayPay. Product payments can be made using the payment information registered with PayPay.
End users can make payments using their PayPay (balance) and PayPay (credit)*Former name: payment after deliverys.
For more information on PayPay, refer to the following website. Note that the URL may change.
PayPay
https://paypay.ne.jp/
Service Diagram
Main Features
- End users can easily shop using their PayPay accounts.
- You can make payments using your PayPay balance.
- Because Merchants do not need to obtain personal information, end users can use the service safely and securely.
Usage Information for End Users
Please refer to the service website for details on the purchasing procedure.
For end-user usage information, please check the FAQ or the page of each financial institution.
Service Specifications
Basic Specifications
The available billing systems and billing system-specific basic specifications are as follows. Each period of time for processing settlement, cancellation, and others performed by the payment administration tool is based on the tool.
Billing Methods
| One-time charge | ○ |
|---|---|
| Recurring charge (simple) | × |
| Recurring charge (based on term or usage rate) | ○ |
Basic Specifications
| Billing method | Field | Specifications | |
|---|---|---|---|
| One-time charge | Close authorization settlement | Automated sales | ○ |
| Specified sales | ○ | ||
| Period for settlement | Auto close authorization settlement: settlement is not necessary. Specified close authorization capture: the same time on the 30th day from the purchase completion*1 *2. | ||
| Period for cancellation | Auto close authorization settlement: cancellation function not available. Specified close authorization capture: the same time on the 30th day from the purchase completion. | ||
| Period for refund | The 365th day from the next day of the payment | ||
| Number of available refunds | 20 refunds/transaction | ||
| Recurring charge (based on term or usage rate) | Close authorization settlement | Automated sales | ○ |
| Specified sales | × | ||
| Recurring billing process | The billing processing is performed by the Merchant * SBPS does not perform the billing processing. | ||
| Period for settlement | Settlement is not necessary because the auto close authorization settlement is performed. | ||
| Date of notification of billing processing not possible | None | ||
| Period for cancellation | None for auto close authorization capture*3 | ||
| Period for refund | The 365th day from the next day of the payment | ||
| Number of available refunds | 20 refunds/transaction | ||
| Expiration date of the recurring billing from the date of last payment process | 365th day | ||
*2: As for the settlement with increased amount, the process can only be carried out by 6 hours before the period for capturing (sales).
*3: As for the push charge cancellation, the cancellation can be performed anytime before the due date of payment when the end user is yet to agree.
Supported devices
The available devices are as follows.
| Device | Availability | Remarks |
|---|---|---|
| PC | ○ | – |
| Smartphone | ○ | – |
| Mobile | × | – |
List of Provided Functions
The following functions are provided. As for the payment administration tool, only the main functions are listed. For details, see the Payment Administration Tool Manual.
| Billing system/Close authorization settlement | Provided functions | Link Type | API Type | Payment management tool |
|---|---|---|---|---|
| One-time billing/Auto close authorization settlement | Purchase | ○ | – | – |
| Refund | – | ○ | ○ | |
| Partial Refund | – | ○ | ○ | |
| Multiple Refunds | – | ○ | ○ | |
| Payment result reference | – | ○ | – | |
| One-time billing/Specified close authorization capture | Purchase | ○ | – | – |
| Settlement | – | ○ | ○ | |
| Partial Settlement*1 | – | ○ | ○ | |
| Settlement with Increased Amount | – | ○ | ○ | |
| Increased sales finalization notification | – | ○ | – | |
| Increased sales expiry notification | – | ○ | – | |
| Cancellation | – | ○ | ○ | |
| Refund | – | ○ | ○ | |
| Partial Refund | – | ○ | ○ | |
| Multiple Refunds | – | ○ | ○ | |
| Payment result reference | – | ○ | – | |
| Recurring charge (based on term or usage rate) | Recurring Billing (Fixed Term/Pay as You Go) Request | ○ | – | – |
| Recurring Billing (Fixed Term/Pay as You Go) Purchase | – | ○ | ○ | |
| Recurring Billing (Fixed Term/Pay as You Go) Unsubscribing | ○ | ○ | ○ | |
| User Cancellation Notification*2 | – | ○ | – | |
| Push Charge Purchase | – | ○ | ○ | |
| Push Charge Finalization Notification | – | ○ | – | |
| Push Charge Cancellation | – | ○ | – | |
| Refund | – | ○ | ○ | |
| Partial Refund | – | ○ | ○ | |
| Multiple Refunds | – | ○ | ○ | |
| Recurring Billing (Fixed Term/Pay as You Go) Request Status Reference*3 | – | ○ | – | |
| Payment result reference | – | ○ | – |
*2: End users can unsubscribe the recurring billing (fixed term/pay as you go) with the PayPay app. After the unsubscribing, this function notifies the Merchants about the unsubscribing.
*3: This function enables to see the request status (requesting or unsubscribed) of the recurring billing (fixed term/pay as you go).
Payment Status Transition
When each of the provided functions is performed, the payment status changes as follows. For the method to perform each of the functions, see the Link Type System Specifications, API Type System Specifications, and Payment Administration Tool Manual.
<<One-time billing/Auto close authorization settlement >>
| Provided functions | Link Type Process name/Function ID | API Type Process name/Function ID | Payment management tool Screen name/Button name |
|---|---|---|---|
| Purchase | Purchase Request A01-1 | – | – |
| Refund | – | Cancel/Refund Request ST02-00306-311 | Billing Information Screen "Refund" |
| Partial Refund | – | Cancel/Refund Request ST02-00306-311 | Billing Information Screen "Multiple partial refunds"*1 |
| Multiple Refunds | – | Multiple Partial Refunds Request ST02-00308-311 | Billing Information Screen "Multiple partial refunds"*1 |
| Payment result reference | – | Payment result reference request MG01-00101-311 Payment Result Reference Request_returning Payment ID MG01-00102-311 | – |
<<One-time billing/Specified close authorization settlement >>
| Provided functions | Link Type Process name/Function ID | API Type Process name/Function ID | Payment management tool Screen name/Button name |
|---|---|---|---|
| Purchase | Purchase Request A01-1 | – | – |
| Settlement | – | Sales request ST02-00201-311 | Billing Information Screen "Settlement" |
| Partial Settlement | – | Sales request ST02-00201-311 | Billing Information Screen "Settlement"*1 |
| Settlement with Increased Amount | – | Sales request ST02-00201-311 | Billing Information Screen "Settlement"*1 |
| Increased sales finalization notification | – | Increased sales finalization notification NT01-00110-311 | – |
| Increased sales expiry notification | – | Increased sales expiry notification NT01-00112-311 | – |
| Cancellation | – | Cancel/Refund Request ST02-00303-311 | Billing Information Screen "Cancellation" |
| Refund | – | Cancel/Refund Request ST02-00303-311 *2 | Billing Information Screen "Refund" |
| Partial Refund | – | Cancel/Refund Request ST02-00303-311 *2 | Billing Information Screen "Multiple partial refunds"*3 |
| Multiple Refunds | – | Multiple Partial Refunds Request ST02-00308-311 | Billing Information Screen "Multiple partial refunds"*3 |
| Payment result reference | – | Payment result reference request MG01-00101-311 Payment Result Reference Request_returning Payment ID MG01-00102-311 | – |
*2: The Refund Request (ST02-00306-311) and Multiple Partial Refunds Request (ST02-00308-311) for auto close authorization capture can be used as well.
*3: Click the "Multiple partial refunds" button, and then enter the amount and suffix number to execute.
<<Recurring billing (fixed term/pay as you go)>>
| Provided functions | Link Type Process name/Function ID | API Type Process name/Function ID | Payment management tool Screen name/Button name |
|---|---|---|---|
| Recurring charge (based on term or usage rate) Application | Recurring charge (based on term or usage rate) Application Request D01-1 | – | – |
| Recurring charge (based on term or usage rate) Purchase | – | Recurring charge (based on term or usage rate) Purchase Request ST01-00104-311 Recurring charge (based on term or usage rate) Purchase request_Payment Number Return ST01-00107-311 | Recurring charge (based on term or usage rate) User Information Screen "purchase" |
| Recurring charge (based on term or usage rate) Cancellation | Recurring charge (based on term or usage rate) Application Request D01-1 | Recurring charge (based on term or usage rate) Cancellation request ST02-00309-311 | Recurring charge (based on term or usage rate) User Information Screen "Cancellation" |
| User Cancellation Notification | – | User Cancellation Notification NT01-00111-311 *5 | – |
| Push Charge Purchase | – | Push charge purchase request (payment request) ST01-00106-311 | Recurring charge (based on term or usage rate) User information screen *3 "Buy Push charge" |
| Push Charge Finalization Notification | – | Push Charge Finalization Notification (Payment Request) NT01-00113-311 Push Charge Finalization Notification (Payment Request)_returning Payment ID NT01-00114-311 *4 | – |
| Push Charge Cancellation | – | Cancel/Refund Request ST02-00303-311 | – |
| Refund | – | Cancel/Refund Request ST02-00303-311 *2 | Billing Information Screen "Refund" |
| Partial Refund | – | Cancel/Refund Request ST02-00303-311 *2 | Billing Information Screen "Multiple parts Refund" *1 |
| Multiple Refunds | – | Multiple Partial Refunds Request ST02-00308-311 | Billing Information Screen "Multiple parts Refund" *1 |
| Recurring Billing (Fixed Term/Pay as You Go) Request Status Reference | – | Recurring charge (based on term or usage rate) Request Status Reference MG01-00103-311 | – |
| Payment result reference | – | Payment result reference request MG01-00101-311 Payment Result Reference Request_returning Payment ID MG01-00102-311 | – |
*2: The Refund Request (ST02-00306-311) and Multiple Partial Refunds Request (ST02-00308-311) for auto close authorization capture can be used as well.
*3: This function can be used only when Recurring Billing (Fixed Term/Pay as You Go) Purchase is executed through the payment administration tool but the user balance is insufficient.
*4: This function sends the push charge establishment notification when "Payment ID Return Flag" is set to "Return" in Push Charge Purchase Request (Payment Request).
*5: When a user cancels an application from the PayPay application, or when a user cancels his/her PayPay account, this function will notify.
Cautions
Time limit for payment and application made by end user
Be aware that for the one-time billing, a time limit of 5 minutes is incurred after the PayPay screen is displayed until the purchase is complete. If 5 minutes have passed, the end user's payment fails.
For the recurring billing (fixed term/pay as you go), a time limit of 15 minutes is incurred after the PayPay application screen is displayed until the application is complete. If 15 minutes have passed, the end user's application fails.
Upper limit of Merchant settlement amount
An upper limit of the monthly settlement amount may be set depending on the result of the examination conducted by PayPay Corporation.
Settlement with increased amount
PayPay (Online Payment) can handle a settlement more than the authorized amount (settlement with increased amount). Upon the settlement with increased amount, a push notification is sent to the end user's PayPay app. When the end user agrees, the settlement process is completed correctly, and the Notification of Finalization of Settlement with Increased Amount function notifies the Merchant about it. On the other hand, if the end user's agreement is not received within 6 hours after the push notification, the settlement process is not performed, and the Notification of Cancellation with Increased Amount function notifies the Merchant about it.
Note that the settlement with increased amount can be executed again if the end user's agreement is not gotten within the authorization valid period.
As for the settlement with increased amount, the process can only be carried out by 6 hours before the period for capturing.
PayPay app link
When you make a purchase or apply from a smartphone with the PayPay app installed, the PayPay app will automatically launch and you will be able to pay and consent to use the app. In addition, after completing the procedure in the app, the return destination will be either the recommended browser or the standard browser when transitioning to the PayPay app. However, please note that if the browser of your smartphone is other than Safari, Chrome, UC, or firefox, it may not be linked. * Please note that in the case of Recurring billing(fixed term/pay-as-you-go) application, it is necessary to set the settings in the application request (D01-1). For details on the settings, please refer to "Link Type System Specifications (Recurring billing(fixed term/pay-as-you-go) Application Request)".
Supported browsers for logging in with the PayPay account
To make a payment with a computer or a smartphone without the PayPay app installed, the end user logs in to the browser with his/her PayPay account. The supported browsers are the latest versions of Chrome, Safari, Firefox, and Edge. Note that secret browser and private mode cannot be used.
What is Recurring billing(fixed term/pay-as-you-go) used for?
Note that the recurring billing (fixed term/pay as you go) cannot be used for one-time billing.
Recurring billing(fixed term/pay-as-you-go) Unit of Cancellation
On the premise that the same PayPay account is used, the recurring billing (fixed term/pay as you go) cancellation can be performed for each application (each MSID) filed to SBPS. Note that it is different from other payment methods.
Example: The ABCD online shop of a Merchant, who is selling commodities X, Y, and Z, has introduced the recurring billing (fixed term/pay as you go) of PayPay (Online Payment). An end user can apply for each of X, Y, and Z using the same PayPay account, and the Merchant can bill the end user for each of them. However, if the end user unsubscribe (cancel the recurring) one of X, Y, and Z, all the commodities sold at the ABCD online shop and applied for by the same PayPay account (X, Y, and Z) are unsubscribed (cancelled).
Push charge purchase function for recurring billing (fixed term/pay as you go)
If the recurring billing (fixed term/pay as you go) purchase request is made but the billing fails due to the end user's insufficient balance, this function can be used for sending a push notification to the end user's PayPay app to request the end user to make a payment. When the end user agrees, the push charge finalization notification function notifies the Merchant about it. In addition, the push charge purchase can be canceled by the push charge cancellation function.
Merchants can set the due date of payment for the push charge purchase. For the setting method, refer to the D408 Specifications (API Type System Specifications (PayPay (Online Payment))).
Even if fail is returned as the response from the Merchant through the push charge finalization notification function, the refund process is not carried out automatically. Be sure to make the refund.
Trade name display in test environment for recurring billing (fixed term/pay as you go)
When an Merchants with the master merchant contract with SBPS tests the recurring billing (fixed term/pay as you go) cancellation function in PayPay app developer mode using a test account provided by SBPS, use the trade name display data indicated by sequences of numbers that start with the combination of the applied Merchant ID and service ID. Because the same test account is shared among all the Merchants, a Merchant can see other Merchants' application data. Pay attention not to unsubscribe (cancel) them by mistake.
Standard for introducing recurring billing (fixed term/pay as you go)
The regulation of PayPay Corporation restricts the use targets of the recurring billing (fixed term/pay as you go) to periodical purchase items only. If a Merchants intends to use the recurring billing (fixed term/pay as you go) for one-time purchase items together with periodical purchase items, the Merchant is required to fulfill a security standard including two-factor authentication.
| Use target of recurring billing (fixed term/pay as you go) | Item attribute | Category | Security standard |
|---|---|---|---|
| Periodical purchase items only | ― | ― | No security standard |
| Periodical purchase items and one-time purchase items | Digital contents | Non-pre-paid commodities | |
| Pre-paid commodities | Required to fulfill security standard | ||
| Goods and services | ― |
* Two-factor authentication: Authenticates a user through a combination of two of the following factors: "something only the user knows," "something only the user has," and "something inherent to the user (such as a fingerprint)."
PayPay payment after deliveryPayPay (credit)*Former name: payment after delivery
If the user has already set up PayPay (credit)*Fo rmer name: payment after delivery in the user's PayPay account, the user can also pay with PayPay (credit)*Former name: payment after delivery in addition to PayPay (balance).
Note that the payment after delivery is prohibited for the following businesses:
・Specific continuous services (aesthetic salons, cosmetic medicines, private classes, English conversation schools, marriage agencies, etc.)
・Cigarettes and related items
・Pharmacies and drugstores
・State-controlled gambling
・Real estate rental
・Insurance (cash-value insurance)
・Event tickets (only for resellers)
・Vouchers and pre-paid cards (except local-limited ones)
PayPay (credit)*Former name: payment after delivery under the Individual Specification for Specified close authorization capture.
PayPay Corporation provides individual specifications for some merchant specified Settlement firm deadlines. In this case, depending on the user's Authorization status in the Payment where the user has selected deferred payment, an error of overdue Authorization may occur even if the Settlement request is made within the Settlement fixed deadline (*).
Please be aware of this in advance when receiving individual specifications for Specified close authorization capture deadline from PayPay, Inc.
*Sales requests made up to the same time 30 days after the completion of the purchase request will not result in an error.
Unauthorized Usage Investigations and Chargebacks
As a result of a complaint from the end user due to defective items or use that he/she is not aware of, or doubts about unauthorized use by a third party, PayPay Corporation may conduct investigation on unauthorized use or charge back (refusal of factoring) may be made. Upon receipt of notification from PayPay Corporation, SBPS will promptly report it to the relevant Merchant. Then, the Merchant is encouraged to take action in accordance with the notification. Note that if the charge back is fixed, the relevant sales amount will be excluded from settlement and be borne by the Merchant. For details, see the statement of material importance submitted when applying for the service.
Specifications
PayPay (Online Payment) is provided by incorporating the service provided by PayPay Corporation into the Online Payment ASP Service. Note that if PayPay Corporation makes a change to the specification or economic requirement, the specifications of PayPay (Online Payment) provided by SBPS may also change.
Service Suspension Due to Maintenance, etc.
Maintenance of the Online Payment ASP Service is performed on an irregular basis. Any service suspension due to maintenance will be notified in advance. As a rule, such a notification is made 1 week before the suspension. However, this may not be the case in the event of emergency maintenance.
If the service is suspended due to maintenance or the failure of PayPay Corporation or its partner systems, which are not SBPS systems, SBPS will promptly report it to Merchants as soon as we become aware of the situation and then find out the cause. Note that although SBPS will report to Merchants as soon as we find out the cause, it may take time to determine the cause if the problem is not attributable to us.
Supplementary Information
PayPay app developer mode
Since September 25, 2020, you can use the PayPay app in the staging environment provided by SBPS by logging in to developer mode of the PayPay app.
Use procedure:
- Start the PayPay app to open the login screen.
* If you are logged in with an actual account, log out. - Tap the header of the login screen seven times, and then select "Log in to developer mode."
- Log in with the test account provided by SBPS.
* Actual accounts cannot be used for logging in.
* The test account provided by SBPS is given on the connection information sheet upon the payment environment construction completion.
* If you log out, developer mode also ends.
Reconciliation between PayPay data and SBPS data
If you have concluded a direct contract with PayPay and need to check PayPay data against SBPS data for adjustment or other reasons, see the following.
| PayPay Data (Transaction data FTP/SFTP linkage) | SBPS data | |
|---|---|---|
| Connection interface information | Payment administration tool CSV download | |
| Payment ID (order_id) | ・Purchase result CGI: 「res_payinfo_key」 ・Payment result reference request_payment ID return response, recurring billing (fixed term/pay as you go) purchase request_returning payment ID response, push charge establishment notification (payment request)_returning payment ID response: "payment_id" | Payment ID |
| Merchant ID (merchantId) | – | – |
| Trade name (brandName) | – | – |
| Store ID (storeId) | – | – |
| Store name (storeName) | – | |
| Terminal ID (terminalId) | – | – |
| Transaction status (transactionStatus) | – | – |
| Transaction date and time (acceptedAt) | – | – |
| Transaction amount (amount) | Each purchase request, settlement establishment (sales) request, cancellation refund request: "amount" | Billing amount |
| Receipt number (orderReceiptNumber) | – | – |
| Payment method (methodOfPayment) | – | – |
| Merchant payment ID (merchantPaymentId) | Varies with the transaction status (transactionStatus) shown above * See the following <<Annexed table>>. | – |
<<Annexed table>>
| Merchant payment ID (merchantPaymentId) | Transaction status (transactionStatus) | SBPS connection interface information |
|---|---|---|
| AUTHORIZED | "res_tracking_id" of purchase result CGI | |
| FAILED | – | |
| CANCELED | "res_sps_transaction_id" of response for cancellation refund request | |
| COMPLETED | ・For auto close authorization capture: "res_tracking_id" of purchase result CGI ・For specified close authorization capture: "res_sps_transaction_id" of response for settlement request | |
| EXPIRED | "res_tracking_id" of purchase result CGI | |
| REFUNDED | "res_sps_transaction_id" of response for cancellation refund request |
