About Cross-border Pack
Types of Payments Handled
Payments are roughly categorized into two types: "face-to-face payment" and "non-face-to-face payment." The Cross-border Pack provides a payment agency service for "non-face-to-face payment."
Face-to-face payment
A payment made when an end user visits a real shop and purchases an item or service.
Examples: department store, supermarket, and restaurant
Non-face-to-face payment
A payment made when an end user purchases an item or service through the Internet or phone.
Examples: online supermarket and digital distribution

Service Overview
The Cross-border Pack service provides all the contracts, systems, and tasks necessary for introducing the online payment function into a Merchant website. For details, refer to each service specifications.
Outline of Cross-border Pack service

Unification of contracts
Various payment methods become available through an application to SBPS only. Discussions and contracts between each financial institution and the Merchant are not necessary in principle.
Unification of systems
Various payment methods are available through the interface provided by SBPS (ColossalTech Co., Ltd.
(CT Co., Ltd.)). Therefore, additional payment methods can easily be added.
Unification of tasks
SBPS collects all the proceeds from sales even when multiple payment methods are used.
Payment Process
After the Cross-border Pack is introduced, SBPS acts as a broker between the Merchant and financial institutions to carry out processes regarding payments and transfers on behalf of the Merchant.

- An end user purchases an item through the Merchant website.
- The Merchant requests SBPS to carry out the payment processing, and then waits for SBPS to return the payment result.
- SBPS (CT Co., Ltd.) requests the financial institution server to carry out the payment processing, receives the payment result, and then returns it to the Merchant.
- The Merchant delivers the item to the end user.
- The financial institution transfers the use fee to SBPS.
- SBPS transfers the usage fee to the Merchant.
* Note that the financial institution bills the end user and the end user pays to the financial institution at the timing stipulated in the financial institution's terms and conditions for end users.
Available Payment Method
Available payment methods are as follows. For the outline of the payment method, refer to the service specifications of the payment method.
Payment method category | Payment method |
---|---|
Cross-Border Pack | WeChat Pay |
system connection method
The system connection methods are as follow.
system connection method | Description |
---|---|
Web Type (PC Payment) | A method that displays a QR code for each payment method on the Merchant's EC website to let end users scan the QR code displayed on a computer with the payment app to carry out the process. |
Web Type (Smartphone Payment) | A method that enables end users to use the payment app installed in a smartphone on the Merchant's EC website to carry out the process. |
InAPP type | A method that obtains payment information through the Merchant's native app to carry out the process through the inter-server link. |
Mini App Type | A method that obtains payment information through the Merchant's mini app built on a payment app used by the user. |
Web Type (Computer Payment / Smartphone Payment)
<<Features>>
- Implement the interface provided by SBPS (CT Co., Ltd.) to carry out the payment process on the Merchant website.
- Because the screen does not move from the Merchant's EC website to another, it is expected that the cart abandonment can be prevented.
<<Usage Overview (computer payment)>>

<<Usage Overview (smartphone payment)>>

InAPP type
<<Features>>
- Because the Merchant's native app carries out the payment process, the Merchant side can flexibly build the desired transition, etc.
* As for WeChat Pay, WeChat Pay SDK needs to be implemented in the native app.
<<Usage Overview>>

MiniApp Type
<<Features>>
- Payments can be made through the mini app in a payment app used by end users.
<<Usage Overview>>

Payment management tool
The Cross-border Pack provides payment administration tools that enable users to easily summarize sales and carry out the refund process after the introduction. For how to use the payment administration tools, refer to the manual provided separately.
Major Functions
Major functions are as follows:
- Payment history search
- Processes after payments such as a refund
Screen Image

Provided functions
The Cross-Border Pack provided functions are as follows: Since available functions vary with the payment method, see Service Specifications for each payment method.
* Note: Functions of the payment administration tool are not shown here. Refer to the Payment Administration Tool Manual.
Provided function name | Description |
---|---|
Payment request | A function for making the payment of the purchased item. |
Payment History Search | A function for checking the payment status. |
Refund request | A function for making a full refund of a transaction after settlement. |
Refund History Search | A function for checking the refund status. |
Payment Cancellation | A function to be executed after a timeout for solving a mismatch in the payment status. |
Customs Clearance Request | A function for carrying out the customs clearance process. |
Customs Clearance History Search | A function for checking the status of the customs clearance process. |
Customs Clearance Re-request | A function for requesting the customs clearance again. |
Cross-Border Pack Environment
The Cross-Border Pack provides a special test environment and a production environment. Use the test environment for introduction and modification, and when releasing, switch to the connection target for the production environment and use it. However, note that the test environment may be out of service without prior notification due to SBPS's circumstances such as a maintenance.
* After you make an application and vetting is complete, we will provide the special test environment and production environment.
Usage Overview

System Requirements (payment administration tool)
The system requirements for the payment administration tool of the Cross-border Pack are as follows. Note that the actual uses do not assure of all functionalities, so we request Merchants check them as necessary.
Browsers supported by payment administration tool | Browsers that support JavaScript and cookies <<Actual uses>>
|
---|---|
Supported OS | No restrictions |
Network | Internet connection: Req'd |
Service Specifications
The general workflow for starting the use of the Cross-border Pack is as follows.

