Master Field

This chapter describes the PCINS e-Payment Cancellation Message.

1. PeP1 Record
The contents of the PeP1 record vary depending on the transaction content.
For example, if there is no starting number of the card issuance date,
this field does not need to be included in the PeP1 record.
The record transmitted from the remote system to the PCINS host is described using HTML.
The layout of the confirmed record does not matter in order.
The fields can be anywhere in the HTML address body.
The response must use XML.

---

2. Master Field Format

No	Field Name	Field Description	Size(byte)	Type Attribute	Condition
1	“?”	Request Start	1	a	M
2	erst	Message Stage	3	a	O
3	ver	“100”	3	n	M
4	merchantId	Merchant ID	10	a	M
5	merchantPwd	Merchant Password	<16	a	M
6	mid	MerchantMID	10	a	M
7	ref	Transaction code	<60	a	M
8	tradeGubun	Transaction type	1	a	M
9	currType	Transaction currency	3	a	M
10	price	Transaction amount (half-width)	<12	n	M
11	shop	Merchant name	<255	a	O
12	payName	Buyer name (English)	<25	a	M
13	paynameJP	Buyer's name (Japanese)	<30	a	O
14	cardNo	Card number (half)	<16	n	M
15	expireM	Card expiration month (half)	2	n	M
16	expireY	Card expiration year (half)	2	n	M
17	csc	Card security code (half)	<4	n	O
18	cardType	Card type code	3	a	O
19	payId	Buyer's ID	<20	a	O
20	payEmail	Buyer e-mail	<50	a	O
21	payTel	Buyer phone number	<30	a	O
22	payAddr	Buyer address	<100	a	O
23	payPostal	Buyer zip code	<10	a	O
24	productName	Product name	<50	a	O
25	charset	Language code	<10	a	O
26	lang	Language	2	a	O
27	transCode	Transaction status code	2	a	M
28	transNo	Transaction number	<20	a	M
29	transTime	Transaction date and time	14	n	M
30	errCode	Error code	3	a	M
31	errMsg	Error message	<50	a	M
32	approvalNo	Approval code	<8	a	M
33	transMsg	Transaction message	<50	a	M
34	resultCode	Payment result code	3	a	M
35	resultMsg	Payment result message	<100	a	M
36	firstPrice	Continuous charging initial payment amount (halfway)	8	n	C
37	sincePrice	Continuous charging amount for 2nd or more times (halfway)	8	n	C
38	regularId	Continuous charging issuance ID	100	a	C
39	regularPwd	Continuous charging issuance password	100	a	C
40	returnURL	Screen transition URL	<1000	a	M
41	callbackURL	Payment result notification URL	<1000	a	M
42	referURL	Payment page URL	<1000	a	C
43	transStaus	Transaction inquiry status	1	n	O
44	tradeInfo	Payment additional information	<6000	a	C

---

3. Field Content

1. "?" (Request Start)
   "?" (Request Start) is the symbol that indicates the start of a PeP1 record.
   It is written after the PCINS URL.

---

2. erst (Message Stage)
   erst contains a value that indicates the message stage.

Value	Definition
logon	Logon Stage
aures	Confirmation stage
logoff	Logoff Stage

---

3. ver (Interface Version)
   PeP1 current version “100”

---

4. merchantId (Merchant ID)
   merchantId records the merchant login ID specified by PCINS to support validation and settlement using the PCINS Host Management Information service. Both upper and lower case letters can be used.

---

5. merchantPwd (Merchant Password)
   merchantPwd is the merchant password specified by PCINS.

---

6. mid (merchant MID)
   mid records the merchant ID assigned by the PCINS host to connect to the bank for transaction progress.

---

7. ref (transaction code)
   ref records one transaction number, and is proof that it is stored only in the host for the next transaction demand. Both uppercase and lowercase letters can be used. If there is no request, leave the field empty.

• Principle
  Developers should use HTML to encode correctly and be careful when sending data..

---

8. tradeGubun (transaction category)
   tradeGubun records the transaction category. The following values ​​are available.

Value	Definition
1	Sale (online approval)
2	Refund
7	Confirmation
9	Transaction inquiry
11	Register recurring billing
12	Cancel recurring billing

---

9. currType (transaction currency)
   currType records the currency code applied to the transaction amount.

