Accept Credit Card Payments for UBF Accounts (UB Marketplace)
On this page:
Credit card payments are accepted through UB Marketplace, available through the UB Foundation (UBF). Learn how UB Marketplace works to collect credit card and e-check payments.
UBF Checkout To Be Replaced by UB Marketplace
UBF is transitioning from UBF Checkout to UB Marketplace. New accounts will be set up using UB Marketplace.
You may continue to use existing UBF Checkout sites.
About UB Marketplace
UB Foundation (UBF) provides a wide range of financial services that support UB units, faculty, staff and students. One of these services is UB Marketplace — an e-commerce service offered by UBF.
UB Marketplace lets you use your website to collect credit card payments and e-check payments online. For example, you can use UB Marketplace to collect conference registrations and tickets.
UB Marketplace Funds for UBF Accounts
Funds from UB Marketplace are deposited into your UBF account. Please note that you must have a UBF account — and complete the UBF Account Setup Form — before using UBF UB Marketplace.
UB Marketplace Setup for UBF Accounts
Upon requesting your UB Marketplace with the UB Marketplace Setup Form, UBF will notify you and provide you with a link and settings you will use to set up your product(s).
Log in with the link provided to you by UBF. If this is your first time logging in, you will need to register and notify UBF once you have created your account. Please send your UB Marketplace login and product category to ubfacr@buffalo.edu once you have registered so that UBF can assign permissions to your login.
After UBF has confirmed your permissions have been assigned, log into your UB Marketplace using the link provided by UBF and proceed to set up your product and attributes in UB Marketplace.
Click Administration in the top black bar in the center.
In the left menu, click Catalog and then Products.
Click Add new, or edit an existing product.
If this is your first time logging in, you will need to switch the view from Basic to Advanced view by clicking the Basic buttoon.
Fill out the General Information:
- Product name - name of your product or event
- Short description to describe your product. If you would like to format the text, you can enter it in the Full description and then click Tools, Source code, then copy the source code and paste it into the Short description box. Then remove it from the Full description box.
- Customer Reviews - Allows customers to review your product or event. Consider unchecking this for one-time events.
Be sure to uncheck the following item.
- Published – ****This step is important because UBF needs to program your product to deposit properly into your account before it is published!****
If your product has a recurring fee, check the box for Recurring product.
- Cycle length – time period recurring order can be repeated.
- Cycle period – units time period is measured in.
- Total Cycles – number of times the customer will be billed
Enter your pricing information, the only field required is the price:
- Price – amount to bill customer for product
- Tax exempt – determines whether tax will be charged at checkout.
- Tax category – select an item from the drop down if you will be selling a physical product.
- For more information regarding taxable and exempt property and services, see NY Tax Bulletin ST-740
Enter your inventory information:
- Inventory method – select Track inventory if the quantity of available spaces or products is limited.
- Stock Quantity – enter quantity of products or spaces available. Product will disappear from UB Marketplace once it is sold out.
- Display availability – shows customer how many spaces or products are remaining
- Minimum/Maximum cart qty – minimum and maximum number of products a customer may purchase
- Not returnable – check the box to prevent a customer from submitting a return request.
Uncheck Shipping enabled, unless you will be shipping a product.
Enter your Mappings provided by UBF:
- Categories - Select the product category provided to you by UBF by beginning to type the category in the box, or selecting it from the drop-down menu.
- Vendor - Choose the vendor group provided to you by UBF.
Click Save and Continue Edit in the top right corner
· Click the Pictures Tab, Click Upload a file and then select your product image, then click Add product picture. The preferred display size is 500x500 pixels.
Click Save and Continue Edit in the top right corner
Click the Product attributes tab, then Add a new attribute.
Select a name attribute from the drop-down menu. You must select a name attribute as the person signing up will not always match the billing information.
Click Save and Continue Edit.
Enter the Product attribute info.
- Is required – Check the box – this will require an entry in the field
- Control type – Select Textbox so that the customer can type a name in the textbox.
- Display order – if you will be using more than one product attribute, enter the number in which you would like this attribute to display in order.
Click Save and Continue Edit in the top right corner.
Add additional Product attributes you may need to collect, or for price adjustments/add-ons your product will need. See Product attribute instructions for more information.
After you have added all product attributes needed, click Save in the top right corner.
Preview your product to test it and make sure it is displaying properly and make any desired changes.
After you have verified your product is displaying properly, notify ubfacr@buffalo.edu that your product is ready for publishing. UBF will program your product to deposit into your account and provide you with your UB Marketplace link for customers.
Product Attributes are used in the UB Marketplace to collect data as well as to modifications to products. For instance, you can use an attribute to collect a registrant’s name, or if you are hosting an event and selling a t-shirt as an option, you can add an attribute to your event and make the t-shirt an add-on.
*Always add an attribute for a registrant’s name as the billing name can be different*
To begin setting up Product Attributes, you must set up your product first. If you have not set up your product, please see the section above regarding adding products to UB Marketplace.
Click Administration in the black bar at the top of the screen.
Click Catalog and then Products.
Select your product by clicking the Edit button.
Click the Product attributes tab.
Click add a new attribute.
If your attribute does not exist you will need to request a new attribute by emailing ubfacr@buffalo.edu with your request.
Click the Attribute pull down menu and add an attribute that is for a name, such as student name or registrant name – You must always add a name attribute as payment information can differ from the person registering.
Set the display order number and then click Save.
Add any additional attributes for collecting additional information or adding features onto your product.
Product Attributes are used in UB Marketplace to collect data as well as to modifications to products. For instance, you can use an attribute to collect a registrant’s name, or if you are hosting an event and selling a t-shirt as an option, you can add an attribute to your event and make the t-shirt an add-on.
For this example, we will add a t-shirt.
To begin setting up Product Attributes, you must set up your product first. If you have not set up your product, please see the section above regarding adding products to UB Marketplace.
Click Administration in the black bar at the top of the screen.
Click Catalog and then Products.
Select your product by clicking the Edit button.
Click the Product attributes tab.
Click add a new attribute.
For this example, we will add a t-shirt by selecting What is your T-Shirt size and click Save and Continue Edit.
If your attribute does not exist you will need to request a new attribute by emailing ubfacr@buffalo.edu with your request.
Click Values, then Add a new value.
Enter your attribute values and then click Save.
- Name – this is the name of the attribute value.
- Price adjustment – this is the amount by which the price of the product will increase by selecting the attribute value. If your original product includes your attribute value in the price, you may skip this field. If your attribute value affects the price, enter your price adjustment here. A negative value will reduce the price of your original product.
- Display order – this is the order in which the attribute value will appear.
Enter additional product values if needed.
After you have finished adding attribute values to your product, preview your product to make sure your attributes display in the correct order your product by clicking the Preview button at the top right of your screen.
Verify your attributes are displaying properly. In this case, we have the registrant name and T-shirt size. Depending on the size of the t-shirt, the price increases by $10 or $15 if a T-shirt is added to the product.
After you have verified your product is displaying properly, notify ubfacr@buffalo.edu so that UBF can program your product to deposit funds into your UBF account and publish it for use.
Manually Process Credit Cards
Please call Kaity Ross at (716)645-8753 or hand deliver or mail the Payment Card Authorization Form below with a UBF Deposit Transmittal Form.
UBF Checkout Developer Guide
UBF Checkout Developer Guide
This guide describes how to integrate your website with UBF Checkout by using HTML forms. UBF Checkout lets you accept credit card or eCheck payments for:
On this page:
Intended Audience
This guide is for:
- Schools, units, departments and developers who want to understand the checkout experience that people go through when they make payments with UBF Checkout
- Developers who want to learn how to accept payments through their website using UBF Checkout
Document Feedback and Questions
Help us improve this guide (or ask questions) by emailing:
UBF Checkout Demo
Payment Experience
Payers add the items you are selling on your website to the UBF Checkout shopping cart hosted by the UB Foundation. Payers may then return to your website to add more items or enter their billing information to make a payment.
Payers view and print payment confirmation.
Payers receive receipt in email
Getting Set Up
UBF transition from Checkout to UB Marketplace
UBF is transitioning acceptance of electronic payment from UBF Checkout to UB Marketplace. UBF is no longer setting up new sites in UBF Checkout. You may continue to use your existing UBF Checkout site at this time if you have one.
If you do not already have UBF Checkout, you will need to set up a UB Marketplace to accept electronic payments. To set up an UB Marketplace, complete the UB Marketplace setup form.
To accept payments through UBF Checkout you will need:
- Your own web space where you are able to to create or edit web pages
- A basic understanding of HTML and HTML forms
- The site code provided by the UB Foundation
- The UBF account number(s) provided by the UB Foundation
Updating Your Site's Information
If you need to update your site's information already on file with UBF (e.g. merchant email address) please email Cindy Johannes at devclj@buffalo.edu with your 4-digit site code and the new information that needs updating.
Generating Code for HTML Forms and Email Payment Links
You may use the utility located in the appendix of this document to generate a basic HTML form as well as an email payment link that will add a single item to the UBF Checkout shopping cart. You will need a valid site_code and UB Foundation account number in order to successfully add items to the shopping cart. Use the utility (requires Javascript to be enabled in your web browser.)
Testing Your Form
The Test Mode URL to submit your form to is:
https://ubfoundation.buffalo.edu/test/checkout/index.php
It is strongly recommended that you test your form with the above URL before you begin accepting payments in Live Mode. Test Mode will display detailed development errors, if any, such as invalid ansite_code or ubf_account, when you add your item(s) to the shopping cart. Live Mode will only display a general error message to payers if there are any development errors.
If you do not see an error message when you add your item(s) to the UBF Shopping cart, your form is ready to begin accepting payments.
Payment notifications will be sent to the merchant email associated with each of your UBF accounts in the form of a merchant-copy receipt whenever a purchase is made. This receipt will contain detailed information about the payment made to the account. For more information on other payment notification methods please see Receiving Payment Notifications.
In Test Mode, our payment gateway will not submit billing information to financial institutions for payment authorization. However, merchant and payer emails will still receive their respective test receipts when completing transactions in Test Mode and will look as they will for live transactions.
A passed-in merchant_email_test will override the merchant email address on file with UBF when in test mode. This is useful if you already have live forms accepting payments but need to test new ones at the same time.
Similarly, if you're already using a silent post URL with live forms, you can test with another URL by using the silent_post_test variable to ensure it is functioning as you expect it to. To do so, you must fully finish the test transaction by entering billing information and clicking the "Submit Payment" button.
The following test credit card numbers may be used for testing credit card transactions:
- Visa - 4007000000027
- Mastercard - 5424000000000015
- Discover - 6011000000000012
- American Express - 370000000000002
The following test bank routing numbers may be used for testing e-check transactions:
- 222371863
- 307075259
- 052000113
When you switch to Live Mode the above test numbers will always result in declined transactions as they are not real.
Going Live
When you are ready to begin accepting payments, be sure your form is set to submit to the Live Mode URL. Any payment made in Test Mode will be ignored by our payment gateway and will not be processed!
The Live Mode URL is:
Adding Individual Items to the Shopping Cart
Basic Requirements for Individual Items
In order to add an item to the shopping cart, your web form or hyperlink must submit the following required variables.
| Name | Description | Max Character Length |
|---|---|---|
| add | Variable to add a single item to the shopping cart. Value must be set to "1". | 1 |
| amount | The price of the item. Minimum 5, maximum 25000. | May vary |
| item_name | The name or brief description of the item. | 256 |
| service_type_code | The type of service or product code assigned to the item. View the list of possible codes here. If you are unsure which service type code to use with your item, please contact Cindy Johannes at 645-8720. | 8 |
| site_code | The alpha-numeric code UB Foundation assigns to you. | 16 |
| ubf_account | UBF account number associated with the item. | 16 |
The following is a basic HTML web form that includes all the required variables.
<form action="https://ubfoundation.buffalo.edu/test/checkout/index.php" method="post"> <input type="hidden" name="add" value="1"> <input type="hidden" name="amount" value="50.00" /> <input type="hidden" name="item_name" value="UB Bulls Jersey" /> <input type="hidden" name="service_type_code" value="7725" /> <input type="hidden" name="site_code" value="YourSiteCode" /> <input type="hidden" name="ubf_account" value="YourUBFAccountNumber" /> <input type="submit" name="submit" value="Add to Cart" /> </form>
Optional Variables for Individual Items
| Name | Description | Max Character Length |
|---|---|---|
| custom | Each item can have 10 variable name/value pairs that you may specify to further track and identify your item or payer. These variables are not shown to the payer during checkout. See example for usage. These variables will be sent to your silent post URL, if set up, and are located within the items sub-array within the greater POST variable array. For more information on retrieving this variable value from within your silent post URL, see the section Accessing Detailed Item Information. | May vary |
| discount_amount | The item discount. If you specify discount_amount and discount_amount2 is not defined, this flat amount is applied regardless of the quantity of items purchased. Must be less than amount. | May vary |
| discount_amount2 | The discount amount for each additional quantity of the item. Cannot be greater than amount. | May vary |
| discount_num | Number of additional quantities of the item to which discount_amount2 applies. Applicable when you use discount_amount2 or discount_rate2. Use this variable to specify an upper limit on the number of discounted items. | May vary |
| discount_rate | Discount rate (percentage) associated with an item. It must be set to a value less than 100. If you do not set discount_rate2, the value in discount_rate this rate is charged regardless of the quantity of items purchased. | May vary |
| discount_rate2 | Discount rate (percentage) associated with each additional quantity of the item. It must be equal to or less than 100. A discount_rate must also be specified as greater than or equal to 0 for discount_rate2 to take effect. | May vary |
| donation_fund | UBF account designated for philanthropic purposes. This will trigger a prompt to make an additional donation on the payment screen. | 16 |
| header_bg_color | The background color for the header of the checkout pages. Valid value is an HTML hexadecimal color code. | May vary |
| header_image | The URL of the image at the top of the checkout pages. The image's maximum size is 960 pixels wide by 100 pixels high. Note: GIF, PNG, and JPG only. Must be HTTPS URL. | May vary |
| header_font_color | The text color for your site name in the header of the checkout pages. Valid value is an HTML hexadecimal color code. | May vary |
| merchant_email_test | Testing email that will override merchant email on file with UBF. This is useful if you already have live forms accepting payments but need to test new ones at the same time. Operational in test-mode only. | May vary |
| option | Options are a way to allow the customer to choose customizations (such as size or color) for an individual item. Each item can have 10 option name/value pairs. See example for usage. | May vary |
| option_amount | For differently-priced options. This will allow you to charge a different amount if the payer selects certain options. See example for usage. | May vary |
| quantity | The number of items. Must be a positive integer. Default is "1". | May vary |
| return_url | The URL of the page on your website that payers return to when they click the "Return to [Your Site Name]" button on the UBF Checkout payment confirmation page. | May vary |
| shipping | The cost of shipping this item. If you specify shipping and shipping2 is not defined, this flat amount is charged regardless of the quantity of items purchased. | May vary |
| shipping2 | The cost of shipping each additional quantity of this item. | May vary |
| shopping_url | The URL of the page on your website that payers return to when they click the Continue Shopping button on the UBF Checkout shopping cart page. | May vary |
| silent_post_test | Testing URL that will override the silent post URL on file with UBF for the item's associated UBF account. This is useful if you already have live forms accepting payments but need to test new ones at the same time. Operational in test-mode only. For more information on what is posted back to your script, see Receiving Payment Notifications. | May vary |
| thank_you_message | Text to replace the default "Thank you for your payment!" on the confirmation page upon completion of their order. | May vary |
Adding a Batch of Items to the Shopping Cart
Basic Requirements for Batched Items
The batch method allows several items to be added to the cart at once, instead of one at a time as outlined above in the "Adding Individual Items to the Shopping Cart" section. In order to add a batch of items at once to the shopping cart, your web form or hyperlink must submit the following required variables with _x appended to them where x is the item number.
For example:
- item_name_1 must have corresponding amount_1, service_type_code_1 and ubf_account_1 variables set
- item_name_2 must have corresponding amount_2, service_type_code_2 and ubf_account_2 variables set
- item_name_3 must have corresponding amount_3, service_type_code_3 and ubf_account_3 variables set
- and so on for each additional item.
| Name | Description | Max Character Length |
|---|---|---|
| batch | Variable to add a batch of items to the shopping cart. Value must be set to "1". | 1 |
| amount_x | The price of item x. | May vary |
| item_name_x | The name or brief description of item x. | 256 |
| service_type_code_x | The type of service or product code assigned to item #1.View the list of possible codes here. If you are unsure which service type code to use with your item, please contact Cindy Johannes at 645-8720. | 8 |
| site_code | The alpha-numeric code that we assign to you. | 16 |
| ubf_account_x | UBF account number associated with item x. | 16 |
Optional Variables for Batched Items
| Name | Description | Max Character Length |
|---|---|---|
| custom_x | Each item can have 10 variable name/value pairs that you may specify to further track and identify your item or payer. These variables are not shown to the payer during checkout. See example for usage. These variables will be sent to your silent post URL, if set up, and are located within the items sub-array within the greater POST variable array. For more information on retrieving this variable value from within your silent post URL, see the section Accessing Detailed Item Information. | May vary |
| discount_amount_batch | Single discount amount applied to the entire batch of items in the cart. It must be less than the selling price of all items combined in the cart. It will override any individual item discount_amount_x values, if present. | May vary |
| discount_amount_x | The discount amount for item x. It must be less than the selling price of the associated item. This amount is applied regardless of the quantity of the associated item. | May vary |
| discount_rate_batch | Single discount rate (percentage) applied to the entire batch of items in the cart. It must less than 100. This will override any individual item discount_rate_x values, if present. | May vary |
| discount_rate_x | The discount rate for item x. It must be less than 100. This rate is applied regardless of the quantity of the associated item. | May vary |
| donation_fund | UBF account designated for philanthropic purposes. This will trigger a prompt to make an additional donation on the payment screen. | 16 |
| header_bg_color | The background color for the header of the checkout pages. Valid value is an HTML hexadecimal color code. | May vary |
| header_image | The URL of the image at the top of the checkout pages. The image's maximum size is 960 pixels wide by 100 pixels high. Note: GIF, PNG, and JPG only. Must be HTTPS URL. | May vary |
| header_font_color | The text color for your site name in the header of the checkout pages. Valid value is an HTML hexadecimal color code. | May vary |
| merchant_email_test | Testing email that will override merchant email on file with UBF. This is useful if you already have live forms accepting payments but need to test new ones at the same time. Operational in test-mode only. | May vary |
| option_x | Each item in a batch can have 10 option name/value pairs. Options are displayed next to each item in the shopping cart. See example for usage. | May vary |
| quantity_x | The number of item x.. Must be a positive integer. Default is "1". | May vary |
| return_url | The URL of the page on your website that payers return to when they click the "Return to [Your Site Name]" button on the UBF Checkout payment confirmation page. | May vary |
| shipping | The cost of shipping for the entire order. | May vary |
| shopping_url | The URL of the page on your website that payers return to when they click the Continue Shopping button on the UBF Checkout shopping cart page. | May vary |
| silent_post_test_x | Testing URL that will override the silent post URL on file with UBF for item x. This is useful if you already have live forms accepting payments but need to test new ones at the same time. Operational in test-mode only. For more information on what is posted back to your script, see Receiving Payment Notifications. | May vary |
| thank_you_message | Text to replace the default "Thank you for your payment!" on the confirmation page upon completion of their order. | May vary |
Variables for Prepopulating Payer Fields
The billing fields can be prepopulated by submitting the following variables.
| Name | Description | Max Character Length |
|---|---|---|
| billing_first_name | First name | 64 |
| billing_last_name | Last name | 64 |
| billing_address | Street | 128 |
| billing_city | City | 64 |
| billing_state | State (valid state codes XML) | 64 |
| billing_zip | Zip | 32 |
| billing_country | Country (valid country codes XML) | 64 |
| billing_email | 128 | |
| billing_phone | Phone number | 32 |
Receiving Payment Notifications
You may receive payment notifications from UBF Checkout by:
- merchant-copy email receipts sent to your UBF account merchant email address
- notifications sent to your silent post URL, if set up
Merchant-Copy Email Receipts
Payment notifications are sent to the merchant email associated with the UBF account that received a payment in the form of a merchant-copy receipt. This receipt contains detailed information about the payment made to the account.
Silent Post URL
The silent post URL is a URL to a script that resides on your web server. This is able to parse HTTP POST variables using a server-side scripting language, such as PHP or ASP.NET. Advanced web programming knowledge is required in order to properly code a silent post URL script.
With the silent post URL, you can:
- Save payment details to a database
- Send additional notifications to email addresses other than the merchant email associated with the UBF account
- Automate back-office and administrative functions, such as fulfilling orders and tracking payers
If you've indicated a silent post URL within the UBF account set-up form, then the variables outlined below are sent to that URL as HTTP POST variables. If you'd like to add or change a silent post URL, please email Cindy Johannes at devclj@buffalo.edu and include the UBF account number as well as the URL you'd like to use for you silent post URL.
Variables Sent to Your Silent Post URL
| Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| authnet_transaction_id | Authorize.net transaction ID | ||||||||||||||||||||||||||||||||||||||||||||||
| bank_acct_last_4_digits | The last 4 digits of the bank account charged. Absent for credit card and declined credit card transactions. | ||||||||||||||||||||||||||||||||||||||||||||||
| billing_first_name | Payer's billing first name | ||||||||||||||||||||||||||||||||||||||||||||||
| billing_last_name | Payer's billing last name | ||||||||||||||||||||||||||||||||||||||||||||||
| billing_address | Payer's billing street | ||||||||||||||||||||||||||||||||||||||||||||||
| billing_city | Payer's billing city | ||||||||||||||||||||||||||||||||||||||||||||||
| billing_state | Payer's billing state | ||||||||||||||||||||||||||||||||||||||||||||||
| billing_zip | Payer's billing zip | ||||||||||||||||||||||||||||||||||||||||||||||
| billing_country | Payer's billing country | ||||||||||||||||||||||||||||||||||||||||||||||
| billing_email | Payer's billing email | ||||||||||||||||||||||||||||||||||||||||||||||
| billing_phone | Payer's billing phone number | ||||||||||||||||||||||||||||||||||||||||||||||
| card_last_4_digits | The last 4 digits on the card charged. Absent for e-check and declined credit card transactions. | ||||||||||||||||||||||||||||||||||||||||||||||
| card_type | The type of card charged. (VISA, MASTERCARD, AMERICANEXPRESS, DISCOVER) Absent for e-check and declined credit card transactions. | ||||||||||||||||||||||||||||||||||||||||||||||
| discount_amount_batch | The value of discount_amount_batch passed in. | ||||||||||||||||||||||||||||||||||||||||||||||
| discount_rate_batch | The value of discount_rate_batch passed in. | ||||||||||||||||||||||||||||||||||||||||||||||
| items | Indexed array containing the details of each item in the transaction. For more information on how to access these variables within the greater HTTP Post array please see the section "Accessing Detailed Item Information".
| ||||||||||||||||||||||||||||||||||||||||||||||
| merchant_email | Email on file with the UB Foundation that receives merchant-copy email receipts. | ||||||||||||||||||||||||||||||||||||||||||||||
| pay_method | Payment method used, "credit" or "e-check". | ||||||||||||||||||||||||||||||||||||||||||||||
| shipping | Order shipping amount | ||||||||||||||||||||||||||||||||||||||||||||||
| shipping_first_name | Payer's shipping first name | ||||||||||||||||||||||||||||||||||||||||||||||
| shipping_last_name | Payer's shipping last name | ||||||||||||||||||||||||||||||||||||||||||||||
| shipping_address | Payer's shipping street | ||||||||||||||||||||||||||||||||||||||||||||||
| shipping_city | Payer's shipping city | ||||||||||||||||||||||||||||||||||||||||||||||
| shipping_state | Payer's shipping state | ||||||||||||||||||||||||||||||||||||||||||||||
| shipping_zip | Payer's shipping zip | ||||||||||||||||||||||||||||||||||||||||||||||
| shipping_country | Payer's shipping country | ||||||||||||||||||||||||||||||||||||||||||||||
| site_code | The passed-in site_code | ||||||||||||||||||||||||||||||||||||||||||||||
| sub_total | Order subtotal. Includes tax and shipping. | ||||||||||||||||||||||||||||||||||||||||||||||
| tax | Order tax | ||||||||||||||||||||||||||||||||||||||||||||||
| total_amount | Order total amount | ||||||||||||||||||||||||||||||||||||||||||||||
| ubf_transaction_id | UBF unique transaction identifier (UBF's Transaction ID) | ||||||||||||||||||||||||||||||||||||||||||||||
| x_authnet_auth_code | Authorize.net authorization or approval code | ||||||||||||||||||||||||||||||||||||||||||||||
| x_avs_code | Authorize.net Address Verification Service (AVS) response code. See Authorize.net documentation at http://www.authorizenet.com/support/AIM_guide.pdf for more information. | ||||||||||||||||||||||||||||||||||||||||||||||
| x_response_code | Authorize.net response code: "1" = This transaction has been approved. "2" = This transaction has been declined. "3" = There has been an error processing this transaction. Please code your message to the payer accordingly. Only when receiving a "1" should you confirm with the payer that the transaction is a success. See Authorize.net documentation at http://www.authorizenet.com/support/AIM_guide.pdf for more information. | ||||||||||||||||||||||||||||||||||||||||||||||
| x_response_reason_text | A brief description of the result, which corresponds with the response reason code. This is especially handy to present as additional information to the payer if something went wrong with the transaction such as an invalid credit card number for example. See Authorize.net documentation at http://www.authorizenet.com/support/AIM_guide.pdf for more information. | ||||||||||||||||||||||||||||||||||||||||||||||
| x_response_reason_code | A code that represents more details about the result of the transaction See section "Response Code Details" in the Authorize.net documentation at http://www.authorizenet.com/support/AIM_guide.pdf for more information. | ||||||||||||||||||||||||||||||||||||||||||||||
| x_response_sub_code | A code used by Authorize.net for internal transaction tracking |
Accessing Detailed Item Information
Detailed item information is sent to your silent post URL (if set up) in the form of an array within the greater HTTP POST array. Items are defined by a sequential index number:
items[1]
items[2]
items[3]
...etc.
In PHP, this translates to:
$_POST['items'][1]
$_POST['items'][2]
$_POST['items'][3]
...etc.
To refer to each item's variables in PHP (using item_name as an example):
$_POST['items'][1]['item_name']
$_POST['items'][2]['item_name']
$_POST['items'][3]['item_name']
...etc.
To refer to both the custom and option sub-arrays within the greater items array in PHP:
$_POST['items'][1]['option']['YourOptionLabel']
$_POST['items'][2]['option']['YourOptionLabel']
$_POST['items'][3]['option']['YourOptionLabel']
...etc.
$_POST['items'][1]['custom']['YourCustomLabel']
$_POST['items'][2]['custom']['YourCustomLabel']
$_POST['items'][3]['custom']['YourCustomLabel']
...etc.
Appendix
Service Type Codes
If you are unsure which service type code to use with your item, please contact Cindy Johannes at 645-8720.
Table a.1 Valid service_type_code values.
New Service Type Codes
| Value | Description |
| 4500 | Continuing Education |
| 4700 | AccuFund Service Payments |
| 4703 | Service Taxable Clothing |
| 4704 | Merchandise Taxable Non-Clothing |
| 4705 | Merchandise Non-Taxable |
| 4717 | Student Fees |
| 4720 | Advertising |
| 4728 | Contest Revenue |
| 4760 | Membership |
Old Service Type Codes
| Value | Description |
| 7702 | Event Admission |
| 7704 | Sales Taxable |
| 7705 | Sales Non-Taxable |
| 7707 | Dinners & Social Functions |
| 7709 | Foreign Programs & Tuition |
| 7710 | Lab/Clinic Activities/Co-Pay |
| 7711 | Orientation |
| 7712 | Parent/Student Welcome/Picnic |
| 7714 | Publications Non-Taxable |
| 7715 | Rental |
| 7716 | Student Competition & Recreation |
| 7717 | Student Fees & Tuition |
| 7718 | Uniform Data Systems |
| 7720 | Technology/Software Services |
| 7725 | Clothing Taxable |
| 7726 | Clothing Non-Taxable |
| 7728 | Sponsorship |
| 7729 | Raffles |
| 7800 | Continuing Ed & Conference Registration |
Sample HTML Codes
Example Usage for Option Variable
Each item can have up to 10 option variables. Option variables are displayed to the user on the Checkout payment and confirmation pages.
Used with drop down box
<label for="size">Jersey Size:</label> <select name="option[Size]" id="size"> <option value="S">S</option> <option value="M">M</option> <option value="L">L</option> <option value="XL">XL</option> </select>
Replace "Size" and option values with any option name and values you wish.
Used with radio buttons
<input type="radio" name="option[Color]" value="White" id="white" /> <label for="white">White</label> <input type="radio" name="option[Color]" value="Blue" id="blue" /> <label for="blue">Blue</label>
Replace "Color", "White" and "Blue" with any name/value pairs you wish.
Used with a text box
<label for="jerseyName">Custom Jersey Name:</label> <input type="text" name="option[Custom Jersey
Name]" value="" id="jerseyName" />
Replace "Custom Jersey Name" with any option name you wish.
Used with check boxes
<input type="checkbox" name="option[Gift Wrap]" value="Yes" id="wrap" /> <label for="wrap">Gift wrap this item</label>
Replace "Gift Wrap" and "Yes" with any option name/value pair you wish.
Example Usage for Option Amount
Used with a drop down box
In this example, if amount is set to "50", selecting either the "XL" or "XXL" options in the "Jersey Size" drop down box. This will override the price of the item in the shopping cart with the correlating price defined in option_amount ("55" or "60" respectively).
<label for="size">Jersey Size:</label> <select name="option[Size]" id="size"> <option value="S">S</option> <option value="M">M</option> <option value="L">L</option> <option value="XL">XL (Adds $5)</option> <option value="XXL">XXL (Adds $10)</option> </select> <input type="hidden" name="option_amount[Size][XL]" value="55" /> <input type="hidden" name="option_amount[Size][XXL]" value="60" />
Example Usage for Custom Variables
Custom variables work just like option variables. The difference is custom variables are hidden from the user throughout the checkout process. Custom variables are meant to store internal information about the transaction that you'd like to keep track of in hidden form inputs, like a customer ID or item code. Custom variables are not shown on the payment screen or confirmation page, like regular option variables (e.g. shirt size or color).
Each item can have up to 10 custom variables.
<input type="hidden" name="custom[MyItemCode]" value="MyItemCodeValue" />
Replace "MyItemCode" and "MyItemCodeValue" with any name/value pair you wish.
Example Usage for Option X
Setting options for item #1
<input type="hidden" name="option_1[YourOptionName1]" value="Your value 1" /> <input type="hidden" name="option_1[YourOptionName2]" value="Your value 2" /> ... <input type="hidden" name="option_1[YourOptionName10]" value="Your value 10" />
Setting options for item #2
<input type="hidden" name="option_2[YourOptionName1]" value="Your value 1" /> <input type="hidden" name="option_2[YourOptionName2]" value="Your value 2" /> ... <input type="hidden" name="option_2[YourOptionName10]" value="Your value 10" />
Example Usage for Custom X
Defining custom variables for item #1
<input type="hidden" name="custom_1[YourVariableName1]" value="Your value 1" /> <input type="hidden" name="custom_1[YourVariableName2]" value="Your value 2" /> ... <input type="hidden" name="custom_1[YourVariableName10]" value="Your value 10" />
Defining custom variables for item #2
<input type="hidden" name="custom_2[YourVariableName1]" value="Your value 1" /> <input type="hidden" name="custom_2[YourVariableName2]" value="Your value 2" /> ... <input type="hidden" name="custom_2[YourVariableName10]" value="Your value 10" />
Example Usage for Donation Fund
<input type="hidden" name="donation_amount" value="Your donation account" />
Robust Example
The following sample HTML form is a full-fledged example for a hypothetical individual item being sold with all or most of the optional fields being used along with various HTML form controls for the item's options.
<h1>UB Bulls Jersey</h1> <form action="https://ubfoundation.buffalo.edu/test/checkout/index.php" method="post"> <input type="hidden" name="add" value="1"> <input type="hidden" name="site_code" value="YourSiteCode" /> <input type="hidden" name="ubf_account" value="YourUBFAccountNumber" /> <input type="hidden" name="service_type_code" value="7725" /> <input type="hidden" name="shopping_url" value="https://yoursite.buffalo.edu/YourItemPage.php" /> <input type="hidden" name="custom[YourCustomVariable1]" value="Your custom value 1" /> <input type="hidden" name="custom[YourCustomVariable2]" value="Your custom value 2" /> <input type="hidden" name="header_font_color" value="#FFFFFF" />
<input type="hidden" name="header_bg_color" value="#666666" />
<input type="hidden" name="item_name" value="UB Bulls Jersey" /> <input type="hidden" name="amount" value="50.00" /> <input type="hidden" name="shipping" value="10" /> <input type="hidden" name="shipping2" value="5" /> <input type="hidden" name="billing_first_name" value="John" /> <input type="hidden" name="billing_last_name" value="Doe" /> <input type="hidden" name="billing_address" value="123 Main St" /> <input type="hidden" name="billing_city" value="Buffalo" /> <input type="hidden" name="billing_state" value="NY" /> <input type="hidden" name="billing_zip" value="14209" /> <input type="hidden" name="billing_country" value="US" /> <input type="hidden" name="billing_email" value="johndoe@example.com" /> <input type="hidden" name="billing_phone" value="555-5555" /> <div> <label for="size">Size:</label> <select name="option[Size]" id="size"> <option value="S">S</option> <option value="M">M</option> <option value="L">L</option> <option value="XL">XL (Adds $5)</option> <option value="XXL">XXL (Adds $10)</option> </select> <input type="hidden" name="option_amount[Size][XL]" value="55" /> <input type="hidden" name="option_amount[Size][XXL]" value="60" /> </div> <div> Jersey color: <input type="radio" name="option[Color]" value="White" id="white" /> <label for="white">White</label> <input type="radio" name="option[Color]" value="Blue" id="blue" /> <label for="blue">Blue</label> </div> <div> <label for="jerseyName">Custom Jersey Name:</label> <input type="text" name="option[Custom Jersey Name]" value="" id="jerseyName" /> </div> <div> <input type="checkbox" name="option[Gift Wrap]" value="Yes" id="wrap" /> <label for="wrap">Gift wrap this item</label> </div> <div> <input type="checkbox" name="custom[Add to mailing list]" value="Yes" id="mailing" /> <label for="mailing">Add me to your mailing list</label> </div> <input type="submit" name="submit" value="Add to Cart" /> </form>
HTML Form and Email Payment Link Utility
The following form creates HTML that will add a single item to the UBF Checkout shopping cart.
Fill out the required fields below and any additional optional fields, then click the "Generate HTML" button. You can copy and paste the generated HTML code into the pages of your website and copy the email payment link to paste into emails.
Note: This form does not check the validity of the information you enter into its fields so please test your form in the "Check Form/Link in Test Mode" section below after you've generated the HTML.
If you wish to make use of the custom, option and/or option_amount variables to your items, refer to the section titled "Sample HTML Code" which describes how to add options using various HTML form controls or view the section titled "Robust Example" for further information on implementing these variables.
For more information on each of these fields, see the section titled "Adding Individual Items to the Shopping Cart."
If you are already processing credit card payments and want to learn how we can help you process revenue, please contact the expert listed below.
Contact an Expert
Kaity Ross
Program Service Revenue Coordinator
UB Foundation
Phone: 716-645-8753
Email: khross@buffalo.edu