èßäÊÓƵapp

The merchant application must confirm to the following rules and specifications:

• The merchant pages are the responsibility of the merchant. ITS does not create or maintain these pages.
• The last page in the merchant application will only pass final information to the èßäÊÓƵapp ePayment system. The ePayment system will not "total up" or validate any data beyond some very core integrity constraints. This means that the merchant is fully responsible for establishing and finalizing all details of the transaction except collecting and verifying the credit card and eCheck information. Transaction details include but are not limited to: calculating shipping, verifying suitability of order, totaling and verifying the final shipping prices, calculating taxes.
• The merchant will not enclose the èßäÊÓƵapp ePayment system within in its own frames or attempt to interfere with the look and feel of the èßäÊÓƵapp ePayment system. Enclosing the ePayment system in frames prevents the user from seeing the SSL icon () in the browser’s border.
• The last merchant page must pass all required fields to the èßäÊÓƵapp ePayment System, and they must be passed using HTTP POST.
• The merchant application must manage all needed transaction information required for their business processes beyond what is contained in the required or optional fields. The merchant may handle this with a secondary field profile. This is coordinated with the Webmaster’s Office.

• The merchant’s pages will not collect or store credit card numbers or any personally-identifiable information. This is exclusively handled by the èßäÊÓƵapp ePayment system. “Personally identifiable information” includes but is not limited to credit card numbers, Social Security numbers, and driver’s license number. Exceptions must be approved by the Associate Vice President for Information Technology Services. This rule is critical. Non-approved exceptions are in violation of University Policy, and appropriate action will be taken to disable the merchant's site.
• The Webmaster’s Office must certify the merchant’s application before it can use the èßäÊÓƵapp ePayment system. This ensures that the èßäÊÓƵapp ePayment system can correctly process data passed to it by the merchant application. In certifying a merchant application, the Webmaster’s Office will test the merchant system by simulating orders. These simulated orders will verify that the merchant application passes the correct fields in the correct format to the èßäÊÓƵapp ePayment system. The Webmaster’s Office also verifies that the merchant application correctly transfers control to the èßäÊÓƵapp ePayment System. The Webmaster’s Office will not inspect code, verify correct math, verify optional fields, or verify the internal workings of the merchant application.
• The merchant must identify each transaction with a unique invoice number that complies with the invoice number schema. We provide an invoice number generator to simplify this.
• The merchant must always collect a billing address. The merchant may choose to also collect a shipping address if products or goods are to be shipped. Shipping address must be requested after the billing address. The ePayment application utilizes an address verification process. To prevent rejections, the billing name and address must match what is on the credit card or checking account. The merchant is strongly urged to put a statement by the billing address fields that instructs buyer to enter the same name and address that appear on credit card statements.
  
  Following is a suggested statement:
  
  
  Please make sure the name and address you have entered match your credit card statement information. The credit card transaction will not be accepted unless this information matches exactly.
• Two important considerations for the country fields:
  • A blank country field will cause the address to be validated as if it is a US address. Therefore, international transactions with a blank country field will fail.
  • To guarantee US address verification, the country field must be blank, nonexistent, or contain "USA".

Required and Optional Fields

Field Name	Value	Required or optional
First_Name	First name of buyer
Last_Name	Last name of buyer
Billing_Address	Buyer’s billing address
Billing_Address_2	Buyer’s billing address line 2
Billing_City	Buyer’s billing city
Billing_State	Buyer’s billing state
Billing_Zip	Buyer’s billing ZIP code
Billing_Country	Buyer's billing country (important note)
Billing_Phone	Buyer’s billing phone number
Shipping_Address	Buyer’s shipping address
Shipping_Address_2	Buyer’s shipping address line 2
Shipping_City	Buyer’s shipping city
Shipping_State	Buyer’s shipping state
Shipping_Zip	Buyer’s shipping ZIP code
Shipping_Country	Buyer's shipping country (important note)
Shipping_Phone	Buyer’s shipping phone number
Email	Buyer’s email address
Amount	Total dollar amount of purchase. This must be decimal and may not have letters, symbols, or dollar signs.
Description	HTML-formatted order description that will appear on the credit card collection and receipt pages. This description must be sufficient to act as the body of a receipt. Note: all double quote marks will be replaced with single quote marks.
Invoice_Num	This is a unique invoice number. Merchant must ensure that this is unique or transaction will fail. It is recommended that you use our invoice number creator to create invoice numbers.
Account	4 digit account number
Fund	2 digit fund number
Org	6 digit org number
Login	Your merchant ID
	HTML-formatted paragraph that is to appear before all other text on the account info collection page. Note: this supplements, NOT REPLACES, the existing wording.
Intro_Receipt	HTML-formatted paragraph that is to appear immediately before the receipt. Note: this supplements, NOT REPLACES, the existing wording.

: required : optional

Invoice Number Schema