Home / CyberPay / PCI Compliance / Q & A

PCI Front-end : Questions and Answers

1.How do we get information on the transactions that did not have a valid return response?

The PCI process will generate an email at the end of each business day letting Student Financial Services know of any transactions that did not successfully complete processing. Student Financial Services will follow-up on behalf of the merchant with any corrective action being required.

2. Can “Credit/Debit Card Number” text be changed for non-PLD merchants?

The Debit label on the screen now only appears for PLD merchants.

3. Can a minimum amount be included as one of the parameters?

No. Current credit card regulations prohibit any minimum amount requirement.

4. Can we avoid displaying the QueryString to the customer?

Once the response has been sent to the merchant, the merchant needs to create intermediate page which will extract the data from the QueryString and store the result. The merchant will then redirect the customer to the display page. The examples on the web site have already been modified to avoid displaying the QueryString information on the response page.

5. Why are we masking the entry of the card number and also requiring a second entry of the number as verification?

This is following a best practice policy recommended by Visa and MasterCard.

6. Can the Online Payment Screen be customized by merchant?

Not at this time. The present generic look supports the view that as an official payment screen for the university, it should be recognized (and trusted) as such by users of every application. So, if a student makes a payment in URSA, they see the same screen as the one they saw when paying housing. Instead of having to trust 40 different merchants one-by-one, they can trust a single entity: UCLA's credit card payment service.

7. Should the screen be timed out in the event a customer walks away from it before completing the transaction?

Yes, a five minute session timeout is currently in place. This can be changed to any time specified.

8. Is there an alternative to the error message screen that attempt to inform a customer that they are not allowed to use the back button to return to the Online Payment screen?

This process will remain in affect because it prevents possible duplicate payments. If a merchant does not want their customer to see this message, they must take the added step of disabling the back button on their end to prevent this action.