TxRefNum
advertisement
Orbital Gateway Scripts ** Any sections or transactions within sections that are not supported should be noted as not applicable (n/a) ** If you do not support any of the requested elements such as AVS, CVD or purchase Level 2, run the transaction without those elements. Please note: Both AVS and CVD are highly recommended. If your business typically processes purchase cards you may want to consider adding the purchase card level 2 data. Please see the credit card 101 document for more information about AVS, CVD and purchase card if needed. This document can be found on the download page at www.paymentech.net/download. ** Please email the completed script to your certification analyst. Use Test cards numbers provided in the test document. Section A – Auth only Transactions- Message Type “A”: The following transactions should be run as auth only with the information requested below. Add customer defined data if you’d like to certify for this functionality. The Response codes received should be recorded in the appropriate columns. # Card AVS Zip 1 2 3 4 5 6 7 8 9 Visa Visa MC MC Amex Amex DS DS JCB 11111 33333 44444 88888 55555 66666 77777 88888 33333 CVD 222 333 666 1111 5555 666 Amount Purchase card Ordernum 30.00 38.01 41.00 11.02 1055.00 75.00 10.00 63.03 29.00 Purchase card dest. zip Auth/ Resp Code AVS Resp CVD Resp TxRefNum Section B – Auth Capture Transactions- Message Type “AC”: The following transactions should be run as auth/capture only with the information requested below. Please add purchase card level 2 and customer-defined data if you’d like to certify for either functionality. The Responses received should be recorded in the appropriate columns. # Card AVS Zip 1 2 3 Visa Visa MC 11111 33333 44444 CVD 222 333 Amount Auth/ Resp Code 30.00 38.01 41.00 AVS Resp CVD Resp TxRefNum 1 4 5 6 7 8 9 MC Amex Amex DS DS JCB 88888 55555 66666 77777 88888 33333 666 4444 5555 666 11.02 1055.00 75.00 10.00 63.03 29.00 Section C – Mark For Capture: The following transactions will mark the previous auth only transactions for capture. The number corresponds to the number of the authorization previously completed in Section A. If you will be capturing the full amount use the amount listed under the “Amount” column. If you will be splitting shipments, the please follow the amount given under the “split shipment amount” column. This is the amount you will capture. # Card Amount A-1 A-3 A-5 A-7 A-9 Visa MC Amex DS JCB 30.00 41.00 1055.00 10.00 29.00 Split Shipment amount 10.00 20.00 500.00 10.00 29.00 Auth/Resp Code TxRefNum Section D – Return Transactions: The following transactions should be completed as returns, with all standard transaction data. # Card Amount 1 2 Visa MC 12.00 11.00 3 4 5 Amex DS JCB 1055.00 10.00 29.00 Auth/Resp Code TxRefNum Section E – Force: The following transactions should be completed as prior sales, with all standard transaction data, and additional information as requested. Use approval codes as listed in the table below. 2 # Card Amount 1 2 3 4 5 Visa MC Amex DS JCB 12.00 11.00 1055.00 10.00 29.00 Auth Code 654544 158945 198543 098756 098757 TxRefNum Section F – Voids: The following transactions are void of previously completed transactions. If you will only processing full voids then follow the amount given in the “Amount” column. If you will be splitting shipments please follow the amounts listed in the split shipment amount column as you did in section C, this is to void the leftover amount. # Amount A-1 A-5 B-9 30.00 1055.00 29.00 Split ship amount to be voided 20.00 500.00 29.00 TxRefNum Section G – Stored Value Transactions: The following transactions should be run as indicated, with all standard transaction data, and additional information as requested. The response code received should be recorded in the appropriate column. # Card Tran Description 1 2 3 4 5 6 7 8 9 10 11 12 Stored Value Stored Value Stored Value Stored Value Stored Value Stored Value Stored Value Stored Value Stored Value Stored Value Stored Value Stored Value Issuance/Add Value Issuance/Add Value Activation Activation Block Activation of 5 cards ($30 EACH) Redemption Redemption Redemption Void # 2 Balance Inquiry Void # 8 Issuance/Add Value CVD Value Amount Response/Auth TxRefNum Code 16.00 30.00 25.00 50.00 150.00 98.00 40.00 56.00 30.00 56.00 16.00 3 13 14 15 16 17 18 Stored Value Stored Value Stored Value Stored Value Stored Value Stored Value 19 Stored Value Deactivation Deactivation Reactivation Reactivation Block Activation of 10 cards ($25 each) Block Activation of 150 cards ($10 each) Block Activation of 200 cards ($10 each) 0.00 0.00 35.00 25.00 250.00 1500.00 2000.00 Section H –Prior Stored Value Transactions: Your certification analysts will give you auth codes for the prior transactions via phone or email. Provide us the card numbers that you want to use and we will then give you the auth code to use during certification. # Card Tran Description 20 21 22 23 24 25 26 27 Stored Value Stored Value Stored Value Stored Value Stored Value Stored Value Stored Value Stored Value Prior Issuance/Add Value Prior Issuance/Add Value Prior Issuance/Add Value Prior Activation Prior Activation Prior Redemption Prior Redemption Prior Redemption Amount Card# 29.00 3.00 31.00 56.00 50.00 56.00 42.00 49.00 Card Card Card Card Card Card Card Card Response/Auth Code Card Card Card Card Card Card Card Card TxRefNum Card Card Card Card Card Card Card Card Section I – Interface Version- This MIME-Header field is used by the Client to identify information about their implementation to assist Paymentech in providing production support. This information will be logged distinctly for research purposes. For example, if our SDK’s are used, they pass the SDK type and Version Number in this field. Another example would be any Third Party Software Provider should log their Software name and version number in this field, such that Paymentech knows how the interface is being managed. A Merchant could place information about their development version and implementation language. Please work with your Certification Analyst to best identify what values should be used in this field. This field will be checked on the transactions sent. Give us the information below so that we can verify what you are populating in this field. Skip the fields that do not apply. Which DTD your using. Software name Software Version Programming Language used Section J – End of Day Settlement: Please tell us how you plan on settling your transactions at the end of the day 4 Manually through the Virtual Terminal ___________ Auto settle _________ What time of the day would you like your auto settle set up for? ____________ What time zone are you in? End of Day XML message__________ 5 Section K – Retry Logic: When processing transactions over the internet, there is a risk that a response to a request will not be received. To address this problem and avoid duplicate authorizations, we offer additional functionality, Retry Logic. Retry logic is HIGHLY recommended. For more information please consult the Orbital Gateway Specifications and the retry specification on the download page. Please follow the scripts below to certify for retry logic. First Set – Transactions sent for the first time. # Card 1 2 3 4 5 Visa MC Visa Amex DS OrderID Trace number TxRefNum Auth code Response TxRefNum Auth code Response Auth code Response Second Set- Retry using the same OrderID and Trace Number. # Card 1 2 3 4 5 Visa MC Visa Amex DS OrderID Trace number Third Set- One transaction that was resent but using a different trace number. # Card 1 Visa OrderID Trace number TxRefNum 6 Section L- Customer Profiles: Customer Profiles provides the ability for you store information about your customer on the Orbital Gateway. This simplifies transaction processing and eliminates the risk associated with the merchant storing sensitive information. Please see the specifications to learn more about Customer profiles. To certify for customer profiles, complete the scripts below. Add- Perform an add profile transaction using information below. # Card Details 1 Func -tion Add 2 Add MC Visa Customer Profile Number TxRefNum Populate- Name, Address, City, State, Zip code and email. Populate- Name and zip code Update the customer profiles you created above. Use the corresponding numbers to update. # 1 2 Function Update Update Card Details Customer Profile Number Amex MC Change card to American Express Add address and phone to profile TxRefNum Retrieve- Retrieve the first customer profile created. # 1 FuncCard tion Retrieve Visa Customer Profile Number TxRefNum Authorize using the customer profile from the corresponding number. # 1 2 Function Auth Auth Card Amount Details Amex MC 25.00 30.00 Override address and zip with new. Customer Profile Number TxRefNum 7 Auth Capture- perform an auth capture utilizing the previously created profile. # 1 2 Function AC AC Card Amount Details Amex MC 45.00 50.00 Override zip code Customer Profile Number TxRefNum Refund- Perform a refund transaction utilizing the previously created profile. # 1 2 Func -tion Auth Auth Card Amount Amex MC 10.00 15.00 Customer Profile Number TxRefNum Add Profile during authorization – Create a new profile during an authorization. # 1 2 Function Auth/add profile Auth/add profile Card Amex MC Amount Details 65.00 Populate address, zip and phone number. 70.00 Populate zip and phone number. Customer Profile Number TxRefNum Customer Profile Number TxRefNum Add Profile during auth/capture– Create a new profile during an auth capture. # 1 2 Function AC/add profile AC/add profile Card Amex MC Amount Details 30.00 Populate address, zip and phone number. 50.00 Populate address and zip. 8 Delete Profile - Delete the Profiles created in the auth or auth capture above. # 1 2 Function Delete Profile Delete Profile Card Amex Customer Profile Number TxRefNum MC Error Processing- Please follow the instructions for the two transactions below. This is to ensure that you can handle error messages. # 1 2 Function Auth/capture or auth only Add profile Card Visa MC Details Use customer profile – 45461SAAX Add profile but do not include customer name. Response TxRefNum 9
