Content of this pageau Kantan Kessai Service
au Kantan Kessai Service is a payment method provided by KDDI. Product payments can be made using the phone bill payment information registered with Au or Uqmobile.
The following methods of payment are available for end users:
{au phone bill combined payment, Uqmobile phone bill combined payment}
The method for paying together with the monthly mobile phone charge
<<au PAY balance payment>>
The method for paying with pre-charged au PAY balance.
<<au PAY card payment>>
The method for paying using an au PAY card registered beforehand
*If you would like to add credit card payment or WebMoney payment as a payment method, you will need to apply separately.
au Kantan Kessai Service is a payment option that can be used on desktop and smartphone websites.
For more information on au Kantan Kessai Service, please refer to the following website. Note that the URL may change.
<au Kantan Kessai Service>
Service Diagram
Main Features
- End users can easily shop using only their au or UQmobile ID and password.
- Use fees are billed together with the monthly mobile phone charge, making the payment easy.
- Because Merchants do not need to obtain a credit card number and other 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
| Billing method | Availability | Remarks |
|---|---|---|
| One-time charge | ○ | – |
| Recurring charge (simple) | ○ | Not available for any payment methods if the WebMoney payment is used together. Not available for the au PAY prepaid card payment. Not available for debit cards and prepaid cards if the credit card payment is used together. |
| Recurring charge (based on term or usage rate) | ○ | Available only for the payment combined with the au phone charge. Not available for any payment methods if either credit card payment or WebMoney payment is used together. |
Basic Specifications
| Billing method | Field | Specifications | |
|---|---|---|---|
| One-time charge | Close authorization settlement | Automated sales | ○ |
| Specified sales | ○ *Not available for any payment methods if the WebMoney payment is used together. | ||
| Period for settlement | Auto close authorization settlement: settlement is not necessary. Specified close authorization settlement: Until the 90th day including the date of purchase request process. | ||
| Period for cancellation | Auto close authorization settlement: cancellation function not available. Specified close authorization settlement: Until the 90th day including the date of purchase request process. | ||
| Period for refund | Until the last day of the month after next including the date of settlement process. | ||
| Recurring charge (simple) | 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 processing | SBPS automatically bills on the first day of each month. | ||
| Date of notification of billing processing not possible | Returned starting from the first day of each month in order. | ||
| 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 | Whether the first month is charged or not and whether cancellation in the first month is billed or not can be selected as options. | ||
| Recurring charge (based on term or usage rate) | 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 90th 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 90th 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 | Until the last day of the month after next including the date of settlement process. | ||
| Expiration date of the recurring billing from the date of last payment process | 365th day | ||
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 method/Close authorization settlement | Provided functions | Link Type | API Type | Payment management tool |
|---|---|---|---|---|
| One-time billing／ Automated sales | Purchase | ○ | – | – |
| Refund | – | ○※1 | ○※1 | |
| Partial Refund | – | ○※1※2 | ○※1※2 | |
| One-time billing／ Specified sales | Purchase | ○ | – | |
| Settlement | – | ○ | ○ | |
| Partial Settlement | – | ○※3 | ○※3 | |
| Cancellation | – | ○ | ○ | |
| Refund | – | ○ | ○ | |
| Partial Refund | – | ○※2 | ○※2 | |
| Recurring billing (simple) | Purchase | ○ | – | – |
| Refund | – | ○ | ○ | |
| Partial Refund | – | – | ○※2 | |
| Cancellation of recurring billing (simplified) | ○ | ○ | ○ | |
| Recurring billing (simplified) cancellation notification | ○ | – | – | |
| Recurring billing (Periodic, pay-as-you-go) | Purchase | ○ | – | – |
| Settlement | – | ○ | ○ | |
| Partial Settlement | – | ○ | ○ | |
| Cancellation | – | ○ | ○ | |
| Refund | – | ○ | ○ | |
| Partial Refund | – | ○※2 | ○※2 | |
| 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 | ○ | ○ | ○ |
*2: 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.
*3: If the payment method is the credit card payment, the partial settlement is not available (an error occurs). It is available for other payment methods.
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-00303-402 | Billing Information Screen "au Refund" |
| Partial Refund | – | Cancel/Refund Request ST02-00303-402 | Billing Information Screen "au Partial Refund" |
<<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-402 | Billing Information Screen "au Settlement" |
| Partial Settlement | – | Sales request ST02-00201-402 | Billing Information Screen "au Partial Settlement" |
| Cancellation | – | Cancel/Refund Request ST02-00303-402 | Billing Information Screen "au Cancel” |
| Refund | – | Cancel/Refund Request ST02-00303-402 | Billing Information Screen "au Refund" |
| Partial Refund | – | Cancel/Refund Request ST02-00303-402 | Billing Information Screen "au Partial Refund" |
<<Recurring billing (simplified)>>
| 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-00303-402 | Billing Information Screen "au Refund" |
| Partial Refund | – | – | Billing Information Screen "au Partial Refund" |
| Recurring charge (simple) Cancellation | Purchase Request A01-1 | Recurring charge (simple) Cancellation request ST02-00302-402 | Recurring charge (simple) User Information Screen "Cancel" |
| Recurring charge (simple) Cancellation notification | Purchase Result CGI A02-1 | – | – |
<<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 |
|---|---|---|---|
| Purchase | Purchase Request A01-1 | – | – |
| Settlement | – | Sales request ST02-00201-402 | Billing Information Screen "au Settlement" |
| Partial Settlement | – | Sales request ST02-00201-402 | Billing Information Screen "au Partial Settlement" |
| Cancellation | – | Cancel/Refund Request ST02-00303-402 | Billing Information Screen "au Cancel” |
| Refund | – | Cancel/Refund Request ST02-00303-402 | Billing Information Screen "au Refund" |
| Partial Refund | – | Cancel/Refund Request ST02-00303-402 | Billing Information Screen "au Partial Refund" |
| Recurring Billing (Fixed Term/Pay as You Go) Request | Recurring charge (based on term or usage rate) Application Request D01-1 | – | – |
| Recurring billing (fixed term/pay as you go) re-request | Recurring charge (based on term or usage rate) Application Request D01-1 | – | – |
| Recurring Billing (Fixed Term/Pay as You Go) Purchase | – | Recurring charge (based on term or usage rate) Purchase Request ST01-00104-402 | Recurring charge (based on term or usage rate) User Information Screen "purchase" |
| Recurring Billing (Fixed Term/Pay as You Go) Unsubscribing | Recurring charge (based on term or usage rate) Application Request D01-1 | Recurring charge (based on term or usage rate) Cancellation request ST02-00309-402 | Recurring charge (based on term or usage rate) User Information Screen "Cancellation" |
Cautions
Behaviors depending on end user status
An error is returned and the process cannot be carried out if the settlement request process, the finalization process for recurring billing (simplified) or recurring billing (fixed term/pay as you go), or cancel/refund process is carried out when the end user who used the service is not in a processable status, for example, he/she has canceled his/her au or UQmobile mobile phone contract. In such a case, note that billing and refund cannot be carried out. * If the process fails, the Merchant shall consider dealing with the end user.
* If the process fails, the Merchant shall consider dealing with the end user.
Uses of recurring billing (fixed term/pay as you go)
Note that the recurring billing (fixed term/pay as you go) cannot be used for one-time billing. In addition, use for reasons such as omitting user authentication is also prohibited.
Mandatory tag element in payment request for recurring billing (fixed term/pay as you go)
Set the "Item (Service) Description ※1" and "Billing Timing※2" to the "Product name (item_name)."
Set item names that are recognizable on the merchant's service site to avoid complaints from end users about wrong billing for unpurchased items, which may occur when they cannot recognize the purchased items.
Incidentally, the value of the product name (item_name, 20 or less double-byte characters in length※3) is displayed on the payment screen (summary field) of the au Kantan Kessai Service and the user my page.
*1: 3,000- JPY -worth wine delivery course, etc.
*2: Billed on 20th each month, billed on every Friday, etc.
*3: On the KDDI screen, only the first 16 double-byte characters are displayed (characters after them are not displayed).
Cancellation procedures for recurring billing (fixed term/pay as you go)
Please prepare a personal page or similar where end users can check the names of the products they are subscribed to, the scheduled billing date, and cancellation instructions. Please set up the cancellation procedure screen at a high level so that it is easy for end users to understand.
Handling of errors in recurring billing (fixed term/pay as you go)
Please consider notifying end users that recurring billing will be suspended the next time a credit limit error (sales confirmation error) occurs during the sale of goods.
Also, please take care to direct them to other payment methods and make sure that the end-user can confirm the next and subsequent payment methods.
Differences of functions when au Kantan Kessai Service is used via SBPS
When using au Kantan Kessai Service, SBPS will incorporate the various interface specifications of au Kantan Kessai Service and the differences in specifications for each additional payment method into SBPS’s standard payment function. Therefore, Merchants can connect with the payment system and manage the payment processing without worrying about the payment methods actually used by the end users.
* Note that some restrictions are imposed on some functions.
- Payment management tool provided by KDDI
The payment management tool provided by KDDI cannot be used. Use the payment administration tool provided by SBPS to manage the payment information. - OpenID sharing
SBPS links the "Customer ID" shared through the payment ASP interface provided by SBPS and the OpenID linked with the au ID and manages them to enable to omit the login screen for the second and later payments with the au Kantan Kessai Service. Note that the customer ID to be shared shall be unique among end users. - Differences in specifications for combinations of additional payment methods
When additional payment methods are used, the available billing systems and refund functions are restricted due to the restrictions on the functions of WebMoney, etc. Understand the following table before selecting additional payment methods.
| Combination of payment methods | Commodity | Close authorization settlement | Billing method | Function | ||||
|---|---|---|---|---|---|---|---|---|
| Item | Digital content | Automated sales | Specified sales | One-time charge | Recurring billing (simple) |
Recurring billing (fixed term/pay as you go) |
Refund | |
| Basic※1 | ○ | ○ | ○ | ○ | ○ | ○※2 | ○※3 | ○ |
| Basic※1 + Credit card | ○ | ○ | ○ | ○ | ○ | ○ | × | ○ |
| Basic※1 + WebMoney | × | ○ | ○ | × | ○ | × | × | × |
| Basic※1 + Credit card + WebMoney | × | ○ | ○ | × | ○ | × | × | × |
*2: Excluding the au PAY prepaid card.
*3: Excluding the au PAY prepaid card and au PAY card.
Distinction among payment methods
The payment administration tool provided by SBPS manages payments as "au Kantan Kessai Service" without distinguishing among payment methods used for the payments.
Payment deadline setting
End users can make a payment even when the due date of payment has passed provided he/she starts the payment before the due date of payment. Note that the payment shall be complete within 4 minutes after the payment is started.
Period for refund
A refund process may end up as a refund error depending on the timing if the refund process is carried out on the first day of the period in which the refund process can be carried out (because the refund is available after the billing process). In such a case, wait for a moment, and then carry out the refund process again.
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, KDDI may conduct unauthorized usage investigation or a chargeback (refusal of factoring) may be made. Upon receipt of notification from KDDI, 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.
Note that if the credit card payment is used as an additional payment method, a notification may be sent directly from the credit card company or a payment agency company subcontracting with KDDI bypassing SBPS.
Specifications
The au Kantan Kessai Service is provided by incorporating the service provided by KDDI into the Online Payment ASP Service provided by SBPS. Note that if KDDI makes a change to the specifications or economic requirements, the specifications of au Kantan Kessai Service 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 one 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 KDDI or its partner systems that 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
If end user inquires of Merchant about problem such as "cannot use au Kantan Kessai Service",
inform the end user about the following common causes:
- The credit limit has been exceeded
- Overdue payment
- The end user himself/herself has imposed some restrictions on the use
* If the end user still not accepts the situation even after checking the items above, let him/her consult KDDI.
