Content of this pageService Overview
Recurring billing (fixed term/pay-as-you-go) is a billing method through which a merchant specifies any timing and amount of money to conduct payments recurrently. A payment is made through processing of the merchant with a payment method specified by an end user.
The end user makes a purchase or request at the first time. At the second time and onwards, registered payment information is used for billing. Before starting using this billing method, ensure to obtain agreement in advance from the end user for the recurring billing and the money amount to be billed.
* Please note that this service is a different billing method from the recurring billing (simplified) provided by SBPS separately.
* Please note that with PayPay (online payment), you can only apply for the first time and cannot purchase at the same time.
Service Diagram
<<Examples of billing patterns>>
Main Features
- This billing method is suited to periodic purchase at a specified date or period.
- The amount of money can be specified or changed.
- Merchants are required to perform the billing processing on a monthly basis.
Available Payment Methods
Recurring billing (fixed term/pay-as-you-go) is available for the payment methods below.
| SoftBank Matomete Shiharai (B) | d Payment | au Kantan Kessai Service |
|---|---|---|
| Rakuten Pay (Online Payment) | Recruit Kantan Shiharai | PayPay (Online Payment) |
| Amazon Pay | Rakuten Pay (Online Payment)V2 |
Service Specifications
Basic Specifications
Basic specifications for each payment method related to recurring billing (fixed term/pay-as-you-go) are as follows. The periods of processing performed on the Payment Management Tool, such as capture and cancellation, depend on the specifications of the Payment Management Tool.
Basic Specifications
| Payment method | Field | Specifications | |
|---|---|---|---|
| SoftBank Matomete Shiharai (B) | Close authorization settlement | Automated sales | × |
| Specified sales | ○ | ||
| Recurring billing processing (authorization) | The billing processing is performed by the Merchant * SBPS does not perform the billing processing. | ||
| Period for settlement | Until the 60th day including the date of purchase request processing or the date of purchase request processing for recurring billing (fixed term/pay as you go). | ||
| Date of notification of billing processing not possible | None | ||
| Period for cancellation | Until the 60th day including the date of purchase request processing or the date of purchase request processing for recurring billing (fixed term/pay as you go). | ||
| Period for refund | In 400 days including the capture processing date *When a credit card payment is used, the period varies with the credit card company. | ||
| Valid period of recurring billing from the last billing processing date | None | ||
| d Payment | Close authorization settlement | Automated sales | ○ Only d Payment (carrier) is available |
| Specified sales | ○ Only d Payment (Wallet) is available | ||
| Recurring billing processing (authorization) | The billing processing is performed by the Merchant * SBPS does not perform the billing processing. | ||
| Period for settlement | Auto close authorization settlement: settlement is not necessary. Specified close authorization settlement: Until 8 p.m. of the end of the month after next including the date of purchase request process. | ||
| Date of notification of billing processing not possible | None | ||
| Period for cancellation | Auto close authorization settlement: cancellation function not available. Specified close authorization settlement: Until 8 p.m. of the end of the month after next including the date of purchase request process. | ||
| Period for refund | Until 8 p.m. of the end of the month after the next including the date of purchase request processing or the date of purchase request processing for recurring billing (fixed term/pay as you go). | ||
| Valid period of recurring billing from the last billing processing date | DOCOMO determines it (13 months as a guide). | ||
| au Kantan Kessai Service | Close authorization settlement | Automated sales | × |
| Specified sales | ○ | ||
| Recurring billing processing (authorization) | The billing processing is performed by the Merchant * SBPS does not perform the billing processing. | ||
| Period for settlement | Purchase request processing date, or within 90 days from the recurring billing (fixed term/pay-as-you-go) purchase request processing date | ||
| Date of notification of billing processing not possible | None | ||
| Period for cancellation | Purchase request processing date, or in 90 days including the recurring billing (fixed term/pay-as-you-go) purchase request processing date | ||
| Period for refund | Until the last day of the month after next including the date of settlement process. | ||
| Valid period of recurring billing from the last billing processing date | 365th day | ||
| Rakuten Pay (Online Payment) | Close authorization settlement | Automated sales | × |
| Specified sales | ○ | ||
| Recurring billing processing (authorization) | The billing processing is performed by the Merchant * SBPS does not perform the billing processing. | ||
| Period for settlement | Purchase request processing month, or by the last day of the month after five months including the recurring billing (fixed term/pay-as-you-go) purchase request processing month * Authorization period of a credit card is valid for 60 days from authorization. When capture processing is conducted for a payment whose authorization has expired, Rakuten conducts re-authorization/capture processing. | ||
| Date of notification of billing processing not possible | None | ||
| Period for cancellation | Purchase request processing month, or by the last day of the month after five months including the recurring billing (fixed term/pay-as-you-go) purchase request processing month | ||
| Period for refund | By the last day of the next month including the capture processing date | ||
| Amount change * Rakuten Pay (online payment) only | Before finalization of settlement: Purchase request processing date, or by the last day of the month after five months including the recurring billing (fixed term/pay-as-you-go) purchase request processing date After the settlement process: By the last day of the next month including the capture processing date | ||
| Valid period of recurring billing from the last billing processing date | 24 months * It becomes NG when the expiration date of the registered credit card has been exceeded. | ||
| Recruit Kantan Shiharai | Close authorization settlement | Automated sales | × |
| Specified sales | ○ | ||
| Recurring billing processing (authorization) | The billing processing is performed by the Merchant * SBPS does not perform the billing processing. | ||
| Period for settlement | Purchase request processing date, or in 30 days including the recurring billing (fixed term/pay-as-you-go) purchase request processing date * It can be extended up to 60 days by requesting at the time of request. | ||
| Date of notification of billing processing not possible | None | ||
| Period for cancellation | Purchase request processing date, or by the last day of the next month of recurring billing (fixed term/pay-as-you-go) purchase request processing | ||
| Period for refund | By the last day of the next month of the capture processing date | ||
| Valid period of recurring billing from the last billing processing date | 24 months * It becomes NG when the expiration date of the registered credit card has been exceeded. | ||
| PayPay (Online Payment) | 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 because it is auto close authorization capture *The Push charge Cancellation feature allows for cancellation at any time before the payment is due and the end user has not yet agreed to the cancellation. | ||
| Period for refund | The 365th day from the next day of the payment | ||
| Expiration date of the recurring billing from the date of last payment process | 365th day | ||
| Amazon Pay | 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 | First time: In 30 days after the "Session Update" processing date and time After the second time: In 30 days after the processing date and time of the billing (fixed term/pay-as-you-go) purchase request. | ||
| Period for cancellation | First time: In 30 days after the "Session Update" processing date and time After the second time: In 30 days after the processing date and time of the billing (fixed term/pay-as-you-go) purchase request. | ||
| Period for refund | No limitation | ||
| Rakuten Pay (Online Payment)V2 | Close authorization settlement | Automated sales | × |
| Specified sales | ○ | ||
| Period for settlement | Up to 30 days after the date of purchase request processing/recurring billing (fixed term/pay as you go) purchase or the last date of change of amount and until the 365th day from the date of purchase (or recurring billing (fixed term/pay as you go) request processing※4 | ||
| Period for cancellation | until the 365th day from the date of purchase (or recurring billing (fixed term/pay as you go) request processing※4 | ||
| Period for refund | Until the 30th day from the date of settlement process and until the 365th day from the date of purchase (or recurring billing (fixed term/pay as you go) request processing※4 | ||
| Period for amount change | Before finalization of settlement: Up to 30 days after the date of purchase request processing/recurring billing (fixed term/pay as you go) purchase processing or the last date of change of amount and until the 365th day from the date of purchase (or recurring billing (fixed term/pay as you go) request processing※4 After finalization of settlement: Until the 30th day from the date of settlement process and until the 365th day from the date of purchase (or recurring billing (fixed term/pay as you go) request processing※4 | ||
| Number of times amount can be changed | There is no limit to the number of times the amount can be changed. | ||
When a debit card is used, a withdrawal from the account is immediately performed at the time of authorization. When the period between authorization and capture is 30 days or more※1the authorized amount may automatically be refunded to the end user's account. After refunding to the end user's account, when the merchant conducts settlement and the amount cannot be withdrawn from the account, it may become a chargeback for the merchant.
*1: Varies with the debit card issue company.
*2: When processing shipments for orders for which 30 days have passed since purchase, authorization may not be obtained since it is be obtained again before finalization. Please conduct the settlement request process before shipping or providing the service.
(Due to a revision of the branding regulations, we plan to change to obtain credit again for orders that are 10 days past due starting in October 2021.)
*3: The guideline is 180 days.
*4: For details, please refer to RakutenPay(Online) V2) Service Overview.
Supported devices
Screen operations for requests or requests with simultaneous purchase for recurring billing (fixed term/pay-as-you-go) are available on the following devices.
| Payment method | PC | Smartphone | Mobile |
|---|---|---|---|
| SoftBank Matomete Shiharai (B) | ○ | ○ | × |
| d Payment | ○ | ○ | × |
| au Kantan Kessai Service | ○ | ○ | × |
| Rakuten Pay (Online Payment) | ○ | ○ | × |
| Recruit Kantan Shiharai | ○ | ○ | × |
| PayPay (Online Payment) | ○ | ○ | × |
| Amazon Pay | ○ | ○ | × |
| Rakuten Pay (Online Payment)V2 | ○ | ○ | × |
List of Provided Functions
Recurring billing (fixed term/pay-as-you-go) provides the functions listed below. The functions of the Payment Management Tool listed below are major ones only. For details, see the Payment Management Tool Manual.
| Payment method | Provided functions | Link Type | API Type | Payment management tool | |
|---|---|---|---|---|---|
| SoftBank Matomete Shiharai (B) | Purchase | ○ | – | – | |
| Settlement | – | ○ | ○ | ||
| Partial Settlement | – | ○ | ○ | ||
| Cancellation | – | ○ | ○ | ||
| Refund | – | ○ | ○ | ||
| 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 | – | – | ○ | ||
| d Payment (Carrier) | Purchase | ○ | – | – | |
| Refund | – | ○ | ○ | ||
| Partial Refund | – | ○ | ○ | ||
| 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 | ○※1 | ○※1 | ○※1 | ||
| d Payment (Wallet) | Purchase | ○ | – | – | |
| Settlement | – | ○ | ○ | ||
| Refund | – | ○ | ○ | ||
| Cancellation | – | ○ | ○ | ||
| 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 | ○※1 | ○※1 | ○※1 | ||
| au Kantan Kessai Service | Purchase | ○ | – | – | |
| Settlement | – | ○ | ○ | ||
| Partial Settlement | – | ○ | ○ | ||
| Cancellation | – | ○ | ○ | ||
| Refund | – | ○ | ○ | ||
| Partial Refund | – | ○※3 | ○※3 | ||
| Recurring Billing (Fixed Term/Pay as You Go) Request | ○ | – | – | ||
| Recurring billing (fixed term/pay as you go) re-request | ○ | – | – | ||
| Recurring Billing (Fixed Term/Pay as You Go) Purchase | – | ○ | ○ | ||
| Recurring Billing (Fixed Term/Pay as You Go) Unsubscribing | ○ | ○ | ○ | ||
| Rakuten Pay (Online Payment) | Purchase | ○ | – | – | |
| Settlement | – | ○ | ○ | ||
| Cancellation | – | ○ | ○ | ||
| Refund | – | ○ | ○ | ||
| Amount change | – | – | ○※3 | ||
| 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 | ○ | ○ | ○ | ||
| Recruit Kantan Shiharai | Purchase | ○ | – | – | |
| Settlement | – | ○ | ○ | ||
| Partial Settlement | – | ○ | ○ | ||
| Cancellation | ○ | ○ | |||
| Refund | – | ○ | ○ | ||
| Partial Refund | – | ○ | ○ | ||
| Multiple Refunds | – | ○ | ○ | ||
| 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 | ○ | ○ | ○ | ||
| PayPay (Online Payment) | 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*4 | – | ○ | – | ||
| Push Charge Purchase | – | ○ | ○ | ||
| Push Charge Finalization Notification | – | ○ | – | ||
| Push Charge Cancellation | – | ○ | – | ||
| Refund | – | ○ | ○ | ||
| Partial Refund*5 | – | ○ | ○ | ||
| Recurring Billing (Fixed Term/Pay as You Go) Request Status Reference*6 | – | ○ | – | ||
| Payment result reference | – | ○ | – | ||
| Amazon Pay | Acquisition of address and payment information | – | ○ | – | |
| Order | – | ○ | – | ||
| Session Update | – | ○ | – | ||
| Settlement*7 | – | ○ | ○ | ||
| Partial settlement *7*8 | – | ○ | ○ | ||
| Cancellation | – | ○ | ○ | ||
| Refund*9 | – | ○ | ○ | ||
| Partial Refund*9 | – | ○ | ○ | ||
| Recurring Billing (Fixed Term/Pay as You Go) Purchase | – | ○ | ○ | ||
| Recurring Billing (Fixed Term/Pay as You Go) Unsubscribing | – | ○ | ○ | ||
| Rakuten Pay (Online Payment)V2 | Purchase | ○ | – | – | |
| Settlement | – | ○ | ○ | ||
| Cancellation | – | ○ | ○ | ||
| Refund | – | ○ | ○ | ||
| Amount change | – | ○ | ○ | ||
| Payment result reference | – | ○ | – | ||
| 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 | ○ | ○ | ○ | ||
*2: Partial refund cannot be conducted in the month of settlement.
*3: Amount change is performed by canceling the purchase payment once and conducting the re-purchase processing. Therefore, note the following points:
- When processing an amount change request, an error may be returned and it may not be processed. In this case, please note that you will not be able to process the billing itself, including the original amount before the change. If it is not possible, please consider responding to the end user on merchant. After changing the amount, you need to confirm Settlement. If you wish to change the amount, please notify the end user in advance that you are changing the amount.
*4: 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.
*5: Partial refunds can only be implemented once. A multiple refunds feature is not provided.
*6: This function enables to see the request status (requesting or unsubscribed) of the recurring billing (fixed term/pay as you go).
*7: If more than 7 days have passed since the "Session update", the final result will be notified with a delay due to asynchronous processing. For details, please refer to "Settlement Request" and "Payment Result Notification" in the API type Amazon PayIF specification.
*8: Partial settlement can only be implemented once.
*9: Due to asynchronous processing, the final result will be notified with a delay. For details, please refer to "Cancellation Refund Request" and "Payment Result Notification" in the API type Amazon PayIF specification.
Provided Functions Summary
The table below shows the summary of the unique functions used in recurring billing (fixed term/pay-as-you-go).
| Provided functions | Overview of functions |
|---|---|
| Purchase | This function allows end users to actually operate screens and conducts recurring billing request processing and first time purchase processing simultaneously. By this function, a tracking ID for recurring billing management is issued. * When a tracking ID is issued through a recurring billing (fixed term/pay-as-you-go) request, this function is not used. * This function is not provided in PayPay (online payment). |
| Recurring Billing (Fixed Term/Pay as You Go) Request | This function obtains an agreement for a recurring billing request and conducts registration processing. This function only registers for the recurring billing (fixed term/pay-as-you-go) and does not bill. By this function, a tracking ID for recurring billing management is issued. By the end user agreeing to use recurring billing through a screen of the financial institution, an approval of the financial institution to use recurring billing (fixed term/pay-as-you-go) is obtained. |
| Recurring billing (fixed term/pay as you go) re-request | This function obtains an agreement again when changing the amount and/or quantity for recurring billing which was applied (registered) once. |
| Recurring Billing (Fixed Term/Pay as You Go) Purchase | This function conducts billing processing for a registered end user. This function uses an issued tracking ID for recurring billing management to conduct billing processing. |
| Recurring Billing (Fixed Term/Pay as You Go) Unsubscribing | This function allows end users to actually operate screens to cancel the request states of recurring billing. By this function, a tracking ID for recurring billing management is voided. Recurring billing that specifies a voided tracking ID results in an error. * There is no cancellation function for SoftBank Matomete Shiharai (B). |
Management Method for Recurring Billing (Fixed Term/Pay-as-You-Go)
Valid states of recurring billing (fixed term/pay-as-you-go) are managed through "customer ID" set by the merchant at the time of request or purchase and "tracking ID" returned from SBPS after obtaining an end user agreement. At the time of recurring billing (fixed term/pay-as-you-go) purchase request processing of the next time and later, by specifying the "customer ID" and "tracking ID," recurring billing processing can be conducted assuming that the end user has agreed.
Recurring Billing Management Image (When the Recurring Billing (Fixed Term/Pay-as-You-Go) Request Is Used at the First Time)
*For details on the items to be specified and the return values, please refer to the relevant IF specifications.
Cautions
Automatic Removal of Recurring Billing (Fixed Term/Pay-as-You-Go) Request
Recurring billing (fixed term/pay-as-you-go) request will automatically be removed if one of the following conditions is met. If this automatic removal occurs, the merchant should take an appropriate action such as asking the customer to submit the request again with another payment method.
| Payment method | Condition for automatic removal of request |
|---|---|
| SoftBank Matomete Shiharai (B) | The registered mobile phone itself is canceled |
| d Payment (Carrier) | The registered mobile phone itself is canceled |
| au Kantan Kessai Service | The registered mobile phone itself is canceled |
| Rakuten Pay (Online Payment) | The registered ID is canceled (withdrawn from membership) |
| Recruit Kantan Shiharai | The registered ID is canceled (withdrawn from membership) |
| PayPay (Online Payment) | The registered account is canceled (withdrawn from membership) |
| Amazon Pay | The registered account is canceled (withdrawn from membership) |
Specification differences for each payment method
For recurring billing (fixed term/pay-as-you-go), SBPS is accepting differences in the interface specifications between payment methods as much as possible so that all payment methods can be used in the common interface. However, since specifications of some functions differ depending on the conditions and functions provided by each financial institution, merchants must consider the functional differences when implementing those functions. The following shows the specification differences between payment methods.
| Payment method | Field | Specification difference |
|---|---|---|
| SoftBank Matomete Shiharai (B) | Cancellation |
|
| d Payment (Carrier) | Close authorization settlement |
|
| Purchase |
| |
| Cancellation |
| |
| au Kantan Kessai Service | Re-request |
|
| Settlement |
| |
| Payment method |
| |
| Partial refund in the month of capture |
| |
| Rakuten Pay (Online Payment) | Result Notification |
|
| PayPay (Online Payment) | Purchase |
|
| Close authorization settlement |
| |
| Cancellation |
| |
| User Cancellation Notification |
| |
| Push charge |
| |
| Recurring charge (based on term or usage rate) Request Status Reference |
| |
| Amazon Pay | system connection method |
|
| Provided functions |
| |
| Rakuten Pay (Online Payment)V2 | Result Notification |
|
| Provided functions |
|
Chargeback
In some cases, financial institutions may decide on refusal to purchase receivables (chargeback) based on complaints from the end user (about defects in delivered items, billing for purchases the user has not made, and the like), suspected fraudulent use, or other reasons. When notified of such refusal by a financial institution, SBPS will quickly inform the merchant about the situation.
Specification Change by Financial Institutions
SBPS is providing payment services from financial institutions by incorporating them in Online Payment ASP Service. Please note that when any financial institution changes the specifications or financial conditions of its services, SBPS may also change the specifications of Online Payment ASP Service accordingly.
Maintenance
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.
In addition to SBPS systems, in the event of service outage owing to maintenance work or failure in any system of financial institutions, their business partners, or others, SBPS will notify merchants of the situation as soon as possible and investigate the cause of the outage. 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
Notes on Using Recurring Billing (Fixed Term/Pay-as-You-Go)
Recurring billing (fixed term/pay-as-you-go) is a service that allows payments to be made only with operation on the merchant side without requiring the end user's intervention after the user has requested this service. Therefore, end users who use this service must fully understand the request content, billing timing, and other details. The following describes what merchants should note and support when using this service.
Member Management
- Member management and billing error prevention control should be designed and implemented on the merchant side.
- Merchants should assign and manage customer IDs to identify end users. In addition, when using the recurring billing function, incorporate the customer ID in the recurring billing interface to identify the end user.
- Make sure that end users can check, on member service or any other page, information such as the services in use and with which payment method recurring billing has been requested. Also describe the procedures to change and cancel recurring billing in a manner easily understood by end users.
- By providing appropriate measures, make sure that end users, though forgetting their login or other information, can inquire their recurring billing status or cancel recurring billing somehow.
Requesting Recurring Billing
- Merchants should clearly show the terms of use, the contract details on purchase and sale of items and others, conditions, and other information on their site so that end users can sufficiently understand the contract terms before requesting recurring billing.
- Inform end users that after the request is submitted, their subsequent payments will be automatically made with the selected payment method. In particular, ensure to describe timing of recurring billing (for example, on the XXth day every month after item delivery), provision timing of services, items, and so on, the next scheduled date, the note on the second and subsequent recurring billing.
- Each tracking ID for recurring billing management, which is assigned in response to a recurring billing request, should be managed per end user and per service, item, and so on for which each end user has requested recurring billing. This ID should not be used for services, items, and so on for which the end user has not requested recurring billing.
Changing the Amount of Money/Period for Recurring Billing
- The procedures for changing the delivery quantity, delivery timing, amount of money, and so on should be designed and implemented on the merchant site.
- If an end user has changed the settings for recurring billing, the user's payments should be made with the amount of money specified in the changed settings.
- When merchants change the payment amount as a measure for a campaign or any other purpose, they should inform end users in an appropriate manner.
- To change the target service/item to another one, submit a recurring billing request again.
Processing Recurring Billing
- Merchants should process recurring billing purchase requests for each end user according to the terms that the user agreed when requesting recurring billing.
- It is recommended that merchants send an order confirmation notification (payment advance notice) to end users before delivering their ordered items/services.
- It is recommended that merchants send notifications such as order email and delivery completion email to end users when they have processed recurring billing for those users.
- If the purchase amount of an end user exceeds the user's usage limit, payment processing may fail depending on the user's usage and contract statuses of the payment service. It is recommended that merchants perform payment processing before delivering items/services.
- Please note that when payment processing is performed after service delivery to end users for pay-as-you-go billing, and the like, the processing may fail in some cases, as shown above.
- If payment processing results in an error, notify and encourage the end user to choose another payment method or to cancel the service.
- Perform capture processing according to the delivery status of items/services. Also note that the settlement method, valid period for cancellation, and valid period for refunding differ between payment methods, which should be taken into consideration in operational designing.
Canceling Recurring Billing
- Inform end users about how to cancel recurring billing (fixed term/pay-as-you-go) in an appropriate manner easily understood by users.
- When an end user requests cancellation of recurring billing, perform cancellation processing quickly. Once cancellation is requested by the end user, do not let recurring billing payments to occur.
- Set up a recurring billing cancellation link on the top page of the merchant site. The link name should be shown in a manner easily understood by users and be displayed to all users, including members and non-members.
- Show the name of the item/service for which recurring billing is to be canceled in a manner easily recognized by the user. In addition, clearly describe the terms of use after cancellation (for example, re-requesting is not accepted during the month of the cancellation).
- Regarding monthly usage fees, and the like, implement service delivery that prevents double billing of monthly usage fees in principle when an end user cancels recurring billing and then requests the same service again.
This may not apply to cases such as additional purchases of the same item in sale of goods. - Do not force end users to answer a questionnaire while they are going through the cancellation procedure. Also note that the cancellation procedure should not use a multi-layer page flow or include too many links.
- The cancellation flow should be easy to understand. Do not use confusing descriptions (for example, "cancel cancellation") or misleading descriptions that may cause end users to misunderstand that the cancellation procedure has finished although it is not yet finished (for example, "Thank you for using our services").
- When receiving a request for cancellation via telephone, email, or other ways from an end user with no access to the merchant site, make sure the request is resolved between the end user and the merchant.
Other
- In response to inquiries from end users about their billing content, how to cancel recurring billing, and the like submitted to SBPS or any financial institution, SBPS may ask merchants to modify the descriptions on their site and/or the site structure.
- In some cases, for example, when an end user reports billing for purchases he or she has not made, chargeback may occur.
- In some cases, for example, when there are many user inquiries and the merchant fails to make appropriate modifications on its site to address the inquiries, SBPS may terminate provision of recurring billing (fixed term/pay-as-you-go).
