Developer/Connection method/Link Type/Link Type Customer Payment Information Registration Request

Link Type Customer Payment Information Registration Request

The following shows the interface field definitions for the provided functions.

Function IDB01-1, C01-1
Process nameB01-1: Customer Payment Information Registration/Update Request
C01-1 Customer Payment Information Deletion Request
FlowMerchant→SBPS
DestinationB01-1: To be informed when the service starts
C01-1 To be informed when the service starts
Transmission methodForm POST
Transmission character encodingShift-JIS, html / text

(Legend of Type X: Single-byte character type M: Mixed double-byte character type 9: Numeric type)
*For the characters available for use, please refer to the Definition of Available Data Types (Basic Specifications).

SEQ Tag element name Field name Chars Format Req'd Type Description Remarks
1pay_methodPayment method1000X  Var.credit: Credit Card Payment
credit3d2: Credit Card Payment
(ID verification service (EMV 3-D Secure))
tpoint: T-Point Program
(Online Payment) accttransfer: (Account transfer service)
Specifies the payment method. (one or more can be specified)
* When omitted or specifying two or more methods, the payment selection screen is displayed by SBPS.
* When specifying two or more methods, separate them with commas.
2merchant_idMerchant ID59FixedID for identifying the merchantAssigned by SBPS
3service_idService ID39FixedID for identifying the merchant's serviceAssigned by SBPS
4cust_codeCustomer ID64XVar.A customer ID managed by the merchantThis must be unique with respect to the combination of merchant ID and service ID.
This ID must be assigned for each customer since it will be used as the association key for storing payment information.
5sps_cust_noSBPS Customer ID129FixedCustomer ID managed by SBPSRequired to specify when the SBPS payment method management number is set.
6sps_payment_noSBPS payment method management number39FixedPayment method management number controlled by SBPSRequired to specify when the SBPS customer ID is set
7terminal_typeType of terminal used by customer19  Fixed0: PC 1: CellphoneWhen omitted, "0" is applied. (PC and mobile device identification)
8success_urlURL when payment is completed500XVar.URL to which the screen returns  
9cancel_urlURL to go to when the payment is canceled500XVar.URL to which the screen returns  
10error_urlURL to go to when an error occurs500XVar.URL to which the screen returns  
11pagecon_urlRegistration notification CGI500XVar.URL to which the result is notifiedSSL communication is required.
12free1Free field 120M  Var.  Japanese characters and halfwidth alphanumeric characters may be used together.
This string is cut off if it exceeds the character limit. Any garbled characters will be replaced by "?".
13free2Free field 220M  Var.  Japanese characters and halfwidth alphanumeric characters may be used together.
This string is cut off if it exceeds the character limit. Any garbled characters will be replaced by "?".
14free3Free field 320M  Var.  Japanese characters and halfwidth alphanumeric characters may be used together.
This string is cut off if it exceeds the character limit. Any garbled characters will be replaced by "?".
15free_csvFree item4000M Var. Please refer to the payment-specific tag "free_csv."
16request_dateDate and time of request149FixedYYYYMMDDHHMISSDate and time when this function is requested by the merchant.
17limit_secondRequest timeout49  Var.Difference in allowed length of time between the time stamp on SBPS server and the date of requestThe default value of 600 is applied if this item is omitted.
18sps_hashcodeChecksum40XFixedThe checksum for the message represented as a valuePlease refer to the Method for Generating Checksums (Basic Specifications).
Function IDB02-1, C02-1
Process nameB02-1: Customer payment information registration/update result CGI
C02-1: Customer Payment Information Deletion Result CGI
FlowSBPS→Merchant
DestinationSpecified (or predefined)
URL (result notification CGI)
Transmission methodHTTP POST
Transmission character encodingShift-JIS

(Legend of Type X: Single-byte character type M: Mixed double-byte character type 9: Numeric type)
*For the characters available for use, please refer to the Definition of Available Data Types (Basic Specifications).

