Planned End Date (if known): The date the emarket should be decommissioned if this store should not remain active after a certain date.

Transcription

1 An ecommerce Request Form [.pdf] must be completed and approved before accepting ecommerce credit card payments via Cashnet emarket, a university approved ecommerce application. The following instructions and information will help with preparing the ecommerce Request Form. General Information TRAIN Store Number: The store number (if known) for a request pertaining to a store created during a training session or a store that is not yet live. If the TRAIN storefront number is unknown input unknown or n/a for not applicable. Request Date: The date the request form was prepared. Planned Launch Date: The date the emarket should go live. This date can be set in advance, but should factor in the following processing times: 5-7 business days for form approval Adequate time to create and test the emarket 3 business days from request approval to transition to production Planned End Date (if known): The date the emarket should be decommissioned if this store should not remain active after a certain date. Storefront Number(s) to be decommissioned: The storefront number if the emarket is a replacement for a storefront in the university s legacy ecommerce application. If the storefront number is unknown input unknown or input n/a for not applicable. Merchant Organization Information Requesting Organization or Department Name: The name of the organization or department that is responsible for the requested emarket. Business Contact Name/ /Title/Phone: The contact information for a person to whom business questions about the requested emarket should be referred. Technical Contact Name/ /Title/Phone: The contact information for a person to whom technical questions about the requested emarket should be referred. ecommerce Information Briefly describe the purpose of the checkout page or storefront, the products and/or service offered for sale, and the target customers/market (students, CMU employees, alumni, or individuals outside the campus): Input details as requested and any information that may be unique in the requested emarket environment for consideration or documentation purposes.

2 Is this a Checkout or Storefront: Select applicable choice below. Checkout: A campus or third-party designed web page that redirects online shoppers to the Cashnet application at checkout to select a payment method and provide payment information to process the transaction. Storefront: An online shopper/payer s entire shopping experience, including credit card processing, happens in Cashnet without redirection for payment. Storefront/Checkout name: The preferred name for the emarket. This name will be the default title of the page and must be limited to 50 characters. Administrator The contact information for a person(s) to whom system notification and other operational communications about the requested emarket should be directed. You may provide multiple contacts or a distribution list in this field. Help The contact information for a person(s) to whom questions from online shoppers/payers about the requested emarket should be directed. This will be displayed in the Help section of the website. You may provide an individual or a distribution list in this field. Failed Transaction The contact information for a person to whom transaction notifications about the requested emarket should be directed for resolution. An individual or a distribution list may be provided in this field. Successful transaction notifications are also sent to this but may be disabled at the store administrator s preference. Does this revenue relate to a sponsored project award (e.g. program income): Select yes or no based on the purpose of your storefront. Estimated Annual Revenue: The estimated amount of annual sales dollars that the requested emarket is expecting to support. Estimated Annual Refund: The estimated amount on annual refunds that this requested emarket expects to process. Enter 0 if none is expected. Do you plan to use the Address Verification System (AVS): Select yes or no. AVS verifies the billing address of the payer s credit card with the address on file at the credit card company prior to transaction authorization to reduce the risk of fraudulent transactions and/or chargeback's for the requested storefront. Do you wish to set up server-to-server file transfer for your transaction files: If yes, the emarket technical contact will receive an with further instruction.

3 If a Checkout Page: Department Contact for PCI Compliance: The contact information for the person to whom credit card compliance questions should be directed for the requested emarket. Callback URL(s): Successful Transaction The URL of the page where payers should be directed after their transaction is successfully processed. Failed Transaction The URL of the page where payers should be directed if their transaction failed during processing. Third-party Integration Partner (if used): The name the third-party integration partner that will manage the storefront application. If the provider is not on the list at the end of these directions, additional setup time may be required. Ask the third-party integration partner for an estimate of how long they will require for setup. If custom application, provide URL: If relevant, the associated URL of a self-developed storefront that should be integrated with Cashnet. Types of credit cards the site will accept: Select the types of cards the requested emarket is able to accept. Only the combination options listed are available. Will the site collect payments for an event?: Select yes or no based on the purpose of your storefront. If the event is recurring, please provide begin and end dates: If relevant, input begin and end dates of the event that is referenced in the previous field. Add an additional list to this form and note see attached in the date fields if more room is needed. Cashnet Access Roles: Multiple people per role and/or multiple roles per person is permitted. Input the associated Andrew ID for the following roles: CMU Owner (required): This role has the most control and is for the person(s) who is creating the storefront, adding items, customizing the page, etc. Typically, someone with operational responsibility over the site would require this access level. Report Manager Inquiry (optional): This role is for a person(s) who needs to review information about the site, but is not permitted to change setup information. Typically, someone with reporting requirements would require this access level. emarket Admin (optional): This role has the least control and cannot update the page or item setups. Typically, someone with responsibility for managing the returns process would require this access level.

4 Other Specify if there is some other type of access a persons(s) require. Oracle Account Information Oracle string to charge for monthly credit card processing fees: The Oracle account string(s) to which credit card processing fees should be charged. Generally, the Organization for the fees and expenses should be the same. A store may have multiple revenue codes, but only one expense. If this is not true, note the reason for this in the description box (the first box under ecommerce Information on the form). Provide a valid Oracle revenue string for each product and/or service offered for sale: Input the general ledger (GL) Oracle account string(s) to which revenue should be recognized. Revenue account strings must have a Function of 000. Attach additional pages to this form as needed. Grants Accounting (GA) String(s): The Project-Task-Award (PTA) associated with this storefront if using any of the following GL Funding source numbers for revenue: , , , , , , 066xxx, , , , Approvals Department Business Manager Approval: Name, signature, and date for business manager approval. Submission Submit the completed form to cashnet-info@lists.andrew.cmu.edu for processing. Processing The Treasury, Financial Reporting and Taxation departments within the Finance Division will review the submitted form and will contact the appropriate stakeholder directly with any questions that may arise. Please allow approximately 5-7 business days from form submission for approval. Upon form approval, a provisional store number and login credentials will be provided via for use in the Cashnet TRAIN environment. This environment can be used to create, test, and update your Cashnet emarket to suit business needs. The person(s) who creates/updates the store is responsible for testing the store before it transitions to production. Submit a request to cashnet-info@lists.andrew.cmu.edu when ready to transition to production. Allow approximately three business days for the emarket to be available in production. The emarket cannot be transitioned to production until the completed ecommerce Request Form [.pdf] has been approved.

5 To change setup details after the emarket transitions to production, contact Cashnet and Third-Party Vendors If you work with a vendor not on this list and wish to integrate with Cashnet, direct the vendor to visit and fill out the requested information. The Cashnet sales department will contact the vendor directly to complete the agreement. For more information, visit or contact cashnet-info@lists.andrew.cmu.edu.