Recurring Billing (simplified) Cancellation
The recurring billing (simplified) conducts a payment of a fixed amount of money on the billing date at the start of every month as prescribed by SBPS. The payment is automatically made every month through the payment method specified by an end user.
Merchants perform the billing processing for the recurring billing (simplified) for the first time. For the next and later months, merchants are no longer required to perform the billing since SBPS does it at the start of every month. 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 payment service from the recurring billing (fixed term/pay-as-you-go) provided by SBPS separately.
Service Diagram

Main Features
- This service supports advance payment, monthly closure, and billing of fixed amount.
- Merchants can specify whether to charge for the first month or not, whether to charge at the time of a cancellation in the first month or not, and the final month for which the billing is made.
- Merchants are not required to perform the monthly billing processing.
Available Payment Methods
Recurring billing (simplified) is available for the payment methods below.
Credit Card Payment | d Payment | au PAY(au Kantan Kessai (Easy Payment)) |
Recruit Kantan Shiharai |
Service Specifications
Basic Specifications
The table below shows the basic specifications of the recurring billing (simplified). Each period of time for processing settlement, cancellation, and others performed by the payment administration tool is based on the tool.
Basic Specifications
Payment method | Field | Specifications | |
---|---|---|---|
Credit Card Payment | Close authorization settlement | Automated sales | ○ |
Specified sales | × | ||
Recurring billing processing (authorization) | First month: Billing processing is performed by the Merchant. Second month onward: Not necessary. | ||
Date of settlement process | Billing processing is performed on the first business day of each month | ||
Date of notification of billing processing not possible※1 | First business day of every month | ||
Period for refund | Until the 6th month including the date of purchase request process | ||
Selection function | Merchants can select first month billed/free and first month cancellation billed/free.※2 | ||
d Payment | Close authorization settlement | Automated sales | ○ |
Specified sales | × | ||
Recurring billing processing (authorization) | First month: Billing processing is performed by the Merchant. Second month onward: Not necessary. | ||
Date of settlement process | SBPS automatically bills on the first day of each month. | ||
Date of notification of billing processing not possible※1 | Second day of every month | ||
Period for refund | Until 8 p.m. of the end of the month after next including the date of purchase request process. * The money billed in the first month can be refunded from the first second day of the next month of the date of the purchase request process. | ||
Selection function | Merchants can select first month billed/free and first month cancellation billed/free. | ||
au PAY(au Kantan Kessai (Easy Payment)) | Close authorization settlement | Automated sales | ○ |
Specified sales | × | ||
Recurring billing processing (authorization) | First month: Billing processing is performed by the Merchant. Second month onward: Not necessary. | ||
Date of settlement process | SBPS automatically bills on the first day of each month. | ||
Date of notification of billing processing not possible※1 | First day of every month | ||
Period for refund | Until the last day of the month after next including the date of purchase request process. * The money billed in the first month can be refunded from the first day of the next month of the date of the purchase request process. | ||
Selection function | Merchants can select first month billed/free and first month cancellation billed/free. | ||
Recruit Kantan Shiharai | Close authorization settlement | Automated sales | ○ |
Specified sales | × | ||
Recurring billing processing (authorization) | First month: Billing processing is performed by the Merchant. Second month onward: Not necessary. | ||
Date of settlement process | SBPS automatically bills on the first day of each month. | ||
Date of notification of billing processing not possible※1 | Second day of every month※1 | ||
Period for refund | Not refundable. * If refund is necessary, the Merchant shall handle it. | ||
Selection function | Merchants can select first month billed/free and first month cancellation billed/free. |
*2: Merchants who applied for the recurring billing (simple) on February 1, 2022, or later do not have access to “Merchants can select first month cancellation billed/free.”
Supported devices
Recurring billing (simplified) is available on the devices listed below.
Payment method | PC | Smartphone | Mobile |
---|---|---|---|
Credit Card Payment | ○ | ○ | ○ |
d Payment | ○ | ○ | ○ |
au PAY(au Kantan Kessai (Easy Payment)) | ○ | ○ | × |
Recruit Kantan Shiharai | ○ | ○ | × |
List of Provided Functions
Recurring billing (simplified) provides the functions listed below. As for the Payment Administration Tool, only the main functions are listed. For details, see the Payment Administration Tool Manual.
Payment method | Provided functions | Link Type | API Type | Payment management tool |
---|---|---|---|---|
Credit Card Payment | Purchase | ○ | ○ | – |
Refund | – | – | 〇 | |
Payment result reference | – | ○※1 | – | |
Cancellation of recurring billing (simplified) | ○ | ○ | ○ | |
Recurring billing (simplified) cancellation notification | ○ | ○ | – | |
d Payment | Purchase | ○ | – | – |
Refund | – | ○ | ○ | |
Partial Refund | – | – | ○ | |
Cancellation of recurring billing (simplified) | ○ | ○※2 | ○※2 | |
Recurring billing (simplified) cancellation notification | ○ | – | – | |
au PAY(au Kantan Kessai (Easy Payment)) | Purchase | ○ | – | – |
Refund | – | ○ | ○ | |
Partial Refund | – | – | ○※3 | |
Cancellation of recurring billing (simplified) | ○ | ○ | ○ | |
Recurring billing (simplified) cancellation notification | ○ | – | – | |
Recruit Kantan Shiharai | Purchase | ○ | – | – |
Cancellation of recurring billing (simplified) | ○ | ○ | ○ | |
Recurring billing (simplified) cancellation notification | ○ | – | – |
*2: If cancellation is processed via API or Payment Management Tool at or after 20:00 on the final day of a month, the processing date at docomo side is the first day of the next month but the billing for the next month does not occur. (The cancellation date displayed in the Payment Management Tool is the final day of the month n and the same displayed in the docomo’s usage history is the first day of the month n+1.)
*3: The partial refund is available after the first day of the next month of the settlement process. However, an error may occur depending on the process status because the partial refund is processed after KDDI's billing process. In such a case, wait for a moment, and then carry out the process again.
Provided Functions Summary
The table below shows the summary of the unique functions used in recurring billing (simplified).
Provided functions | Overview of functions |
---|---|
Purchase | This function allows end users to actually operate the screen to process purchase of a recurring billing item or registration. |
Cancellation of recurring billing (simplified) | This function cancels a registration of recurring billing (simplified). No billing occurs after the cancellation is made |
Recurring billing (simplified) cancellation notification | This function notifies the merchant about a transaction that cannot be billed for. No billing occurs after the cancellation notification is issued. |
Optional Functions
Recurring billing (simplified) provides the optional functions listed below for the month in which the billing starts.
Selection function | Description |
---|---|
First month billed/free※1 | The merchant can specify whether or not to bill for the month in which the billing starts. To use this option, please set the camp_type parameter of each Purchase Request API of link type or API type. |
Select first month cancellation billed/free | The merchant can specify whether or not to bill for a purchase that is canceled within the month in which the billing has started. To use this option, please apply the setting before the start of the service provision. |
<<Image of Settlement Flow>>
The following shows the settlement flows of the cases where an end user purchases an item in January using the optional functions.



