Transact (formerly known as CASHNet)
- 24 Oct 2025
- 2 minute read
- Print
- DarkLight
- PDF
Transact (formerly known as CASHNet)
- Updated 24 Oct 2025
- 2 minute read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Note: CASHNet is now known as Transact
You may see the company and product referred to by either name.
To establish an integration with Transact (formerly known as CASHNet), you must:
Set up the required configurations on the Transact side. Work with your Transact representative for assistance.
Open a Support Ticket with Technolutions to set up the configuration on our side. Note: It’s not currently possible to set up a payment integration with Transact without submitting a Support Desk ticket.
Step 1: Configure Transact
In Transact:
Under HTTP notifications, use the Name Value Format (POST) option to send a silent postback to https://YOUR.SLATE.DOMAIN.EDU/apply/payment?cmd=cashnet with the ref1value, tx (Transact/CASHNet transaction ID), and amount.
Be sure to replace “YOUR.SLATE.DOMAIN.EDU” with your actual Slate domain.
For example, if you log in to Slate via apply.slateuniversity.edu/manage, your silent postback URL will be https://apply.slateuniversity.edu/apply/payment?cmd=cashnet.
Configure Transact to redirect the payer in the browser, when finished, to https://YOUR.SLATE.DOMAIN.edu/apply/status using a GET request.
Set up ref code 1 as
SLATETX, which will contain our Slate integration/transaction data.Set up at least one item code that is associated with a “payment_account” prompt and is not a convenience fee. If you are setting up a convenience fee, see how to configure a convenience fee below.
🔔 Important!
The Transact/CASHNet ref1 value must be SLATETX. Slate uses this reftype to transmit integration/transaction data.
Step 2: Create a Support ticket with Technolutions
To create a Support ticket:
Navigate to Database.
Under Support Resources, select Discover Slate.
Under Level III: Advanced Exploration, select Support Desk.
In the Support Ticket, provide the following information:
The posting URL for Production and Test
The item code(s) that should be passed. If providing multiple item codes, provide a description of the Slate logic to determine which item code to pass. For example, “Pass item code A when the round key is UG, and pass item code B when the round key is GR.”
If you would optionally like to send additional data to Transact, please provide:
The ref code (for example, “NAME_G”) and number (for example, “ref2”).
The Slate field that should be passed to each ref code.
If you are charging a convenience fee via Transact, let us know in the ticket and confirm that you have followed the directions below.
How to configure a convenience fee
If you are planning to charge a convenience fee in Transact, additional configuration is required to prevent a mismatch in the payment amount displayed in Slate and Transact.
You will need to add a new item code (only in Transact) with a zero dollar value (non-editable); that second item code will act as a placeholder. Slate will pass in itemCode1 and amount1 (the actual fee amount due); in addition we will pass in itemCode2 (e.g. Slate) with amount $0. This will cause your convenience fee to be placed as an itemCode3/amount3, which is a field/value that Slate will ignore. This will ensure that the value of the resulting payment received activity in Slate matches your payment due amount exactly.
Was this article helpful?
