Skip to main content

Trouble Viewing Scholarship Payment Remittance Details

Steps to help your University resolve issues with viewing scholarship payment remittance details

Backpack sends scholarship remittance emails to universities when a partnered Scholarship Provider makes a scholarship payment. These emails include a link to view the payment and scholarship details.

If you cannot see the button in the email, or the remittance details page does not load, try the steps below.

What the remittance email should look like?

If the button is missing in the email

Some email systems block buttons, images, or links for security reasons.

Try the following:

  1. Look for and click the blue text link below where the button should be.

  2. Hover over the whitespace where the button should be - attempt to click.

  3. Click “Unable to view the button above? Click here.” if shown.

  4. Open the email in a different browser or email client.

  5. Check whether your email system has blocked external images or links.

  6. Ask your IT team whether links from Backpack are being filtered or rewritten.

If the remittance page does not load

If you can see the button and /or click the link but the page does not open, it may be due to your university’s network or security settings.

Try the following:

  1. Copy and paste the link directly into your browser.

  2. Try a different browser, such as Chrome, Edge, or Safari.

  3. Try opening the link in a private or incognito window.

  4. Try from a different network, such as a mobile hotspot.

  5. Ask your IT team to allow access to Backpack and all it's subdomains, including:

    • backpackpay.com

    • backpack529.com

Do you have instructions I can share with my IT team?

Some universities use email security tools that scan, rewrite, or block links before they reach the recipient. If the remittance link is being blocked, your IT team may need to allow Backpack links so payment details can be accessed.

You can share this explanation with your IT team:

Backpack sends secure scholarship remittance links so our university can view payment details, student details, award information, and download the remittance CSV. Please allow links from Backpack domains so these remittance pages can be accessed.

Please note that Backpack uses two domains: email is sent from backpackpay.com, and the remittance page is hosted on backpack529.com. Both must be permitted.

  • Allowlist both Backpack domains and all their subdomains on your web proxy, firewall, and content or DNS filter:

    • backpack529.com and all subdomains (the remittance page is served here, for example scholarships.dashboard.backpack529.com)

    • backpackpay.com and all subdomains

    • Traffic is standard HTTPS over port 443.

  • Check your email link protection. If you use Microsoft Defender for Office 365 (Safe Links), Proofpoint URL Defense, Mimecast, Cisco, or Barracuda, the link is likely rewritten and scanned before it opens. Some scanners pre-visit the link, which can break it for the recipient. Please add both Backpack domains to your trusted or excluded list so the original link opens normally.

  • The page is a standard web application that needs JavaScript and a current browser. Internet Explorer and other outdated browsers are not supported.

  • No sign-in is required to view the page.

If the page still loads blank after allowlisting both domains, email scholarships@backpackpay.com and we will provide the specific technical details your filtering system needs.

Still need help?

Email us at scholarships@backpackpay.com and include the Payment ID shown near the top of your email. We can:

  • Re-send the remittance link.

  • For immediate resolution and as a one-time workaround, we can send you the remittance details as a PDF or CSV you can open without the web page.

  • Confirm the payment amount, student, and expected arrival date.

Note: Your payment is not affected by any of these display issues. Funds are sent separately and typically appear within 1 to 3 business days of receiving the email.

Did this answer your question?