SEQ Tag element name Field name Chars Format Req'd Type Description Remarks
1pay_methodPayment method1000X  Var.As per the purchase request  
2merchant_idMerchant ID59Fixed  
3service_idService ID39Fixed  
4cust_codeCustomer ID64XVar.  
5sps_cust_noSBPS Customer ID129  Fixed  
6sps_payment_noSBPS payment method management number39  Fixed  
7terminal_typeType of terminal used by customer19  Fixed  
8free1Free field 120M  Var.  
9free2Free field 220M  Var.  
10free3Free field 320M  Var.  
11request_dateDate and time of request149Fixed  
Fields to be set when the result is returned
12res_pay_methodProcessed result Payment method20XVar.  The payment method selected when the
customer payment information was registered or requested to be deleted.
13res_resultStatus of processing result2XFixedOK: Registration process complete
CN: Deletion process complete
NG: Processing NG
When the deletion process is completed normally in the customer payment information deletion request process, the processed result status, CN (deletion process completed), is returned.
In customer payment information registration/deletion requests, the process result status NG (Processing NG) will not be returned.
14res_sps_cust_noSBPS Customer ID for processing129FixedCustomer ID managed by SBPSReturned only when the process is completed normally.
15res_sps_payment_noSBPS payment method management number for processing39FixedPayment method management number controlled by SBPSReturned only when the process is completed normally.
16res_payinfo_keyKey to identify customer payment information32X  FixedKey to identify the customer payment informationTo be returned only if the processed result is OK.
Credit card payment:
Hash value calculated from the card number through an SBPS original calculation (Supplementary 0 + 16 digits)
T-Point Program (Online Payment): None
17res_err_codeError code4X  Var.See list of error codes  
18res_dateDate and time of response149Var.YYYYMMDDHHMISSDate and time responded by SBPS
19limit_secondResponse limit time49Var.Difference in allowed length of time between the time stamp on SBPS server
and the date of request
The default value of 600 is applied if this item is omitted.
20sps_hashcodeChecksum40XFixedThe checksum for the message represented as a valuePlease refer to the Method for Generating Checksums (Basic Specifications).
* If pay_method is "accttransfer (account transfer service)" when requesting B01-1, the registration result will be linked in the account registration result file after 1 to 2 business days.
Function IDB02-2, C02-2
Process nameB02-2: Response to Customer Payment Information Registration/Update Result CGI
C02-2: Response to Customer Payment Information Deletion Result CGI
FlowMerchant→SBPS
DestinationNotification source of each result CGI
Transmission methodHTTP POST
Transmission character encodingShift-JIS, text/csv

When the HTTP status is 200, it is considered OK. When the status is other than 200, it is considered NG. . Even when an error is returned, process for SBPS has been completed. The screen moves to the specified error screen.

Note that even when a response error is returned from the merchant, the HTTP status 200 is given a higher priority and the process will be completed.