Settlement Rules
Types of Fees
Fee items related to settlement are as follows.
Field | Description | Remarks |
---|---|---|
Initial fee | The cost of various procedures, including environment-related setup. This fee is incurred the month that service begins. | |
Fixed monthly fee | The fixed monthly operating cost. This fee is incurred every month from the month that service begins. | A calculation on a daily prorated basis is not conducted. |
Payment fee | A fee for the payment processing of the purchase money of an item or service. | |
Payment service use fee | A fee for the use of the Cross-border Pack. | |
Transaction fee | A fee for the system processing. |
* Other fees may be charged in addition to the fees shown above. For details, check upon application.
Settlements
Using the date of settlement as the calculation base, the settlement processing results and amounts of money from the first day to the end day are summed, and the receipt statement is sent by the 10th business day of the month of settlement (or by 21st of the next month depending on the used payment method). The proceeds from sales are transferred to the specified bank account at the end of the next month of the month of settlement (the end of the month in which the receipt statement is sent).
Example Settlement Flows

Notes
Field | Description |
---|---|
Settlement cycle |
|
Billing method |
|
Check of transfer information |
|
Receipt statement |
|
Other |
|
Receipt statement image

Shown item | Description |
---|---|
(1) Total amount of settlement and date of transfer | The amount transferred to the specified account, and the date of transfer. * (5) The total of settlement amounts of all the fee items. |
(2) Fee item | Fee items for the introduced payment methods and options (including the installation fees). |
(3) Amounts of payment processing | The number and amount of settlements of each fee item, number and amount of refunds, and total number and amount. |
(4) Fees | The settlements for charging a fee for each fee item and number of them, unit price of fee, and the total amount of fees including the consumption tax. |
(5) Settlement amount | Settlement amount of each fee item. (A bill is sent when the amount is negative.) * (3) Total amounts of payment processing - (4) total amounts of fees |
(6) Summing period and service name | The target payment processing period and service name of the receipt statement. * A receipt statement showing the summing period and service name is sent for each service ID (SID). |
(7) Query number | A query number to be used for inquiring of SBPS. |
* Note that the shown items and design may change.
Which page should I check?
Information intended to help each Merchant staff understand the Cross-border Pack is posted.
Target Readers
Operation staff
Intended for the staff who operates the Merchant website, checks payments, and accesses the payment administration tool.
System staff
Intended for the staff who develops, operates, modifies, and constructs the Merchant website.
Description pages for target readers
Category | Target Readers | Description | |
---|---|---|---|
Operation staff | System staff | ||
Please Read First | ○ | ○ | Pages to check when the introduction of the Cross-border Pack is considered. |
Service Overview | ○ | ○ | Pages that describe the details of the service for the payment method to be introduced. |
API Type Cross-Border Pack Interface Specifications | ― | 〇 | The system specifications that provide information for connecting to the interface. |
Management Tool Manual | 〇 | ― | A page that explains the payment administration tool for checking the payment transaction status. |
Definitions of Terms
The definitions of terms used in the documents of the Cross-border Pack are as follows.
Term | Synonyms | Definition |
---|---|---|
SBPS | SB Payment Service Corp., SBPS | A payment agent company who contracts with Merchants It handles the contracts and collections for payment methods. |
CT Co., Ltd. | ColossalTech Co., Ltd. CT | A company operating gateways for connecting Merchants. A support desk handling queries about payments. |
Merchant | You, company | A company who contracted with SBPS for the Cross-border Pack. |
End user | End user, user, customer | The user of the Merchant's service. |
Financial institution | Financial Institution | A company who provides payment services through the Cross-border Pack of SBPS. |
Device | Terminal | A device to access websites. |
Payment | Settlement, payment | Interchange of money between a Merchant and an end user through a trade transaction. |
Payment method | Payment method | A method for paying the purchase money of an item or service. |
Payment status | – | The transaction status of a payment. |
Payment processing | – | Transmission and acceptance of payment information conducted by a system. |
Billing processing | – | To bill for the purchase money of an item or service. |
Chargeback | – | To cancel a settlement of a use fee (this is conducted by a financial institution) if the end user does not agree to the payment of the use fee for some reason such as unauthorized use. |
Regulation | – | Usage regulations stipulated by a financial institution intending for Merchants. |
Acceptance mark | – | A mark that indicates that a payment method is available. |
API | – | Stands for Application Programming Interface. A set of commands, rules, functions, etc., that can be used for programming. |
Interface | IF, interface | Stands for Interface. A device or software to connect different systems to each other. |
SSL communication | – | Stands for Secure Sockets Layer. A technology to encrypt information sent and received via the Internet. |
Native app | Merchant app | An app prepared by a service provider. |
InAPP | – | One of the connection methods of the Cross-Border Pack. A method that obtains payment information through the Merchant's native app to carry out the process through the inter-server link. |
SDK | Software development kit | Provides the interface for native apps to exchange communications of payments. |
Mini app | Mini program | Various service apps included in a payment app. A function that can be used on the payment app seamlessly. |
Web Type (PC payment) | MPM | A method that displays a QR code for each payment method on the Merchant's EC website to let end users scan the QR code displayed on a computer with the payment app to carry out the process. |
Web Type (Smartphone Payment) | H5 payment | A method that lets end users use the payment app installed on a smartphone on the Merchant's EC website to carry out the process. |