For merchants who apply for recurring billing (simplified) after December 1, 2021, the following settlement flow will be used for credit cards only.

Recurring Billing (Simplified) Cancellation Notification
Recurring Billing (Simplified) provides a function that issues a notification to merchants when an end user becomes unavailable for billing processing for certain reasons. The table below shows the types of the notifications. Upon receiving any of these notifications, merchants are requested to take appropriate actions such as termination of the service provision.
Type of Notification | Connection method | Description | Notification method |
---|---|---|---|
CR notification | Link Type | Notifies that the billing is impossible for the month of the notification and thereafter. | Result parameter of the Purchase Request API |
CC notification | Link Type | Notifies that the billing is impossible for the month that follows of the month of the notification and thereafter. | Result parameter of the Purchase Request API |
NG notification | API Type | Notifies that the billing is impossible for the month of the notification and thereafter. * This notification is available only for credit card payment. | Recurring Billing (Simplified) Cancellation Notification API |
<<Reasons for Recurring Billing (Simplified) Cancellation Notification>>
Payment method | Reason for notification | ||
---|---|---|---|
CR notification | CC notification | NG notification | |
Credit Card Payment | An error occurred in the billing processing. | – | An error occurred in the billing processing. |
d Payment |
| The mobile user contract with docomo was canceled before the billing processing at the start of the month. | – |
au PAY(au Kantan Kessai (Easy Payment)) | The billing result returned from KDDI was NG. | – | – |
Recruit Kantan Shiharai | An error occurred in the billing processing. |
| – |
<<Timing of Recurring Billing (Simplified) Cancellation Notification>>
Payment method | Timing of notification | ||
---|---|---|---|
CR notification※1 | CC notification | NG notification | |
Credit Card Payment | First business day of every month | – | First business day of every month |
d Payment | Second day of every month | Daily around 9:00※2 | – |
au PAY(au Kantan Kessai (Easy Payment)) | First day of every month | – | – |
Recruit Kantan Shiharai | Second day of every month | Real time※3 | – |
*2: The time here is provided roughly for your reference. The notification is issued on business days only.
*3: The notification is issued at the time communication from the financial institution is received.
Billing Date in Usage Statement
The time at which the billing data is included in the usage statement for end users depends on the setting of “first month billed/free” and “first month cancellation billed/free.” Please see the table below.
Billing Date in Usage Statement for End Users
First month billed/free | Billing at the time of cancellation in the first month | Payment method | First month | Second or later months※1 | First month cancellation |
---|---|---|---|---|---|
Billed | Billed | Credit Card Payment※2 | Final day of the request month | First day of every month | Final day of the request month |
d Payment | Request date※3 | First day of every month | Request date※3 | ||
au PAY(au Kantan Kessai (Easy Payment)) | Request date | First day of every month | Request date | ||
Recruit Kantan Shiharai | Request date | First day of every month | Request date | ||
Free | Billed | Credit Card Payment※2 | - | - | Final day of the request month |
d Payment | - | - | Request date※3 | ||
au PAY(au Kantan Kessai (Easy Payment)) | - | - | First day of the month that follows the request month | ||
Recruit Kantan Shiharai | - | - | Request date | ||
No charge | Credit Card Payment※2 | - | First day of every month | - | |
d Payment | Request date※4 | First day of every month | - | ||
au PAY(au Kantan Kessai (Easy Payment)) | - | First day of every month | - | ||
Recruit Kantan Shiharai | - | First day of every month | - |
*2: The behavior may be different for debit cards and other types of cards, since the authorization is obtained at the time of the request.
In addition, for merchants who apply for Recurring Billing (Simple) by credit card payment after February 1, 2022,
billing at the time of cancellation in the first month is unavailable.
*3: The billing data is displayed in the usage statement with the status of “未確定 (To be finalized)”. The status is updated to “確定済 (Finalized)” on the first day of the following month.
*4: The billing data is displayed in the usage statement with the status of “未確定 (To be finalized)”. The status is updated to “キャンセル済 (Cancelled)” on the first day of the following month.
<<Other Points of Attention>>
- The option of first month billed/free (charged or not charged) can be specified differently for each of the transactions. (specify camp_type)
- Merchants can specify whether or not to bill for any purchase that is free for the first month and that is canceled within the first month. This option must be specified in advance since the setting is applied by SBPS. This option cannot be specified differently for each of the transactions.
Cautions
Cautions for Each Payment Method
Payment method | Cautions |
---|---|
Credit Card Payment |
|
d Payment |
|
au PAY(au Kantan Kessai (Easy Payment)) |
|
Recruit Kantan Shiharai | None |
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
No supplementary information available.