Developer/Connection method/Link Type/Link Type Purchase Request

Link Type Purchase Request

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

The interface items differ depending on the billing method [one-time charge/recurring charge (based on term or usage rate)/Recurring charge (simple)].
Please select the tab for the billing system you wish to use.

Function IDA01-1
Process namePurchase Request
FlowMerchant→SBPS
DestinationTo 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).

  • One-time charge
  • Recurring charge (based on term or usage rate)
  • Recurring charge (simple)
SEQ Tag element name Field name Chars Format Req'd Type Description Remarks
1pay_methodPayment method1000XVar. Please refer to the payment method tag "pay_method"for details.Specifies the payment method. (one or more can be specified)
2merchant_idMerchant ID59Fixed ID for identifying the merchantAssigned by SBPS
3service_idService ID39Fixed ID 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 ID129  Fixed Customer ID managed by SBPSNot to be set for this linkage model (null characters)
6sps_payment_noSBPS payment method management number39  Fixed Payment method management number controlled by SBPSNot to be set for this linkage model (null characters)
7order_idPurchase ID38XVar. A purchase ID managed by the merchantThis must be unique with respect to the combination of merchant ID and service ID. *Set a unique ID also for the cancellation of recurring billing (simplified).
8item_idProduct ID32XVar. A product ID managed by the merchant  
9pay_item_idFinancial Institution Item ID32X  Var.   Not to be set for this linkage model (null characters)
10item_nameProduct name40MVar. A product name of your choiceJapanese 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 "?". *If not set, the item name is not displayed on the Purchase Confirmation screen. Mandatory field for NP Atobarai. For Pay-easy payment, the following characters are prohibited:
(*) Asterisk
(_) Underscore
(@) at symbol
11taxAmount of tax79Var. Amount of collecting taxes0 yen or more should be specified.
*Mandatory only for General Wire Transfer (bank-to-bank wire transfer) Payment.
12amountMonetary amount including tax79Var. Amount of charge with tax included0 yen or more should be specified.
13pay_typePurchase type19Fixed 0: One-time charge 
15service_typeService type19Fixed 0: Settlement (Purchases)
20terminal_typeType of terminal used by customer19  Fixed 0: PC 1: Feature phone When omitted, "0" is applied.
*For details, please refer to the Setting the Terminal Type for Requests (Basic Specifications).
21success_urlURL when payment is completed500XVar. URL to which the screen returns  
22cancel_urlURL to go to when the payment is canceled500XVar. URL to which the screen returns  
23error_urlURL to go to when an error occurs500XVar. URL to which the screen returns  
24pagecon_urlCGI for payment notification500XVar.URL to which the result is notified SSL communication is required.
25free1Free 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 "?".
26free2Free 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 "?".
27free3Free 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 "?".
28free_csvFree item4000M  Var. Please refer to the payment-specific tag "free_csv."
Repeat when purchasing more than one item (field for displaying on the screen)
29dtl_rownoLine number for detailed description39Var. 1, 2, 3, ...Row number in the details (order of display)Required if detail are used. Increment the number by 1 each time. *Max number of details is 999 items.
30dtl_item_idProduct ID for detailed description20XVar.Item ID in details to be displayed on screen Mandatory when this is set to any detail item ID in other details.
31dtl_item_nameDetailed item names40MVar.Item name of the details to be displayed on screen 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 "?". Mandatory when this is set to any detailed item ID in other details. Mandatory field for NP Atobarai when the settings for details are configured. For Pay-easy payment, the following characters are prohibited:
(*) Asterisk
(_) Underscore
(@) at symbol
32dtl_item_countQuantity for detailed description69Var.Purchase quantity of the details to be displayed on screen Mandatory when this is set to any detail quantity in other details. Mandatory field for NP Atobarai when the settings for details are configured.
33dtl_taxAmount of tax for detailed description89  Var.The amount of tax for the subtotal in the detailed description   
34dtl_amountMonetary amount including tax for detailed description89Var.Subtotal amount (including tax) of details to be displayed on screen Mandatory when this is set to any detail amount (incl. tax) in other details. Mandatory field for NP Atobarai when the settings for details are configured.
35dtl_free1Detail free field 13000M  Var.   *This field will not be stored in our payment system. If you wish to use this, please confirm with our sales representative.
36dtl_free2Detail free field 23000M  Var.   *This field will not be stored in our payment system. If you wish to use this, please confirm with our sales representative.
37dtl_free3Detail free field 33000M  Var.   *This field will not be stored in our payment system. If you wish to use this, please confirm with our sales representative.
Repeated up to here when purchasing more than one item
38request_dateDate and time of request149FixedYYYYMMDDHHMISS Date and time when this function is requested by the merchant.
39limit_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.
40sps_hashcodeChecksum40XFixedThe checksum for the message represented as a value Please refer to the Method for Generating Checksums (Basic Specifications).
SEQ Tag element name Field name Chars Format Req'd Type Description Remarks
1pay_methodPayment method1000XVar. Please refer to the payment method tag "pay_method"for details.Specifies the payment method. (one or more can be specified)
2merchant_idMerchant ID59FixedID for identifying the merchant Assigned by SBPS
3service_idService ID39FixedID for identifying the merchant's service Assigned by SBPS
4cust_codeCustomer ID64XVar.A customer ID managed by the merchant This 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 ID129  FixedCustomer ID managed by SBPS Not to be set for this linkage model (null characters)
6sps_payment_noSBPS payment method management number39  FixedPayment method management number controlled by SBPS Not to be set for this linkage model (null characters)
7order_idPurchase ID38XVar.A purchase ID managed by the merchant This must be unique with respect to the combination of merchant ID and service ID. *Set a unique ID also for the cancellation of recurring billing (simplified).
8item_idProduct ID32XVar.A product ID managed by the merchant   
9pay_item_idFinancial Institution Item ID32X  Var.   Not to be set for this linkage model (null characters)
10item_nameProduct name40MVar.A product name of your choice 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 "?". *If not set, the item name is not displayed on the Purchase Confirmation screen. Mandatory field for NP Atobarai. For Pay-easy payment, the following characters are prohibited:
(*) Asterisk
(_) Underscore
(@) at symbol
11taxAmount of tax79Var.Amount of collecting taxes 0 yen or more should be specified. *Mandatory only for General Wire Transfer (bank-to-bank wire transfer) Payment.
12amountMonetary amount including tax79Var.Amount of charge with tax included 0 yen or more should be specified.
13pay_typePurchase type19Fixed2: Recurring charge (based on term or usage rate)  
14auto_charge_typeAutomated charge type19Fixed0: No automated charge
1: Automated charge
Mandatory field only if the purchase type is "Recurring billing (simplified)" or "Recurring billing (fixed term/pay as you go)" When the purchase type is "Recurring billing (fixed term/pay as you go)," only "No automated charge" can be specified.
15service_typeService type19Fixed0: Settlement (Purchases)
1: Cancel (cancel monthly billing)
When the purchase type is "One-time billing" or "Recurring billing (fixed term/pay as you go)," only "Settlement (purchase)" can be specified For "Cancel (cancel monthly billing)," only "Recurring billing (simplified)" can be specified.
16div_settelePayment category19Fixed0: Advance payment Mandatory field only if the purchase type is "Recurring billing (simplified)" or "Recurring billing (fixed term/pay as you go)" When the purchase type is "One-time billing," this field is not set.
20terminal_typeType of terminal used by customer19  Fixed0: PC
1: Feature phone
When omitted, "0" is applied.
*For details, please refer to the Setting the Terminal Type for Requests (Basic Specifications).
21success_urlURL when payment is completed500XVar.URL to which the screen returns   
22cancel_urlURL to go to when the payment is canceled500XVar.URL to which the screen returns   
23error_urlURL to go to when an error occurs500XVar.URL to which the screen returns   
24pagecon_urlCGI for payment notification500XVar.URL to which the result is notified SSL communication is required.
25free1Free 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 "?".
26free2Free 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 "?".
27free3Free 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 "?".
28free_csvFree item4000M  Var. Item names, address, and other informationPlease refer to the payment-specific tag "free_csv."
Repeat when purchasing more than one item (field for displaying on the screen)
29dtl_rownoLine number for detailed description39Var.1, 2, 3, ...Row number in the details (order of display) Required if detail are used. Increment the number by 1 each time. *Max number of details is 999 items.
30dtl_item_idProduct ID for detailed description20XVar.Item ID in details to be displayed on screen Mandatory when this is set to any detail item ID in other details.
31dtl_item_nameDetailed item names40MVar.Item name of the details to be displayed on screen 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 "?". Mandatory when this is set to any detailed item ID in other details. Mandatory field for NP Atobarai when the settings for details are configured. For Pay-easy payment, the following characters are prohibited:
(*) Asterisk
(_) Underscore
(@) at symbol
32dtl_item_countQuantity for detailed description69Var.Purchase quantity of the details to be displayed on screen Mandatory when this is set to any detail quantity in other details. Mandatory field for NP Atobarai when the settings for details are configured.
33dtl_taxAmount of tax for detailed description89  Var.The amount of tax for the subtotal in the detailed description   
34dtl_amountMonetary amount including tax for detailed description89Var.Subtotal amount (including tax) of details to be displayed on screen Mandatory when this is set to any detail amount (incl. tax) in other details. Mandatory field for NP Atobarai when the settings for details are configured.
35dtl_free1Detail free field 13000M  Var.   *This field will not be stored in our payment system. If you wish to use this, please confirm with our sales representative.
36dtl_free2Detail free field 23000M  Var.   *This field will not be stored in our payment system. If you wish to use this, please confirm with our sales representative.
37dtl_free3Detail free field 33000M  Var.   *This field will not be stored in our payment system. If you wish to use this, please confirm with our sales representative.
Repeated up to here when purchasing more than one item
38request_dateDate and time of request149FixedYYYYMMDDHHMISS Date and time when this function is requested by the merchant.
39limit_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.
40sps_hashcodeChecksum40XFixedThe checksum for the message represented as a value Please refer to the Method for Generating Checksums (Basic Specifications).
SEQ Tag element name Field name Chars Format Req'd Type Description Remarks
1pay_methodPayment method1000XVar.Please refer to the payment method tag "pay_method"for details.Specifies the payment method. (one or more can be specified)
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 ID129  FixedCustomer ID managed by SBPSNot to be set for this linkage model (null characters)
6sps_payment_noSBPS payment method management number39  FixedPayment method management number controlled by SBPSNot to be set for this linkage model (null characters)
7order_idPurchase ID38XVar.A purchase ID managed by the merchantThis must be unique with respect to the combination of merchant ID and service ID. *Set a unique ID also for the cancellation of recurring billing (simplified).
8item_idProduct ID32XVar.A product ID managed by the merchant  
9pay_item_idFinancial Institution Item ID32X  Var.  Not to be set for this linkage model (null characters)
10item_nameProduct name40MVar.A product name of your choiceJapanese 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 "?". *If not set, the item name is not displayed on the Purchase Confirmation screen. Mandatory field for NP Atobarai. For Pay-easy payment, the following characters are prohibited:
(*) Asterisk
(_) Underscore
(@) at symbol
11taxAmount of tax79Var.Amount of collecting taxes0 yen or more should be specified. *Mandatory only for General Wire Transfer (bank-to-bank wire transfer) Payment.
12amountMonetary amount including tax79Var.Amount of charge with tax included0 yen or more should be specified.
13pay_typePurchase type19Fixed1: Recurring charge (simple) 
14auto_charge_typeAutomated charge type19Fixed0: No automated charge
1: Automated charge
Mandatory field only if the purchase type is "Recurring billing (simplified)" or "Recurring billing (fixed term/pay as you go)" When the purchase type is "Recurring billing (fixed term/pay as you go)," only "No automated charge" can be specified.
15service_typeService type19Fixed0: Settlement (Purchases)
1: Cancel (cancel monthly billing)
When the purchase type is "One-time billing" or "Recurring billing (fixed term/pay as you go)," only "Settlement (purchase)" can be specified For "Cancel (cancel monthly billing)," only "Recurring billing (simplified)" can be specified.
16div_settelePayment category19Fixed0: Advance paymentMandatory field only if the purchase type is "Recurring billing (simplified)" or "Recurring billing (fixed term/pay as you go)" When the purchase type is "One-time billing," this field is not set.
17last_charge_monthLast charged month69  FixedYYYYMMRecurring billing is not performed from the month following the set month. Can only be specified if the purchase type is "Recurring billing (simplified)." Not set for "Recurring billing (fixed term/pay as you go)."
18camp_typeCampaign type19Fixed0: No campaign
1: First month free
Can only be specified when the purchase type is "Recurring billing (simplified)" and is mandatory. Not set for "Recurring billing (fixed term/pay as you go)." *Merchants who applied for the recurring billing (simplified) on February 1, 2022, or later cannot use the request for billing the cancellation in the first month using "1: First month free" for the credit card payment. (If a request is made, you will be redirected to the system error screen. )
19tracking_idTracking ID14XFixedID assigned by SBPS at time of purchaseCan only be specified if the service type is "Cancel (Cancel monthly billing)" and mandatory.
Unique value for each payment method
20terminal_typeType of terminal used by customer19  Fixed0: PC
1: Feature phone
When omitted, "0" is applied.
*For details, please refer to the Setting the Terminal Type for Requests (Basic Specifications).
21success_urlURL when payment is completed500XVar.URL to which the screen returns  
22cancel_urlURL to go to when the payment is canceled500XVar.URL to which the screen returns  
23error_urlURL to go to when an error occurs500XVar.URL to which the screen returns  
24pagecon_urlCGI for payment notification500XVar.URL to which the result is notifiedSSL communication is required.
25free1Free 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 "?".
26free2Free 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 "?".
27free3Free 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 "?".
28free_csvFree item4000M  Var.Item names, address, and other informationPlease refer to the payment-specific tag "free_csv."
Repeat when purchasing more than one item (field for displaying on the screen)
29dtl_rownoLine number for detailed description39Var.1, 2, 3, ...Row number in the details (order of display)Required if detail are used. Increment the number by 1 each time. *Max number of details is 999 items.
30dtl_item_idProduct ID for detailed description20XVar.Item ID in details to be displayed on screenMandatory when this is set to any detail item ID in other details.
31dtl_item_nameDetailed item names40MVar.Item name of the details to be displayed on screenJapanese 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 "?". Mandatory when this is set to any detailed item ID in other details. Mandatory field for NP Atobarai when the settings for details are configured. For Pay-easy payment, the following characters are prohibited:
(*) Asterisk
(_) Underscore
(@) at symbol
32dtl_item_countQuantity for detailed description69Var.Purchase quantity of the details to be displayed on screenMandatory when this is set to any detail quantity in other details. Mandatory field for NP Atobarai when the settings for details are configured.
33dtl_taxAmount of tax for detailed description89  Var.The amount of tax for the subtotal in the detailed description  
34dtl_amountMonetary amount including tax for detailed description89Var.Subtotal amount (including tax) of details to be displayed on screenMandatory when this is set to any detail amount (incl. tax) in other details. Mandatory field for NP Atobarai when the settings for details are configured.
35dtl_free1Detail free field 13000M  Var.  *This field will not be stored in our payment system. If you wish to use this, please confirm with our sales representative.
36dtl_free2Detail free field 23000M  Var.  *This field will not be stored in our payment system. If you wish to use this, please confirm with our sales representative.
37dtl_free3Detail free field 33000M  Var.  *This field will not be stored in our payment system. If you wish to use this, please confirm with our sales representative.
Repeated up to here when purchasing more than one item
38request_dateDate and time of request149FixedYYYYMMDDHHMISSDate and time when this function is requested by the merchant.
39limit_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.
40sps_hashcodeChecksum40XFixedThe checksum for the message represented as a value Please refer to the Method for Generating Checksums (Basic Specifications).
Function IDA02-1
Process namePurchase Result CGI:
FlowSBPS→Merchant
DestinationDesignated 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).

  • One-time charge
  • Recurring charge (based on term or usage rate)
  • Recurring charge (simple)
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  
7order_idPurchase ID38XVar.  
8item_idProduct ID32XVar.  
9pay_item_idFinancial Institution Item ID32X  Var.  
10item_nameProduct name40M  Var.  
11taxAmount of tax79  Var.  
12amountMonetary amount including tax79Var.  
13pay_typePurchase type19Fixed  
14auto_charge_typeAutomated charge type19Fixed  
15service_typeService type19Fixed  
16div_settelePayment category19Fixed  
17last_charge_monthLast charged month69  Fixed  
18camp_typeCampaign type19Fixed  
19tracking_idTracking ID14X  FixedUnique value for each payment method
20terminal_typeType of terminal used by customer19  Fixed  
21free1Free field 120M  Var.  
22free2Free field 220M  Var.  
23free3Free field 320M  Var.  
Repeat when purchasing more than one item (field for displaying on the screen)
24dtl_rownoLine number for detailed description29 Var.  
25dtl_item_idProduct ID for detailed description20X  Var.  
26dtl_item_nameDetailed item names40M  Var.  
27dtl_item_countQuantity for detailed description69  Var.  
28dtl_taxAmount of tax for detailed description89  Var.  
29dtl_amountMonetary amount including tax for detailed description89  Var.  
30dtl_free1Detail free field 13000M  Var.  
31dtl_free2Detail free field 23000M  Var.  
32dtl_free3Detail free field 33000M  Var.  
Repeated up to here when purchasing more than one item
33request_dateDate and time of request149Fixed
Fields to be set when the result is returned
34res_pay_methodProcessed result Payment method20XVar.  Payment method selected at time of purchase request
35res_resultStatus of processing result2XFixedOK: Request processing OK
NG: Request NG
PY: Deposit notification
CN: Overdue payment cancellation
Please see here for more details.
36res_tracking_idTracking ID for processing14XFixedID assigned by SBPS at time of purchaseUnique value for each payment method
37res_sps_cust_noSBPS Customer ID for processing129  FixedCustomer ID managed by SBPS  
38res_sps_payment_noSBPS payment method management number for processing39  FixedPayment method management number controlled by SBPS  
39res_payinfo_keyCustomer payment information145X  Var.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)
• Recruit Kantan Shiharai: Recruit's order number (fixed 15 digits)
* When the end user payment method is the convenience store payment, the string "webcvs," prefixes this field.
Receive the Deposit Receipt Notification, etc., at a later date.
・ d payment (Carrier ・ Wallet): When the Purchase type is "Periodic purchase", DOCOMO's approval number (fixed 12 digits)
• SoftBank Matomete Shiharai (A): Order number of the financial institution
• Invoice (convenience store payment, general wire transfer, or Pay-easy): Alphanumeric characters consisting of deposit category code, amount deposited, cumulative amount of deposit,
and email address delimited with comma (,)
*The deposit category code of invoice is fixed to one digit and the notification details are as follows.
P: Prompt report/C: Cancel prompt report/D: Confirmed report/G: Cancel confirmed report
*Some deposit category codes are not used depending on the collection agent.
Example: Prompt report deposit of 10,000 yen; Cumulative amount of 15,000 yen: P,10000,15000,aaa@aaa.com
• UnionPay Net Payment: UnionPay Transaction ID
• Merpay Online Payment Transaction ID for user check
• Wallet Payment Service (Type-Y): Number consisting of the breakdowns of the amount for the credit card and PayPay delimited with comma (,) (for example,
(500,300: when the amounts for the credit card and PayPay are 500 yen and 300 yen, respectively)
• PayPay (Online Payment): PayPay Payment Number
• EPOS Kantan Kessai Service: For a purchase, 'amount to be paid using a credit card + "," + amount to be paid using a coupon + "," + amount to be paid using points'
* "0" is set to each unused item before returned
• Rakuten Pay (Online Payment) V2: charge_id
40res_payment_dateHandle completion date/time149  Var.YYYYMMDDHHMISSIf the processed result status is OK, the processed date of the financial institution.
If the processing result status is NG, there may be no processing date and time.
If the processing result status is PY, it will be the notification processing date.
41res_err_codeError code4X  Var.See list of error codes  
42res_dateDate and time of response149Var.YYYYMMDDHHMISSDate and time responded by SBPS
43limit_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.
44sps_hashcodeChecksum40XFixedThe checksum for the message represented as a valuePlease refer to the Method for Generating Checksums (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  
7order_idPurchase ID38XVar.  
8item_idProduct ID32XVar.  
9pay_item_idFinancial Institution Item ID32X  Var.  
10item_nameProduct name40M  Var.  
11taxAmount of tax79  Var.  
12amountMonetary amount including tax79Var.  
13pay_typePurchase type19Fixed  
14auto_charge_typeAutomated charge type19Fixed  
15service_typeService type19Fixed  
16div_settelePayment category19Fixed  
17last_charge_monthLast charged month69  Fixed  
18camp_typeCampaign type19Fixed  
19tracking_idTracking ID14X  FixedUnique value for each payment method
20terminal_typeType of terminal used by customer19  Fixed  
21free1Free field 120M  Var.  
22free2Free field 220M  Var.  
23free3Free field 320M  Var.  
Repeat when purchasing more than one item (field for displaying on the screen)
24dtl_rownoLine number for detailed description29 Var.  
25dtl_item_idProduct ID for detailed description20X  Var.  
26dtl_item_nameDetailed item names40M  Var.  
27dtl_item_countQuantity for detailed description69  Var.  
28dtl_taxAmount of tax for detailed description89  Var.  
29dtl_amountMonetary amount including tax for detailed description89  Var.  
30dtl_free1Detail free field 13000M  Var.  
31dtl_free2Detail free field 23000M  Var.  
32dtl_free3Detail free field 33000M  Var.  
Repeated up to here when purchasing more than one item
33request_dateDate and time of request149Fixed
Fields to be set when the result is returned
34res_pay_methodProcessed result Payment method20XVar.  Payment method selected at time of purchase request
35res_resultStatus of processing result2XFixedOK: Request processing OK
NG: Request NG
Please see here for more details.
36res_tracking_idTracking ID for processing14XFixedID assigned by SBPS at time of purchaseUnique value for each payment method
37res_sps_cust_noSBPS Customer ID for processing129  FixedCustomer ID managed by SBPS  
38res_sps_payment_noSBPS payment method management number for processing39  FixedPayment method management number controlled by SBPS  
39res_payinfo_keyCustomer payment information145X  Var.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)
• Recruit Kantan Shiharai: Recruit's order number (fixed 15 digits)
* When the end user payment method is the convenience store payment, the string "webcvs," prefixes this field.
Receive the Deposit Receipt Notification, etc., at a later date.
・ d payment (Carrier ・ Wallet): When the Purchase type is "Periodic purchase", DOCOMO's approval number (fixed 12 digits)
• SoftBank Matomete Shiharai (A): Order number of the financial institution
• Invoice (convenience store payment, general wire transfer, or Pay-easy): Alphanumeric characters consisting of deposit category code, amount deposited, cumulative amount of deposit,
and email address delimited with comma (,)
*The deposit category code of invoice is fixed to one digit and the notification details are as follows.
P: Prompt report/C: Cancel prompt report/D: Confirmed report/G: Cancel confirmed report
*Some deposit category codes are not used depending on the collection agent.
Example: Prompt report deposit of 10,000 yen; Cumulative amount of 15,000 yen: P,10000,15000,aaa@aaa.com
• UnionPay Net Payment: UnionPay Transaction ID
• Merpay Online Payment Transaction ID for user check
• Wallet Payment Service (Type-Y): Number consisting of the breakdowns of the amount for the credit card and PayPay delimited with comma (,) (for example,
(500,300: when the amounts for the credit card and PayPay are 500 yen and 300 yen, respectively)
• PayPay (Online Payment): PayPay Payment Number
• EPOS Kantan Kessai Service: For a purchase, 'amount to be paid using a credit card + "," + amount to be paid using a coupon + "," + amount to be paid using points'
* "0" is set to each unused item before returned
• Rakuten Pay (Online Payment) V2: charge_id
40res_payment_dateHandle completion date/time149  Var.YYYYMMDDHHMISSIf the processed result status is OK, the processed date of the financial institution.
If the processing result status is NG, there may be no processing date and time.
41res_err_codeError code4X  Var.See list of error codes  
42res_dateDate and time of response149Var.YYYYMMDDHHMISSDate and time responded by SBPS
43limit_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.
44sps_hashcodeChecksum40XFixedThe checksum for the message represented as a valuePlease refer to the Method for Generating Checksums (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  
7order_idPurchase ID38XVar.  
8item_idProduct ID32XVar.  
9pay_item_idFinancial Institution Item ID32X  Var.  
10item_nameProduct name40M  Var.  
11taxAmount of tax79  Var.  
12amountMonetary amount including tax79Var.  
13pay_typePurchase type19Fixed  
14auto_charge_typeAutomated charge type19Fixed  
15service_typeService type19Fixed  
16div_settelePayment category19Fixed  
17last_charge_monthLast charged month69  Fixed  
18camp_typeCampaign type19Fixed  
19tracking_idTracking ID14X  FixedUnique value for each payment method
20terminal_typeType of terminal used by customer19  Fixed  
21free1Free field 120M  Var.  
22free2Free field 220M  Var.  
23free3Free field 320M  Var.  
Repeat when purchasing more than one item (field for displaying on the screen)
24dtl_rownoLine number for detailed description29 Var.  
25dtl_item_idProduct ID for detailed description20X  Var.  
26dtl_item_nameDetailed item names40M  Var.  
27dtl_item_countQuantity for detailed description69  Var.  
28dtl_taxAmount of tax for detailed description89  Var.  
29dtl_amountMonetary amount including tax for detailed description89  Var.  
30dtl_free1Detail free field 13000M  Var.  
31dtl_free2Detail free field 23000M  Var.  
32dtl_free3Detail free field 33000M  Var.  
Repeated up to here when purchasing more than one item
33request_dateDate and time of request149Fixed
Fields to be set when the result is returned
34res_pay_methodProcessed result Payment method20XVar.  Payment method selected at time of purchase request
35res_resultStatus of processing result2XFixedOK: Request processing OK
CR: Cancelled billing
CC: Cancellation on the carrier side
CL: Cancellation due to last charged month
Please see here for more details.
36res_tracking_idTracking ID for processing14XFixedID assigned by SBPS at time of purchaseUnique value for each payment method
37res_sps_cust_noSBPS Customer ID for processing129  FixedCustomer ID managed by SBPS  
38res_sps_payment_noSBPS payment method management number for processing39  FixedPayment method management number controlled by SBPS  
39res_payinfo_keyCustomer payment information145X  Var.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)
• Recruit Kantan Shiharai: Recruit's order number (fixed 15 digits)
* When the end user payment method is the convenience store payment, the string "webcvs," prefixes this field.
Receive the Deposit Receipt Notification, etc., at a later date.
・ d payment (Carrier ・ Wallet): When the Purchase type is "Periodic purchase", DOCOMO's approval number (fixed 12 digits)
• SoftBank Matomete Shiharai (A): Order number of the financial institution
• Invoice (convenience store payment, general wire transfer, or Pay-easy): Alphanumeric characters consisting of deposit category code, amount deposited, cumulative amount of deposit,
and email address delimited with comma (,)
*The deposit category code of invoice is fixed to one digit and the notification details are as follows.
P: Prompt report/C: Cancel prompt report/D: Confirmed report/G: Cancel confirmed report
*Some deposit category codes are not used depending on the collection agent.
Example: Prompt report deposit of 10,000 yen; Cumulative amount of 15,000 yen: P,10000,15000,aaa@aaa.com
• UnionPay Net Payment: UnionPay Transaction ID
• Merpay Online Payment Transaction ID for user check
• Wallet Payment Service (Type-Y): Number consisting of the breakdowns of the amount for the credit card and PayPay delimited with comma (,) (for example,
(500,300: when the amounts for the credit card and PayPay are 500 yen and 300 yen, respectively)
• PayPay (Online Payment): PayPay Payment Number
• EPOS Kantan Kessai Service: For a purchase, 'amount to be paid using a credit card + "," + amount to be paid using a coupon + "," + amount to be paid using points'
* "0" is set to each unused item before returned
• Rakuten Pay (Online Payment) V2: charge_id
40res_payment_dateHandle completion date/time149  Var.YYYYMMDDHHMISSIf the processed result status is OK, the processed date of the financial institution.
If the processing result status is NG, there may be no processing date and time.
If the processing result status is PY, it will be the notification processing date.
41res_err_codeError code4X  Var.See list of error codes  
42res_dateDate and time of response149Var.YYYYMMDDHHMISSDate and time responded by SBPS
43limit_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.
44sps_hashcodeChecksum40XFixedThe checksum for the message represented as a valuePlease refer to the Method for Generating Checksums (Basic Specifications).

Types of Processed Result Status in Purchase Result CGI

The following are the seven types of processed result status.

The decision to provide merchant services should be based on the Processed result status of "Purchase result CGI" from us.

Status of processing resultDescription
OK (Payment Processing OK)Notification is made when the payment is successfully processed.
NG (Payment Processing NG)Notification is made when the payment processing fails.
CR (Cancellation of recurring billing (simplified))Notification is made when the monthly billing in Recurring Billing (simplified) fails.
CC (Cancellation on the carrier side)Notification is made when billing recurring billing (simplified) on the next month onward fails due to cancellation of mobile subscription, recurring billing items, and so on.
PY (Deposit receipt notification)Notification is made that a credit has been made in an offline payment.
CN (Expiration notification)Notification is made that the payment due date of payment slip has passed in an offline payment.
CL (Cancellation due to last charged month)Notification is made when recurring billing (simplified) is suspended in the last charged month.

The timing of notification of processed result status, status of occurrence, and a decision for each processed result status made at the Merchant for provision of the services are as follows.

  • One-time charge
  • Recurring charge (based on term or usage rate)
  • Recurring charge (simple)
Status of processing resultTiming of notificationService to be provided by Merchant
OK (Payment Processing OK)One-timeProvide services
NG (Payment Processing NG)One-timeNot provide services
Payment methodStatus of processing result
OKNG*1
Credit card payment / ID verification service (3D secure)
UnionPay Net Payment
PayPay (Online Payment)
SoftBank Matomete Shiharai (A)
SoftBank Matomete Shiharai (B)
d Payment (Carrier/Wallet)
au Kantan Kessai Service
WebMoney payment
BitCash payment
Net Cash payment
JCB PREMO payment
Wallet payment service (Type-Y)
Rakuten Pay (Online Payment)V2
Alipay+
PayPal Payment
LINE Pay
Merpay Online Payment
NetMile payment
Rakuten Edy payment
Mobile Suica Payment
T-point program (online payment)
Apple Pay
NP Atobarai
au PAY (Online Payment)
EPOS Kantan Kessai Service
WeChatPay
*1: Depending on the specifications of the payment institution, the purchase result CGI (A02-1) may not be executed and the user may be transferred to an error screen.
Status of processing resultTiming of notificationService to be provided by Merchant
OK (Payment Processing OK)One-timeProvide services
NG (Payment Processing NG)One-timeNot provide services
PY (Deposit receipt notification)When payment was madeProvide services
CN (Expiration notification)When the payment due expiredNot provide services
Payment methodStatus of processing result
OKNG*3PYCN
Recruit Kantan Shiharai○※2
Convenience store payment○※1
Pay-easy payment○※1
General wire transfer (bank-to-bank wire transfer) payment○※1
*1: Notifies that the request has been captured.
*2: This function is used for Recruit Kantan Shiharai only when the end user payment method includes convenience store payment.
*3: Depending on the specifications of the payment institution, the purchase result CGI (A02-1) may not be executed and the user may be transferred to an error screen.
Status of processing resultTiming of notificationService to be provided by Merchant
OK (Payment Processing OK)One-timeProvide services
NG (Payment Processing NG)One-timeNot provide services
Payment methodStatus of processing result
OKNG*1
SoftBank Matomete Shiharai (B)
d Payment (Carrier/Wallet)
au Kantan Kessai Service
Rakuten Pay (Online Payment)V2
Recruit Kantan Shiharai
*1: Depending on the specifications of the payment institution, the purchase result CGI (A02-1) may not be executed and the user may be transferred to an error screen.

Status of processing resultTiming of notificationService to be provided by Merchant
OK (Payment Processing OK)One-timeProvide services
NG (Payment Processing NG)One-timeNot provide services
CR (Cancellation of recurring billing (simplified))Monthly (beginning of month)Immediately stop providing services
CC (Cancellation on the carrier side)DailyStop providing services at end of the month of notification
CL (Cancellation due to last charged month)Monthly (beginning of month)Confirm that provision of services has ended

Payment methodStatus of processing result
OKNG*1CRCCCL
Credit card payment / ID verification service (3D secure)
d Payment (Carrier/Wallet)
au Kantan Kessai Service
Recruit Kantan Shiharai○※2
*1: Depending on the specifications of the payment institution, the purchase result CGI (A02-1) may not be executed and the user may be transferred to an error screen.
*2: This function is used for Recruit Kantan Shiharai only when the end user payment method includes convenience store payment.
Function IDA02-2
Process nameResponse to Purchase Result CGI
FlowMerchant→SBPS
DestinationNotification source of purchase result CGI
Transmission methodHTTP POST
Transmission character encodingShift-JIS, text / csv

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 Field name Chars Format Req'd Description Remarks
1Processed result2XOK/NGProcessed result on the Merchant side.
*Be sure to return OK if "res_result" of the result CGI is NG.
2Error message100M Message to be displayed when an error occurs on the Merchant sideNot required when the process is "OK."
*For detailed specifications, refer to the Link Type (Basic Specifications).
Function IDA03-1
Process namePurchase Result (redirect back to Merchant's screen)
FlowBrowser → Merchant
DestinationDesignated URL (when completed)
Transmission methodHTTP 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  
7order_idPurchase ID38XVar.  
8item_idProduct ID32XVar.  
9pay_item_idFinancial Institution Item ID32X  Var.  
10item_nameProduct name40M  Var.  
11taxAmount of tax79  Var.  
12amountMonetary amount including tax79Var.  
13pay_typePurchase type19Fixed  
14auto_charge_typeAutomated charge type19Fixed  
15service_typeService type19Fixed  
16div_settelePayment category19Fixed  
17last_charge_monthLast charged month69  Fixed  
18camp_typeCampaign type19Fixed  
19tracking_idTracking ID14X  FixedUnique value for each payment method
20terminal_typeType of terminal used by customer19  Fixed  
21free1Free field 120M  Var.  
22free2Free field 220M  Var.  
23free3Free field 320M  Var.  
Repeat when purchasing more than one item (field for displaying on the screen)
24dtl_rownoLine number for detailed description29 Var.  
25dtl_item_idProduct ID for detailed description20X Var.  
26dtl_item_nameDetailed item names40M Var.  
27dtl_item_countQuantity for detailed description69 Var.  
28dtl_taxAmount of tax for detailed description89 Var.  
29dtl_amountMonetary amount including tax for detailed description89 Var.  
30dtl_free1Detail free field 13000M Var.  
31dtl_free2Detail free field 23000M Var.  
32dtl_free3Detail free field 33000M Var.  
Repeated up to here when purchasing more than one item
33request_dateDate and time of request149Fixed  
Fields to be set when the result is returned
34res_pay_methodProcessed result Payment method20XVar.  Payment method selected at time of purchase request
35res_resultStatus of processing result2XFixedOK: Request processing OK NG: Request NG  
36res_tracking_idTracking ID for processing14XFixedID assigned by SBPS at time of purchaseUnique value for each payment method
37res_sps_cust_noSBPS Customer ID for processing129  FixedCustomer ID managed by SBPS  
38res_sps_payment_noSBPS payment method management number for processing39  FixedPayment method management number controlled by SBPS  
39res_payinfo_keyCustomer payment information145X  Var.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)
• Recruit Kantan Shiharai: Recruit's order number (fixed 15 digits)
・ d payment (Carrier ・ Wallet): When the Purchase type is "Periodic purchase", DOCOMO's approval number (fixed 12 digits)
• SoftBank Matomete Shiharai (A): Order number of the financial institution
• Invoice: Alphanumeric characters consisting of deposit category code, amount deposited, cumulative amount of deposit, and e-mail address delimited with comma (,)
*The deposit category code of invoice is fixed to one digit and the notification details are as follows.
P: Prompt report/C: Cancel prompt report/D: Confirmed report/G: Cancel confirmed report
Example: Prompt report deposit of 10,000 yen; Cumulative amount of 15,000 yen:
P,10000,15000,aaa@aaa.com.
• UnionPay Net Payment: UnionPay Transaction ID
• Merpay Online Payment Transaction ID for user check
• Wallet Payment Service (Type-Y): Number consisting of the breakdowns of the amount for the credit card and PayPay delimited with comma (,) (for example, (500,300: when the amounts for the credit card and PayPay are 500 yen and 300 yen, respectively)
• PayPay (Online Payment): PayPay Payment Number
• Rakuten Pay (Online Payment) V2: charge_id
40res_payment_dateHandle completion date/time149  Var.YYYYMMDDHHMISSIf the processed result status is OK, the processed date of the financial institution.
If the processing result status is NG, there may be no processing date and time.
If the processing result status is PY, it will be the notification processing date.
41res_err_codeError code4X  Var.See list of error codes  
42res_dateDate and time of response149Var.YYYYMMDDHHMISSDate and time responded by SBPS
43limit_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.
44sps_hashcodeChecksum40XFixedThe checksum for the message represented as a valuePlease refer to the Method for Generating Checksums (Basic Specifications).

Close notification (Rakuten Pay (Online Payment) and NP Atobarai only)
*For Rakuten Pay (online payment) V2, there is no asynchronous notification.

Function IDA04-1
Process nameClose Notification
FlowSBPS→Merchant
DestinationDesignated 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  
7order_idPurchase ID38XVar.  
8item_idProduct ID32XVar.  
9pay_item_idFinancial Institution Item ID32X  Var.  
10item_nameProduct name40M  Var.  
11taxAmount of tax79  Var.  
12amountMonetary amount including tax79Var.  
13pay_typePurchase type19Fixed  
14auto_charge_typeAutomated charge type19Fixed  
15service_typeService type19Fixed  
16div_settelePayment category19Fixed  
17last_charge_monthLast charged month69  Fixed  
18camp_typeCampaign type19Fixed  
19tracking_idTracking ID14X  FixedUnique value for each payment method
20terminal_typeType of terminal used by customer19  Fixed  
21free1Free field 120M  Var.  
22free2Free field 220M  Var.  
23free3Free field 320M  Var.  
Repeat when purchasing more than one item (field for displaying on the screen)
24dtl_rownoLine number for detailed description29 Var.  
25dtl_item_idProduct ID for detailed description20X Var.  
26dtl_item_nameDetailed item names40M Var.  
27dtl_item_countQuantity for detailed description69 Var.  
28dtl_taxAmount of tax for detailed description89 Var.  
29dtl_amountMonetary amount including tax for detailed description89 Var.  
30dtl_free1Detail free field 13000M Var.  
31dtl_free2Detail free field 23000M Var.  
32dtl_free3Detail free field 33000M Var.  
Repeated up to here when purchasing more than one item
33request_dateDate and time of request149Fixed
Fields to be set when the result is returned
34res_pay_methodProcessed result Payment method20XVar. Payment method selected at time of purchase request
35res_resultStatus of processing result2XFixedOK: Request processing OK NG: Request NG  
36res_tracking_idTracking ID for processing14XFixedID assigned by SBPS at time of purchaseUnique value for each payment method
37res_sps_cust_noSBPS Customer ID for processing129  FixedCustomer ID managed by SBPS  
38res_sps_payment_noSBPS payment method management number for processing39  FixedPayment method management number controlled by SBPS  
39res_payinfo_keyCustomer payment information145X  Var.Rakuten Pay (Online Payment)
R01: Authorization Result (Fixed Term/Pay as You Go) R02: Amount Change Result
R03: NP Atobarai Settlement Result N01: Transaction Registration Result
N02: Authorization Result
N03: Settlement Result
N04: Cancellation Result
N05: Refund Result
Set the applicable processing category value for closed process in Rakuten Pay (Online Payment) and NP Atobarai.
40res_payment_dateHandle completion date/time149Var.YYYYMMDDHHMISSIf the processed result status is OK, the processed date of the financial institution.
If the processing result status is NG, there may be no processing date and time.
If the processing result status is PY, it will be the notification processing date.
41res_err_codeError code4XVar.See list of error codes
42res_dateDate and time of response149Var.YYYYMMDDHHMISSDate and time responded by SBPS
43limit_secondResponse limit time49Var.Timeout when a request is issuedThe default value of 600 is applied if this item is omitted.
44sps_hashcodeChecksum40XFixedThe checksum for the message represented as a valuePlease refer to the Method for Generating Checksums (Basic Specifications).

* Rakuten Pay (Online Payment)

Settlement, amount change, and recurring billing (fixed term/pay as you go) purchase are closed separately. Use this function to make close notification asynchronously. For this reason, provide services after receiving close notification.

*NP Atobarai

Purchase, settlement, cancellation, and refund are closed separately. Use this function to make close notification asynchronously. For this reason, provide or stop services after receiving close notification. Purchase is closed after notifications of transaction registration result and authorization result.

Specify the payment method in pay_method. (one or more can be specified)
When a payment method is selected, the payment information input screen moves to the screen for each selected payment method.
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.
*If the service type is "1: Cancel (Cancel monthly billing)", be sure to specify.

Setting ValuePayment methodOne-time chargeRecurring Billing (Fixed Term/Pay as You Go)Recurring Billing (Simplified)
creditCredit Card Payment
credit3d2Credit Card Payment (ID Verification Service (3D Secure))
UnionPayUnionPay Net Payment
PayPayPayPay (Online Payment)
webcvsConvenience store payment
PayeasyPay-easy Payment
banktransferGeneral wire transfer (bank-to-bank wire transfer) payment
cyberedyRakuten Edy Payment (Rakuten Edy)
mobileedyRakuten Edy Payment (Rakuten Edy)
suicaMobile Suica Payment
webmoneyWebMoney Payment
netcashNET CASH Payment
bitcashBitCash Payment
prepaidJCB PREMO Payment
docomod Payment (Carrier/Wallet)
auoneau Kantan Kessai Service
yahoowallet2Wallet payment service (Type-Y)
yahoowalletdgYahoo! Wallet (Digital Content)
RakutenRakuten Pay (Online Payment)
Rakutenv2Rakuten Pay (Online Payment)V2
recruitRecruit Kantan Shiharai
softbank2SoftBank Matomete Shiharai (B)
AlipayAlipay+
PaypalPayPal Payment
netmileNetMile payment
mysoftbankSoftBank Matomete Shiharai (A)
LinePayLINE Pay
merpayMerpay Online Payment
tpointT-Point Program (Online Payment)
applepayApple Pay
nppostpayNP Atobarai
aupayau PAY (Online Payment)
eposeasypayEPOS Kantan Kessai Service
wechatpayWeChatPay

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 "EMV 3-D Secure Authentication System".
TDS2INFO_TOKEN_KEYToken key of payment information of credit card user X 

<<Setting Examples>>

(1) The setting value and its corresponding value are connected with a connecting character (half-width equal sign) and concatenated with a delimiter (half-width comma).

   TDS2INFO_TOKEN=123456789abc,TDS2INFO_TOKEN_KEY=asdefg123

(2) Perform Triple DES and convert using base64 method.

1BNK6NDjiRdhEN0p5rajgyp2tjEC5EEnpvbBGYO+F6fckdWWXllvDYGQ1Jq...

(3) Set it to the free_csv of the Link Type POST item 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

Link Type PayPay (Online Payment) allows you to set an expiration date for Authorization only for Suggested Sellers.

The expiration date should be shorter than the deadline that merchant applied for to Financial institution.

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 namePAYPAY_EXPIRED_DATETIMEExpiration date of authorization209Specify as an Epoctime
ORDER_DESCRIPTIONDescription of transaction255M 
TRANSITION_TYPETransition type 1: Transition from app (WebLink)/2: Transition from app (DeepLink)19Specify "1" as the setting value when the WebView setting of the Merchant app is WebLink (Universal Links/App Links).
(Recommended) Specify "2" as the setting value when the WebView setting of the Merchant app is DeepLink (Custom URL Scheme).
* Read the cautions below the table as well.

Notes: About TRANSITION_TYPE

For more information on this item, please refer to "Linking the merchant App and the PayPay App".

This field is provided for the purpose of preventing the user from launching an external browser during PayPay (Online Payment). To use the field, pay attention to the following:

When " 2: Transition from app (DeepLink)" is set to the field, the payment cannot be finished unless the PayPay app is installed in the user's smartphone.

If the setting value is "1: Transition from the app (WebLink)", payment can be completed via the web even if the PayPay app is not installed on the user's smartphone, so the setting value "1: Transition from the app (WebLink)" is recommended.

Use only when there is a problem that cannot be solved when "1: Transition from app (WebLink)" is set to the field.

In addition, when using this function on Android, it is necessary to set the Activity setting of the merchant app to launchMode to singleTask or singleInstance. Normally, Standard is set, so please be sure to set this setting when implementing the merchant side application.

<<Setting Examples>>

(1) The setting value and its corresponding value are connected with a connecting character (half-width equal sign) and concatenated with a delimiter (half-width comma).

PAYPAY_EXPIRED_DATETIME=1582862260,ORDER_DESCRIPTION=xxxxx

(2) Perform Triple DES and convert using base64 method.

1BNK6NDjiRdhEN0p5rajgyp2tjEC5EEnpvbBGYO+F6fckdWWXllvDYGQ1Jq...

(3) Set it to the free_csv of the Link Type POST item 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

For the Link Type LINE Pay, screen link can be achieved for item image URLs displayed on the LINE Pay screen as FreeCSV fields. In addition, depending on the link field, the channel web login screen can be omitted and the character language in the LINE Pay in-process screen can be specified.

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 ValueDescriptionCharsFormatRemarksExample
Field namePRODUCT_IMAGE_URLItem image URL500MURL of the item image to be displayed on the LINE Pay app screen*1https://stbfep.sps- system.com/material/spsdummy/i mg/button/bt_linepay.jpg
LINE_MEMBER_IDLINE member ID50Mmid of LINE member who makes a payment*2LINEmid1234
DELIVERY_PLACE_PHONEContact of the recipient100MReferenced in Risk Management inside LINEPay0368892130
LANG_CDLanguage code for the payment wait screen7XLanguage code for the payment wait screen*3en
CHECK_CONFIRM_URL_BROWS ERWhether a browser check is performed at the transition destination URL after payment approval5XWhether the browser check is performed when the screen has moved to the confirmUrl*4 true: Perform the check / false: Do not perform the checkfalse
Connection character=Single-byte equal
Field valueAccording to each fieldNo validation for each field value
Delimiter,Single-byte comma

*1: If an item image URL is not set, the item image is not displayed on the app.

*2: If a LINE member ID is used for screen linkage, the channel web login screen for screen transition is omitted.

*3: The language code for payment wait screen supports the following six types of language.

  • ja: Japanese
  • ko: Korean
  • en: English
  • zh -Hans: Chinese (simplified Chinese character)
  • zh -Hant: Chinese (traditional Chinese character)
  • th: Thai

*4: If the field is not set, false is set as the default value.

<<Setting Examples>>

(1) Create a Concatenation characters according to the setting method.

PRODUCT_IMAGE_URL=https://stbfep.spssystem.com/material/spsdummy/img/button/bt_linepay.jpg,LANG_CD=ko

(2) Encode the created Concatenation characters in base64 format.

   UFJPRFVDVF9JTUFHRV9VUkw9aHR0cHM6Ly9zdGJmZXAuc3BzLXN5c3RlbS5jb20vbWF0ZXJpYWwvc3BzZHVtbXkvaW1nL2J1dHRvbi9idF9saW5lcGF5LmpwZyxMQU5HX0NEPWtv

(3) Set it to the free_csv of the Link Type POST item and send.

* When using the API Type service together, 3DES encryption following (1) and then the encoding in (2) are required. For details, refer to the API Type System Specifications (Basic Specifications).

<<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

Screen Image

The following are images of screens generated when the above example data is sent:

<<PC Browser Screen (LINE Pay In-process Screen)>>

<<LINE Pay App Screen>>

When you use offline payment (convenience store payment, Pay-easy payment, general wire transfer (bank-to-bank wire transfer) payment) in the Link Type, the following are possible by using "free_csv."

  • To display information required for payment, such as the telephone number and email address, on the screen as the default values
  • To specify the payment due date for each transaction

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 ValueDescriptionCharsFormatRequired input field by payment method *1Remarks
Convenience store paymentPay-easy PaymentGeneral wire transfer (bank-to-bank wire transfer) payment
Field nameLAST_NAMELast name20MDouble-byte
FIRST_NAMEFirst name20MDouble-byte
LAST_NAME_KANALast name (kana)20MDouble-byte kana
FIRST_NAME_KANAFirst name (kana)20MDouble-byte kana
FIRST_ZIPZip code (3 digits)3
SECOND_ZIPZip code (4 digits)4
ADD1Prefecture50M
ADD2Street, City50M
ADD3Building name, etc.100※4M
TELTelephone number (without a hyphen)11
MAILEmail address128XSingle-byte alphabet and numbers*3
BILL_DATE*5Payment Due Date (YYYYMMDD)8Single-byte numbers
BILL_DATE_TIME*Payment Due Date and Time (YYYYMMDDHHMI)12Single-byte numbers
Connection character=Single-byte equal
Field valueAccording to each fieldNo validation for each field value
Delimiter,Single-byte comma

*1: The field is not mandatory for system cooperation, but it is a mandatory field in the Payment Information Input screen following cooperation.
*2: See "Characters Available for Fields Specified to Use Double-byte Kana Characters in free_csv Fields" in this section.
*3: See “Characters Available for Fields Specified for E-mail Address” in this section.
*4: If payment methods is General wire transfer, it will be 200 bytes. When using Delimiter in the printing Restriction described below, each item must be 100 bytes or less, and the total value including Delimiter must be 200 bytes or less.
*5: BILL_DATE and BILL_DATE_TIME are only applicable to specific payment methods and billers. If specified for non-applicable payment methods, they will be disregarded. Please check the service overview of each payment methods for availability.

<<Setting Examples>>

(1) The setting value and its corresponding value are connected with a connecting character (half-width equal sign) and concatenated with a delimiter (half-width comma).

LAST_NAME=Suzuki,FIRST_NAME=Taro,MAIL=test@ps.softbank.co.jp,・・・

(2) Convert using the base64 method.

TEFTVF9OQU1FPZfpltgsRklSU1RfTkFNRT2RvphZLE1BSUw9dGVzdEBwc...

(3) Set it to the free_csv of the Link Type POST item and send.

* When using the API Type service together, 3DES encryption following (1) and then the encoding in (2) are required. For details, refer to the API Type System Specifications (Basic Specifications).

<<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 the free_csv field>

The following characters cannot be used in any field.

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

<Characters that can be used in the full-width kana specification field in the free_csv field>

The following characters are available for use in the Last Name (Kana) and Given Name (Kana) fields.

CharacterS-JIS Code
A I I U E O K A K G I K G K E K O S A S I S U S E S O T A D A C I T D I T E T D O N A N I N N E N H A B A P I B I P I H B P E H O B O P O M A M I M M I N Y A Y U Y O R A R I L E R O W A I E W O N V K A K8340-8396, 815B

《Characters that can be used in the E-mail address specification field in the free_csv field》

The following characters are available for use in email address fields:

CharacterNameS-JIS Code
ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyzSingle-byte alphabet0x41~0x5A 0x61~0x7A
0123456789Single-byte numbers0x30–0x39
@Single-byte at sign0x40
.Single-byte period0x2E
_Single-byte underscore0x5F
Single-byte hyphen0x2D

Screen Image

<<Screen Images in System Cooperation>>

The payment screen image for the convenience store payment is shown as follows.

<<Restrictions in Paper Bills>>

In the case of Paper bill reception, ADD2 and ADD3 are connected to one line, but by using Delimiter for ADD3, it is possible to separate the company name and department name and print it with a line break.

Example: Address: 25F Shiodome Sumitomo Building, 1-9-2 Higashi-Shinbashi, Minato-ku, Tokyo

Company Name: SB Payment Service Corp.

Department Name: Service Department, Service Headquarters

If you wish to print as stated above, set up free_csv as follows.

  • ADD1=Tokyo
  • ADD2=1-9-2 Higashi-shimbashi, Minato-ku
  • ADD3 = Shiodome Sumitomo Building 25F □□□ SB Payment Service Corp. □□□ Service Division Service Department

※□=Full-width space

* ADD3 is limited to 200 bytes, but if you use Delimiter to divide it into building name, company name, and department name, it will be 100 bytes for the building name, 60 bytes for the company name, and 100 bytes for the department name.

* In the case of Paper bill, half-width characters cannot be used in ADD1, ADD2, and ADD3.

*To display the "Company name" and "Department name" input fields separately in above Input screen, you need to make a request to the screen customizing service separately. If you do not make such a request, they will be displayed as they are in "Building name, etc." input field.

When you use Recruit Kantan Shiharai in the Link Type, the following are possible by using "free_csv."

  • To specify the payment due date for each transaction

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 nameBILL_DATE*Payment Due Date (YYYYMMDD)8Single-byte numbers
BILL_DATE_TIME*Payment Due Date and Time (YYYYMMDDHHMI)12Single-byte numbers

*5: For BILL_DATE and BILL_DATE_TIME, payment methods and receiving agents that can be specified are limited, and a non-applicable payment method will not be used even if it is specified. For payment methods that can be specified or not, confirm with the service specifications for each payment method.

This function is used for Recruit Kantan Shiharai only when the end user payment method includes convenience store payment.

<<Setting Examples>>

(1) The setting value and its corresponding value are connected with a connecting character (half-width equal sign) and concatenated with a delimiter (half-width comma).

BILL_DATE =20170201

(2) Convert using the base64 method.

TEFTVF9OQU1FPZfpltgsRklSU1RfTkFNRT2RvphZLE1BSUw9dGVzdEBwc...

(3) Set it to the free_csv of the Link Type POST item 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.

In the Link Type NP Deferred Payment, the order date and customer information need to be shared as FreeCSV items.

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 nameNP_ORDER_DATEMerchant order date89YYYYMMDD
NP_COMPANY_NAMEPurchaser company name60MUse double-byte characters only.
NP_DEPARTMENTPurchaser department name60MUse double-byte characters only.
NP_CUSTOMER_NAMEPurchaser name42MUse double-byte characters only.
NP_CUSTOMER_NAME_KANAPurchaser name (kana)50MUse double-byte kana characters only.
NP_ZIPPurchaser postal code79 
NP_ADDRESSPurchaser address110MUse double-byte characters only.
NP_TELPurchaser phone number119 
NP_EMAILPurchaser email address100X 
NP_DEST_COMPANY_NAMEDelivery destination company name60MUse double-byte characters only.
NP_DEST_DEPARTMENTDelivery destination department name60MUse double-byte characters only.
NP_DEST_CUSTOMER_NAMEDelivery destination person's name42MUse double-byte characters only. Mandatory only when any of the delivery destination postal code, delivery destination address, and delivery destination phone number is specified.
NP_DEST_CUSTOMER_NAME_KA NADelivery destination person's name (kana)50MUse double-byte kana characters only.
NP_DEST_ZIPDelivery destination postal code79Mandatory only when any of the delivery destination person's name, delivery destination address, and delivery destination phone number is specified.
NP_DEST_ADDRESSDelivery destination address110MUse double-byte characters only. Mandatory only when any of the delivery destination person's name, delivery destination postal code, and delivery destination phone number is specified.
NP_DEST_TELDelivery destination phone number119Mandatory only when any of the delivery destination person's name, delivery destination postal code, and delivery destination address is specified.

<<Setting Examples>>

(1) The setting value and its corresponding value are connected with a connecting character (half-width equal sign) and concatenated with a delimiter (half-width comma).

NP_ORDER_DATE=20180901,NP_COMPANY_NAME=company name・・・

(2) Convert using the base64 method.

1BNK6NDjiRdhEN0p5rajgyp2tjEC5EEnpvbBGYO+F6fckdWWXllvDYGQ1Jq...

(3) Set it to the free_csv of the Link Type POST item 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
  • The following fields are mandatory:
    Buyer's name, postal code, address, phone number, email address

    In addition, if any of the following items are entered, all items must be set.
    Delivery name, delivery postal code, delivery address, delivery phone number

  • 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

Apple Pay on the Web is used for our Link Type Apple Pay payment. For information on system requirements and restrictions, refer here.

Was this page helpful?