Description

This page provides information on how to handle a post back from Touchnet UPay. 

A post back is triggered after a payment is fully submitted.  A record of the transaction is created in UPay and UPay will attempt a post back based on per-configured settings.  Failed post backs can be manually triggered by by going to: Touchnet U.Commerce Central > Applications > Marketplace > Test > Sites > (site name) Posting Exceptions.

See: UPay - Payment Form Submission for more information on configuring UPay.

Post Back

UPay submits an HTLM form on post back, this form contains a number of UPay defined values (if data is available) as well as custom parameters (if any have been created).

UPay Provided Parameters:
Parameters Description Field Length Data Type
posting_keyThe Additional Posting Value specified on the
uPay Miscellaneous Settings page. Some campus
web applications use this value to ensure the
identity of the uPay site that is communicating
with the posting URL. (See "General Settings"
on page 480.)		30 alphanumeric
tpg_trans_id A reference number assigned by Payment
Gateway. 		unlimited alphanumeric
session_identifier Unique code that identifies the session. maximum of
48 		alphanumeric
pmt_statusStatus of the transaction as reported by Payment
Gateway. Either "success" or "cancelled". 		unlimited alphanumeric
Parameters Description Field Length Data Type
pmt_amtAmount of the transaction processed by Payment
Gateway. (Maximum value: $99,999.99.)
Forrecurring payments:
During setup, the total amount of all recurring
payments is passed to the posting URL as the
pmt_amt parameter. This is the same parameter
used for each recurring payment. The campus
web application must be able to use the value
passed to the posting URL in the recurring_
payment_type parameter (either "setup" or
"payment") to determine if pmt_amt represents a
total for all recurring payments or the amount for
an individual recurring payment.		8 (including
2 characters
after the
decimal
point)		numeric
pmt_date Date the transaction was processed by Payment
Gateway. (Format: mm/dd/yyyy.) 		unlimited alphanumeric
name_on_acct Name on payment card account or bank account. 50 alphanumeric
acct_addrThe address entered by the customer in uPay.
This parameter is passed only if the uPay site has
been set up to require address verification data.		35 alphanumeric
acct_addr2The second address line entered by the customer
in uPay. This parameter is passed only if the
uPay site has been set up to require address veri
fication data.		35 alphanumeric
acct_cityThe city entered by the customer in uPay. This
parameter is passed only if the uPay site has
been set up to require address verification data.		35 alphanumeric
acct_stateThe state entered by the customer in uPay. This
parameter is passed only if the uPay site has
been set up to require address verification data.		2 alphanumeric
acct_zipThe zip code entered by the customer in uPay.
This parameter is passed only if the uPay site has
been set up to require address verification data.		30 alphanumeric
Parameters Description Field Length Data Type
acct_countryThe country selected by the customer.
The two-letter code represents the English
language country codes approved by the
International Organization for Standardization.
This list can be found at
www.iso.org/iso/country_codes.htm.
This parameter is passed only if the uPay site has
been set up to require address verification data.		2 alphabetic
acct_email_
address		The customer can be required to enter an e-mail
address or this field can be optional. 		50 alphanumeric
acct_phone_day This phone field is an optional entry field. 20 alphanumeric
acct_phone_night This phone field is an optional entry field. 20 alphanumeric
acct_phone_
mobile 		This phone field is an optional entry field. 20 alphanumeric
EXT_TRANS_IDAn ID generated/assigned by your campus web
application. This value is posted only if it was
initially passed to uPay from the campus web
application.		250 alphanumeric
UPAY_SITE_IDA unique ID that identifies the uPay site.
Assigned by Marketplace when the uPay site
was created.		unlimited numeric
sys_tracking_idAn internal Marketplace identifier (also known
as the order ID) that is displayed to the customer
on the uPay receipt page.		unlimited numeric
recurring_
payment_type		This value is only specified if the payment is a
recurring payment. Two values are possible:
"setup" (for the initial setup of recurring
payments) and "payment" (for a single recurring
payment).
During setup, the total amount of all scheduled
payments is passed to the posting URL as the
pmt_amt parameter. This is the same parameter
used for each recurring payment. The campus
web application must be able to use the value
passed to the posting URL in the recurring_
payment_type parameter (either "setup" or
"payment") to determine if pmt_amt represents a
total for all recurring payments or the amount for
an individual recurring payment.		unlimited alphanumeric
Parameters Description Field Length Data Type
recurring_setup_
number_of_
payments		This value is specified for uPay-driven recurring
payments and indicates the total number of
payments.		unlimited numeric
recurring_setup_
start_date		This value is specified for uPay-driven recurring
payments and indicates the date of the first
scheduled payment. (Format: mm/dd/yyyy.)		10 alphanumeric
recurring_setup_
end_date		This value is specified for uPay-driven recurring
payments and indicates the date when the
recurring payments will end. If this date does
not coincide with a scheduled payment date (as
determined by the selected frequency and start
date), the final payment will be the last
regularly scheduled payment date before the
"recurring_setup_end_date". (Format:
mm/dd/yyyy.)		10 alphanumeric
recurring_setup_
frequency		This numerical value is specified for uPay-driven
recurring payments and indicates the frequency
of payments: 4=weekly, 1=monthly, 2=bi
monthly, 5=quarterly, 6=semi-annually, and
7=annually.		unlimited numeric

Post Back Form Example

Below is an example of what the HTML post back form sent by UPay to the post back URL may look like.  Note this post back example contains both UPay provided parameters and custom parameters.

<form name ="frm_upay" method="POST"action='https://<url>/PostBack.aspx'>
  <input type="hidden" name='sys_tracking_id' Value='101' />
  <input type="hidden" name='posting_key' Value='abc123' />
  <input type="hidden" name='tpg_trans_id' Value='20990101012345' />
  <input type="hidden" name='UPAY_SITE_ID' Value='987' />
  <input type="hidden" name='name_on_acct' Value='Butch Cougar' />
  <input type="hidden" name='WSU_USER_ID' Value='0123456789' />
  <input type="hidden" name='pmt_amt' Value='25.00' />
  <input type="hidden" name='WSU_ACAD_CAREER' Value='UGRAD' />
  <input type="hidden" name='BILL_EMAIL_ADDRESS' Value='butchc@wsu.edu' />
</form>

Important Provided Parameters

Which parameters are used will depend on your needs, however there are several parameters that are highly recommended that you include in your application.

Parameters for tracking payments:
Parameter NameDescriptionExampleInfo
tpg_trans_idPayment Gateway Reference Number20220412000004

This is a unique transaction ID.  This will be needed to help find transactions for refunds etc. 
This is the primary ID used internally by myWSU (PeopleSoft) for payment reference to UPay.  Your application may be required to send this information to myWSU

sys_tracking_idSystem Tracking ID101An internal, sequential, Marketplace identifier (also known as the order ID) that is displayed to the customer on the uPay receipt page.  This is also the ID primarily shown when looking at transactions in the U Commerce Central site


Depending on how your receipt for customers is configured, customers may receive a receipt that looks similar to the below image.  Note the System Tracking ID and the Payment Gateway Reference Number.