Function IDB03-1, C03-1
Process nameB03-1: Customer Payment Information Registration/Update Result (Redirect back to merchant's screen)
C03-1: Customer Payment Information Deletion Result (redirect back to merchant's screen)
FlowSBPS→Merchant
DestinationDesignated (or predefined) URL (Result Notification CGI)
Transmission methodForm POST
Transmission character encodingShift-JIS, html / text

(Legend of Type X: Single-byte character type M: Mixed double-byte character type 9: Numeric type)
*For the characters available for use, please refer to the Definition of Available Data Types (Basic Specifications).

SEQ Tag element name Field name Chars Format Req'd Type Description Remarks
1pay_methodPayment method1000X  Var.As per the purchase request 
2merchant_idMerchant ID59Fixed 
3service_idService ID39Fixed 
4cust_codeCustomer ID64XVar. 
5sps_cust_noSBPS Customer ID129  Fixed 
6sps_payment_noSBPS payment method management number39  Fixed 
7terminal_typeType of terminal used by customer19  Fixed 
8free1Free field 120M  Var. 
9free2Free field 220M  Var. 
10free3Free field 320M  Var. 
11request_dateDate and time of request149Fixed 
Fields to be set when the result is returned
12res_pay_methodProcessed result Payment method20XVar.  The payment method selected when the payment information was registered
13res_resultStatus of processing result2XFixedOK: Registration process complete
CN: Deletion process complete
NG: Processing NG
When the deletion process is completed normally in the customer payment information deletion request process,
the processed result status, CN (deletion process completed), is returned.
In customer payment information registration/deletion requests,
the process result status NG (Processing NG) will not be returned.
14res_sps_cust_noSBPS Customer ID for processing129FixedCustomer ID managed by SBPSReturned only when the process is completed normally.
15res_sps_payment_noSBPS payment method management number for processing39FixedPayment method management number controlled by SBPSReturned only when the process is completed normally.
16res_payinfo_keyKey to identify customer payment information32X  FixedKey to identify the customer payment informationTo be returned only if the processed result is OK.
Credit card payment: Hash value calculated from the card number through an SBPS original calculation (Supplementary 0 + 16 digits)
T-Point Program (Online Payment): None
17res_err_codeError code4X  Var.See list of error codes  
18res_dateDate and time of response149Var.YYYYMMDDHHMISSDate and time responded by SBPS
19limit_secondResponse limit time49Var.Difference in allowed length of time between the time stamp on SBPS server and the date of requestThe default value of 600 is applied if this item is omitted.
20sps_hashcodeChecksum40XFixedThe checksum for the message represented as a valuePlease refer to the Method for Generating Checksums (Basic Specifications).

The settings necessary for the ID verification for the Link Type credit card payment (ID verification service (EMV 3-D Secure)) can be configured.

How to Use

<<API Used>>

Connection methodAPI TypeData flow
Link TypePurchase RequestMerchant→SBPS

<<Elements to be Configured>>

(Legend of Type X: Single-byte character type M: Mixed double-byte character type 9: Numeric type)
*For the characters available for use, please refer to the Definition of Available Data Types (Basic Specifications).

Tag element nameField nameCharsFormatTypeDescriptionRemarks
free_csvFree field (CSV format)4000MVar.Refer to "How to Set Up" below.base64 encoding is required.
When using the API Type service together, an encryption with 3DES may be required.

How to Set Up

Concatenate (1) Field name, (2) Connection character (single-byte equal), (3) Field value, and (4) Delimiter (single-byte comma).

<<Field Definitions>>

DescriptionSetting ValueDescriptionCharsFormatRemarks
Field nameTDS2INFO_TOKENToken of payment information of credit card user XFor details, refer to "E003_EMV 3-D Secure Authentication Specifications."
TDS2INFO_TOKEN_KEYToken key of payment information of credit card user X 

<<Setting Examples>>

  • Connect the setting value and that value with a connection character (single-byte equal), and concatenate them with a delimiter (single-byte comma). TDS2INFO_TOKEN=123456789abc,TDS2INFO_TOKEN_KEY=asdefg123
  • Encrypt the string through the 3DES encryption, and then convert it in the base64 format. 1BNK6NDjiRdhEN0p5rajgyp2tjEC5EEnpvbBGYO+F6fckdWWXllvDYGQ1Jq・・・
  • Set it to free_csv with Link Type POST fields, and send.

<<Validation>>

When making a request of purchase request, although validation for the whole field is performed, validation is not performed for each field. (Validation for each field is performed after the screen has moved to the Input screen, and if it results in an error, the screen moves to the error screen.)

The details of validation for free_csv are as follows:

  • The sent character string is 4,000 bytes or less.
    • The encoding format is base64.
    • The decoded character string is 2,500 bytes or less.

 Restrictions

<<Restrictions>>

Attention must be paid to free_csv as it has the following restrictions:

  • The character encoding must be S-JIS
  • Field names must be case sensitive
  • Field names must not include connectors or delimiters
  • Field values must not include delimiters
  • The field order does not matter
  • Fields are not mandatory
  • Although setting undefined fields will not be a problem, such undefined fields must be ignored. Change of input by end users will not be redirected after the screen has moved to the Input screen.
  • On the administration screen, the free_csv data itself is not displayed.

<<Characters that cannot be Used in free_csv Fields>>

The following characters cannot be used in any of the fields:

CharacterNameS-JIS Code
,Single-byte comma0x2C
Single-byte single quotation0x27
Single-byte double quotation0x22
%Single-byte percent0x25
|Single-byte pipe0x7C
&Single-byte ampersand0x26
<Single-byte smaller-than sign0x3C
>Single-byte greater-than sign0x3E
。 「」、・ヲァィゥェォャュョッーアイウエオカキクケコサシスセソタチツテトナニヌネノハヒフヘホマミムメモヤユヨラリルレロワン゙゚Single-byte katakana0xA1–0xDF
Was this page helpful?