Difference between revisions of "CreditLine Import/Export"
(→<font color=#ff0000>UNDER CONSTRUCTION</font>) |
(→Usage) |
||
(30 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{CreditLine Header|Manual}} | {{CreditLine Header|Manual}} | ||
− | == | + | == Import == |
+ | ===Usage=== | ||
+ | '''Import Feature''' will import from a text file (see format below) into the current journal. | ||
+ | The Import Feature is useful for processing massive recurrent charges, for instance Club Membership. This tool is also used in [[Expired Transactions Re-Run]]. | ||
+ | |||
+ | Note: PCI requires the file to be encrypted prior to usage. Remember, to destroy or secure the plain text file after the encryption. | ||
<br> | <br> | ||
− | + | Step 1)<br> | |
+ | [[Image:encryptImport.png|none|framed|Select '''Tools->Encrypt Import File''' from '''[[CreditLine Manager]]''' | ||
+ | ]] | ||
+ | <br> | ||
+ | Step 2)<br> | ||
+ | From the menu select Tools->Import and select the newly encrypted file. | ||
− | |||
− | |||
+ | [[Image:Import.gif|none|framed|Click '''Ok '''to proceed]] | ||
+ | ===Directly To Journal Function=== | ||
+ | ''This is an advanced function!'' Selecting '''Directly To Journal ''' will bypass the processor and import the transactions without obtaining new [[Credit_Card_Glossary#Auth_Code|Auth Codes]]. It is recommended that you leave this check box unchecked. | ||
− | == | + | ===Testing Functions=== |
+ | '''Repeat, Interval '''(in seconds) and '''Random Interval '''fields are for stress testing. This can be used if you need to stress test your software or integration with multiple transaction over and over again. | ||
− | + | ===Output Destination=== | |
− | + | ;Approved Output: is the file where the approved transaction results are directed | |
− | + | ;Declined Output: is the file where the declined transaction results are directed | |
− | + | → The '''Approved Output ''' and '''Declined Output '''files have to be different so as not to override each other! | |
− | |||
− | + | === Import Format === | |
− | + | ====File Format==== | |
− | + | *A single transaction is represented by a line. | |
+ | *Every line in the file consists of fields in quotes separated by ','. | ||
+ | *End of line is '''0x13, 0x10''' (standard new line) | ||
− | |||
− | + | "field1", "field2", "field3", "field4","field5","field6","field7","field8"<new line> | |
− | + | {| border="1" cellpadding="5" | |
+ | ! style="background:#efefef;" | Field | ||
+ | ! style="background:#efefef;" | Description | ||
+ | ! style="background:#efefef;" | Notes | ||
+ | |- | ||
+ | |field1 || [[#Transaction Types|Transaction Type]] || e.g. C1 is sale. See [[#Transaction Types|Transaction Type]] for more types. | ||
+ | |- | ||
+ | |field2 || Clerk || Operator Code | ||
+ | |- | ||
+ | |field3 || Member Number || | ||
+ | |- | ||
+ | |field4 || Credit Card Number || | ||
+ | |- | ||
+ | |field5 || Credit Card Exp Date || MMYY format (e.g. 1207) | ||
+ | |- | ||
+ | |field6 || Amount|| #####0.00 where # is space as needed for total of 9 characters. e.g. " 1.00" | ||
+ | |- | ||
+ | |field7 || Member Zip Code || | ||
+ | |- | ||
+ | |field8 || Member Address Line 1|| | ||
+ | |} | ||
− | + | ===Verification=== | |
+ | After the import, check the [[CreditLine_View_Log_Dialog|log]], [[CreditLine ViewModify Dialog]], as well as the approve and decline files to ensure that all the imported transactions have been successfully run. | ||
− | + | == Export == | |
+ | '''This function was deprecated due to PCI requirements''' | ||
− | === | + | ===Security Warning=== |
+ | →<font color=#ff0000>'''Warning:'''</font> this feature must not be used by anyone except administrators. Full account info is exported for administration purposes. Unless using version 3.03.11+, remove the log as well as the export files from the system after usage to avoid exposing sensitive credit card information. | ||
− | + | ''Disable the access to this feature by anyone except administrators in [[CreditLine Security Setup]].'' | |
− | + | ===Usage=== | |
− | + | [[Image:ToolsExport.gif|none|framed|Select '''Tools->Export '''from '''CreditLine Manager''']] | |
− | |||
− | + | Export will export from a journal to a text file (see format below). | |
− | + | [[Image:Export.gif|none|framed|Click '''Ok '''to proceed]] | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=== Command Line Export === | === Command Line Export === | ||
− | Please see | + | Please see [[CreditLine Command Line]]. |
=== Export Format === | === Export Format === | ||
Line 74: | Line 98: | ||
Export can be used for third part interoperation or server synchronization. | Export can be used for third part interoperation or server synchronization. | ||
− | ''ICVerify Note: Update Member Accounts will read the upload file created by | + | → ''ICVerify Note: Update Member Accounts will read the upload file created by ICVERIFY. (Export Transactions )'' |
− | File Format | + | ====File Format==== |
− | A single transaction is represented by a line. | + | *A single transaction is represented by a line. |
− | + | *Every line in the file consists of fields in quotes separated by ','. | |
− | Every line in the file consists of fields in quotes separated by ','. | + | *End of line is '''0x13, 0x10''' (standard new line) |
− | + | ||
− | End of line is 0x13, 0x10 (standard new line) | + | |
"field1", "field2", "field3", "field4","field5","field6","field7","field8","field9"<new line> | "field1", "field2", "field3", "field4","field5","field6","field7","field8","field9"<new line> | ||
− | + | {| border="1" cellpadding="5" | |
− | + | ! style="background:#efefef;" | Field | |
− | + | ! style="background:#efefef;" | Description | |
− | + | ! style="background:#efefef;" | Notes | |
− | {| | + | |
− | + | ||
− | + | ||
|- | |- | ||
− | | | + | |field1 || [[#Transaction Types|Transaction Type]] || e.g. C1 is sale. See [[#Transaction Types|Transaction Type]] for more types. |
− | | | + | |
|- | |- | ||
− | | | + | |field2 || Clerk || Operator Code |
− | | | + | |
|- | |- | ||
− | | | + | |field3 || Member Number || |
− | | | + | |
|- | |- | ||
− | | | + | |field4 || Credit Card Number || |
− | | | + | |
|- | |- | ||
− | | | + | |field5 || Credit Card Exp Date || MMYY format (e.g. 1207) |
− | + | |- | |
+ | |field6 || Amount|| #####0.00 where # is space as needed for total of 9 characters. e.g. " 1.00" | ||
+ | |- | ||
+ | |field7 || Member Zip Code || | ||
+ | |- | ||
+ | |field8 || Member Address Line 1|| | ||
+ | |- | ||
+ | |field9 || Response Code || '''Y12345612345678Y''' at the beginning of this field indicates that the transaction was approved. '''N''' at the beginning of this field indicated that the transaction was declined. | ||
+ | |||
|} | |} | ||
− | + | ==Transaction Types== | |
+ | {{Text Based Transaction Type}} | ||
+ | |||
+ | ==See Also == | ||
+ | * For more info please see [http://911software.com/files/icvsdk1.pdf ICVerify SDK Format Spec] | ||
+ | * [[Expired Transactions Re-Run]] | ||
+ | |||
[[Category:CreditLine Manual|Import/Export Guide]] | [[Category:CreditLine Manual|Import/Export Guide]] |
Latest revision as of 20:04, 12 February 2015
This article is part of the Payment Processing Software Library |
|
Get it... | |
Install it... | |
Connect to it... | |
Set it up... | |
Learn to use it... | |
→ Manual & User Guide | |
Fix it... | |
→ Errors & Troubleshooting | |
Get Help... | |
More Info ... | |
See also... | |
CreditLine Payment Processing Software Manual. This site can also be reached at http://docs.911software.com
→ Looking for better rates? Get a Free Credit Card Processing Cost Comparison!
Contents
Import
Usage
Import Feature will import from a text file (see format below) into the current journal. The Import Feature is useful for processing massive recurrent charges, for instance Club Membership. This tool is also used in Expired Transactions Re-Run.
Note: PCI requires the file to be encrypted prior to usage. Remember, to destroy or secure the plain text file after the encryption.
Step 1)
Step 2)
From the menu select Tools->Import and select the newly encrypted file.
Directly To Journal Function
This is an advanced function! Selecting Directly To Journal will bypass the processor and import the transactions without obtaining new Auth Codes. It is recommended that you leave this check box unchecked.
Testing Functions
Repeat, Interval (in seconds) and Random Interval fields are for stress testing. This can be used if you need to stress test your software or integration with multiple transaction over and over again.
Output Destination
- Approved Output
- is the file where the approved transaction results are directed
- Declined Output
- is the file where the declined transaction results are directed
→ The Approved Output and Declined Output files have to be different so as not to override each other!
Import Format
File Format
- A single transaction is represented by a line.
- Every line in the file consists of fields in quotes separated by ','.
- End of line is 0x13, 0x10 (standard new line)
"field1", "field2", "field3", "field4","field5","field6","field7","field8"<new line>
Field | Description | Notes |
---|---|---|
field1 | Transaction Type | e.g. C1 is sale. See Transaction Type for more types. |
field2 | Clerk | Operator Code |
field3 | Member Number | |
field4 | Credit Card Number | |
field5 | Credit Card Exp Date | MMYY format (e.g. 1207) |
field6 | Amount | #####0.00 where # is space as needed for total of 9 characters. e.g. " 1.00" |
field7 | Member Zip Code | |
field8 | Member Address Line 1 |
Verification
After the import, check the log, CreditLine ViewModify Dialog, as well as the approve and decline files to ensure that all the imported transactions have been successfully run.
Export
This function was deprecated due to PCI requirements
Security Warning
→Warning: this feature must not be used by anyone except administrators. Full account info is exported for administration purposes. Unless using version 3.03.11+, remove the log as well as the export files from the system after usage to avoid exposing sensitive credit card information.
Disable the access to this feature by anyone except administrators in CreditLine Security Setup.
Usage
Export will export from a journal to a text file (see format below).
Command Line Export
Please see CreditLine Command Line.
Export Format
Export can be used for third part interoperation or server synchronization.
→ ICVerify Note: Update Member Accounts will read the upload file created by ICVERIFY. (Export Transactions )
File Format
- A single transaction is represented by a line.
- Every line in the file consists of fields in quotes separated by ','.
- End of line is 0x13, 0x10 (standard new line)
"field1", "field2", "field3", "field4","field5","field6","field7","field8","field9"<new line>
Field | Description | Notes |
---|---|---|
field1 | Transaction Type | e.g. C1 is sale. See Transaction Type for more types. |
field2 | Clerk | Operator Code |
field3 | Member Number | |
field4 | Credit Card Number | |
field5 | Credit Card Exp Date | MMYY format (e.g. 1207) |
field6 | Amount | #####0.00 where # is space as needed for total of 9 characters. e.g. " 1.00" |
field7 | Member Zip Code | |
field8 | Member Address Line 1 | |
field9 | Response Code | Y12345612345678Y at the beginning of this field indicates that the transaction was approved. N at the beginning of this field indicated that the transaction was declined. |
Transaction Types
Credit Card
Type | Code |
---|---|
Auth | CA |
Book, Checkin | C4 |
Auth Only | C6 |
Sale | C1 |
Force, Voice Auth | C5 |
Credit | C3 |
Void Sale | C2 |
Void Credit | CR |
Add Tip, Edit, Finalize | CT |
Post, Ship, Checkout | CO |
Extend Stay | CI |
No Show | CN |
Add Charge | CG |
Settle | ST |
Settle and Print Batch Report | SP |
Gift Card
Type | Code |
---|---|
Inquiry | GI |
Activation | GA |
Deactivation | GD |
Adjust | GJ |
Verification
If using the format for the export function: after the export check the export file to ensure that all the transactions have been successfully processed.
See Also
- For more info please see ICVerify SDK Format Spec
- Expired Transactions Re-Run