Common Troubleshooting: Fast Flow

Q: How does guest checkout work?

A: There is a detailed guide on overall Guest Checkout configuration and another on Selective Guest Checkout. If you are unfamiliar with guest checkout, the following chart can offer a brief overview of how guests will be navigated through checkout depending on the email address used or auto-filled when an attempt is made to check out as a guest:

Q: What happens if I try to log out as a guest and the email associated with my account is already in RTP?

A: If we recognize a guest’s email address, the guest will be given the option to either proceed as a guest or try to log in.

Q: How do I find the transaction for a passholder that checks out with a guest account?

A: The transaction will show both on the newly created guest account and on the passholder’s account.

Q: What happens if the purchaser checked out as a guest but their email is already associated to a different account?

A: A new account is created using the same email address as the primary account with the pass media, but with a TYPE set as “Guest Checkout Customer” and no Auth profile will be set. The transaction will show both on the newly created guest account and on the passholder’s account.

Q: What happens if an established passholder checks out as a guest but has an issue with their purchase? How will we find their transaction?

A: Because the passholder will be assigned access via Fast Flow the transaction will show both on the guest/purchaser’s account (a guest IP Code) as well as on the passholder’s account. See an example of this below:

Flow: Leigh Tester and Jenni Fastflow already have season passes and therefore IP codes in RTP|ONE to which their pass media information is attached (Leigh Tester = IP Code: 1076328 and pass media RFID = 16142028098445933986; Jenni Fastflow = IP Code: 1076514 and pass media RFID = 16147133534689806675). Leigh wants to purchase 2 Fast Pass upgrades without logging into Aspenware Commerce, one for herself and another for her friend Jenni. Leigh goes to the Fast Pass product and enters her RFID (16142028098445933986), after which her pass media is assigned with the Fast Pass upgrade product and she adds the product to her cart. Leigh scans her friend Jenni’s pass (RFID = 16147133534689806675), which assigns the second Fast Pass upgrade product to Jenni’s pass media. Leigh adds to cart and selects to check out as a guest using the email address Leigh.GuestCheckout@mailinator.com.

Here is what the transaction will look like in RTP|ONE:

1. Leigh’s account with the pass media associated with it (Leigh Tester = IP Code: 1076328 and pass media RFID = 16142028098445933986)

   1. an order will show in Order History under IP Code

   2. access will be added to the pass media

2. Jenni’s account with pass media associated with it ( IP Code: 1076514 and pass media RFID = 16147133534689806675)

   1. an order will show on the Order History tab under IP Code

3. The guest account Leigh created so she didn’t have to log in

   1. an order will show on the Order History tab under newly created IP Code Type - Guest Customer

Alternate flow:
Leigh sees that her email address Leigh.Tester@mailinator.com is autocompleted after she selects guest checkout. What happens if Leigh proceeds through guest checkout with the prepopulated email address on file?

• A new guest account is created using the same email address as the primary account with the pass media, but with a TYPE = Guest Checkout Customer.

1. Leigh.Tester@mailinator.com account in RTP|ONE (account with pass media):

2. Leigh.Tester@mailinator.com newly

Q: What happens if Leigh tried to log out as a guest using the same email address as the one she already holds an RTP|ONE account with?

A: First, Leigh will receive a popup box that says “. If Leigh ignores this and continues to check out as a guest she will create a guest account with the same email address as her primary account, but with the Type = Guest Checkout Customer. Leigh’s order will still show under the Guest Checkout Customer, her primary RTP|ONE account (Type = Customer), and her friend Jenni’s account.

Q: Why aren’t my age-range rules aren’t working as expected?

A: Most common resolutions are:

• You do not have the correct age rules set up on the product in RTP|One. The stored procedure for Fast Flow validates age based on the Guest’s age in RTP|One and the age rule on the product.

If after reviewing documentation and Common Troubleshooting Q&A and you still don’t have a solution for the configuration question or issue you are experiencing please write into support@aspenware.com and our support team will be happy to help!