Authorization (Offline)

👍
Connect using SFTP

IP Address : 52.76.184.174

Port : 22

Username : The merchant must fill in the SFTP setup form and send the request to support team. An account will be created for merchant to access 2c2p SFTP in demo and production environment.

Request Path : /input ( For File Pickup )

Response Path : /output ( For File Drop )

File Information Time
Reconciliation report file drop Before 4:00AM GMT+7
SimpleAuthorization file pickup 5:00AM GMT+7
SimpleAuthorization file drop Before 6:00AM GMT+7
OfflineAuthorization file pickup 2:00PM GMT+7
OfflineAuthorization file drop Before 6:00AM GMT+7 (next day)
Tokenization/Refund file pickup 2:00AM GMT+7
Tokenization/Refund file drop Before 3:00AM GMT+7
Quickpay/Promocode file pickup Every hour
Quickpay/Promocode file drop Within the next hour

File Information	Time
Reconciliation report file drop	Before 4:00AM GMT+7
SimpleAuthorization file pickup	5:00AM GMT+7
SimpleAuthorization file drop	Before 6:00AM GMT+7
OfflineAuthorization file pickup	2:00PM GMT+7
OfflineAuthorization file drop	Before 6:00AM GMT+7 (next day)
Tokenization/Refund file pickup	2:00AM GMT+7
Tokenization/Refund file drop	Before 3:00AM GMT+7
Quickpay/Promocode file pickup	Every hour
Quickpay/Promocode file drop	Within the next hour

🚧
File Format Specification

File name format : offlineauth_YYYYMMDD_fileName.csv

Parameter delimiter : semicolon ';'

Record delimiter : line break

Encryption Method : GPG . Download the PGP Public Keyhere.

How to integrate

Merchants must prepare the auth request file. Refer to Authorization Request.
Encrypt the auth request file using GPG.
Upload the encrypted auth request file to the SFTP Server.
2C2P will pick up the auth request file and process the payment.
2C2P will drop an encrypted auth response file in SFTP Server.
Merchants must get the encrypted auth response file from SFTP Server.
Decrypt the auth response file using GPG.
Read the response data as payment acknowledgement. Refer to Authorization Response.

📘
Data Attribute Reference
Data Type

A: Alphabet

AN: Alphanumeric

NT: NText

C: Characters

B: Boolean

D: Decimal

N: Numeric

Mandatory attributes

M: Mandatory

C: Conditional

O: Optional

Authorization Request

Header Parameters

H;1.0;0000001;2015-01-01 00:00:01;2015-01-01 00:00:02;2

Parameter	Data Type	Mandatory	Description
recordType	C 1	M	Header = H
version	N 5	M	Current version is 1.0
merchantID	C 15	M	Merchant ID provided by 2C2P
createDateTime	C 19	M	YYYY-MM-DD HH:mm:ss (24 hours format)
processDateTime	C 19	M	YYYY-MM-DD HH:mm:ss (24 hours format)
totalRecord	N 5	M	Total number of transactions

Detail Parameters

D;1;Invoice00001;1 night hotel in bali;300.00;840;4111111111111111;12;2020;;123;Joppie tjoa;[email protected];data1;data2;data3;data4;data5
D;2;Invoice00002;2 night hotel in bali;600.00;840;4111111111111111;12;2020;;123;Joppie tjoa;[email protected];;;;;

Parameter	Data Type	Mandatory	Description
recordType	C 1	M	Details = D
recordNo	N 5	M	running no 1 - 99999
uniqueTransactionCode	C 20	M	Transaction unique invoice number Provided by merchant
desc	C 50	M	Payment description The following symbols are not allowed: !@#$%^&_()<>;
amount	D 12,2	M	Transaction amount Example: 12.50
currencyCode	N 3	M	Standard ISO-4217 currency codes Refer to List of Currency Codes N3.
pan	N 16	M	Credit Card Number This is optional if stored card token is used
expiryMonth	N 2	M	Credit Card Expiry Month This is optional if stored card token is used
expiryYear	N 4	M	Credit Card Expiry Year This is optional if stored card token is used
storeCardUniqueID	C 20	O	Stored card token
securityCode	N 4	O	CVV2/CVC2/CID
cardholderName	C 50	M	Credit card holder name
cardholderEmail	C 50	O	Credit card holder email address
userDefined1	C 150	O	Merchant-defined information
userDefined2	C 150	O	Merchant-defined information
userDefined3	C 150	O	Merchant-defined information
userDefined4	C 150	O	Merchant-defined information
userDefined5	C 150	O	Merchant-defined information

Authorization Response

Header Parameters

H;1.0;0000001;2015-01-02 00:00:02;4

Parameter	Data Type	Mandatory	Description
recordType	C 1	M	Header = H
version	C 5	M	Current version is 1.0
merchantID	C 15	M	Merchant ID provided by 2C2P
completeDateTime	C 19	M	YYYY-MM-DD hh:mm:ss
totalRecords	N 5	M	Total number of transactions

Detail Parameters

D;1;Invoice00001;ABC123456;111222;0123456789;000000030000;840;411111XXXXXX1111;;user1;user2;user3;;;00;approved

Parameter	Data Type	Mandatory	Description
recordType	C 1	M	Details = D
recordNo	N 5	M	running no 1 - 99999
uniqueTransactionCode	C 20	M	Transaction unique invoice number Provided by merchant
tranRef	C 28	M	Routing trace reference number
approvalCode	C 6	M	Bank approval code
refNumber	C 15	M	Bank reference number
amt	D 12,2	M	Transaction amount Example: 12.50
currencyCode	N 3	M	Standard ISO-4217 currency codes Refer to List of Currency Codes N3.
pan	N 16	M	Masked card number
storeCardUniqueID	C 20	O	Stored card token
userDefined1	C 150	M	Merchant-defined information
userDefined2	C 150	M	Merchant-defined information
userDefined3	C 150	M	Merchant-defined information
userDefined4	C 150	M	Merchant-defined information
userDefined5	C 150	M	Merchant-defined information
respCode	C 2	M	Refer to Card Response Code.
respDesc	C 100	M	Refer to Card Response Code.