Value	Definition
JPY	Japanese Yen
USD	US Dollar
EUR	Euro
KRW	Korean Won

---

10. price (transaction amount)
    price records the transaction amount.

• Principle
  JPY amounts do not allow decimal points. USD amounts allow up to two decimal points.

---

11. shop (merchant name)

---

12. payName (purchaser name (English))

---

13. paynameJP (purchaser name (Japanese)

---

14. cardNo (card number)
    cardNo records the card number. This number is used in the process of checking the transaction status.
    Speedy payment specifies the card number in the following cases.

Value	Definition
88888888888888	Search for credit card information in merchantId+phone number+payId.
88888888888881	Search for credit card information in merchantId+phone number.
88888888888882	Search for credit card information in merchantId+payId.

---

15. expireM (Card valid month)
    expireM records the card's expiration date (month).

• Principle
  The request format is MM.
  If 10 or less, always include 0 (01, 02, 03...)

---

16. expireY (Card valid year)
    expireY records the card's expiration date (year).

• Principle
  The request format is YY.
  If it is less than 10, it must contain 0 (01, 02, 03...)

---

17. csc (Card Security Code)
    csc displays the CSC (Card Security Code) and Address Verification System (AVS) used to verify the cardholder.

---

18. cardType (Card Type Code)
    cardType records the card type code. The following values ​​are available.

Value	Definition
AMX	American Express
JCB	Japanese Credit Bank
MSC	MasterCard
VIS	VISA

---

19. payId
    payId records the Hanazono ID managed by the Merchant store.

• Principle
  Only letters and numbers are allowed in the data format.

---

20. payEmail
    Email address of the buyer

---

21. payTel
    Phone number of the buyer

---

22. payAddr
    Address of the buyer

---

23. payPostal
    Postal code of the buyer

---

24. productName
    Product name

---

25. charset (language code)
    The default value of charset is UTF-8.

Value	Definition
UTF-8	Global
SHIFT-JIS	Japanese
EUC-KR	Korean

---

26. lang(Language)

Value	Definition
JP	Japanese
EN	English
CN	Chinese

---

27. transCode(Transaction Status Code)

Value	Definition
AS	Authorization Success
AF	Authorization Failed

---

28. transNo(Transaction Number)
    transNo records the unique transaction key and must be submitted to retrieve additional data for the transaction request.

---

29. transTime(Transaction Date and Time)
    transTime records the transaction time and task.

• Principle
  The request format is YYYYMMDDHHMMSS.

---

30. errCode (Error Code)
    errCode displays and records the transaction status in a code.

• Principle
  See Appendix Error Code..

---

31. errMsg (Error Message)
    errMsg records the reason for transaction failure.

• Principle
  See Appendix Error Code.

---

32. approvalNo (Approval Code)
    approvalNo records the international standard code provided by the approval authority for approved transactions.

---

33. transMsg (Transaction Message)

---

34. resultCode (Payment Result Code)
    result Code displays and records the payment result in a code.
    Used in non-UI.

• Principle
  See Appendix Error Code.

---

35. resultMsg (payment result message)
    Used in non-UI.

---

36. first Price (initial payment amount for recurring charges)

---

37. sincePrice (payment amount for recurring charges more than once)

---

38. regular Id (recurring charge issue ID)
    Regular Id is used when canceling.

---

39. regular Pwd (recurring charge issue password)
    Regular Pwd is used when canceling.

---

40. returnURL (screen switch URL)
    This is the URL that will redirect to the Merchant store screen after the UI payment is completed.

---

41. callbackURL (payment result notification URL)
    This is the URL that will notify the Merchant store screen of the payment information after the UI payment is completed.
    Screen security settings allow only IP connections from 61.74.60.18 and 61.74.60.19.
    The parameters are sent using the POST method.

---

42. referURL (Payment page URL)
    This is the URL of the payment page or homepage address where the UI payment is attempted.

---

43. transStaus (Transaction inquiry status)

Value	Definition
1	Sale
2	Refund

---

44. trade Info (Additional payment information)
    Information is applied differently depending on the value of qrServiceType,
    and values are entered and transmitted according to the data definition table for each payment line.
    Details are explained in the QR Payment (UI) chapter.

---