Skip to content
English
Customer portal Sign in
Go to www.readyeducation.com
  • There are no suggestions because the search field is empty.

Payment Gateways

CampusGroups allows you to integrate with the following Payment Gateways.

CampusGroups allows you to integrate with the following Payment Gateways.

Please note that certain payment gateway integrations can be configured by the Integrations Team, while other integrations require engineering effort. Turnaround times can vary for each payment gateway.

PayPal

image-20240425-211618

Integration Requirements

  • PayPal Account (email address) (Can use one per group)

Touchnet

image-20240425-211645

Integration Requirements

  • TLink URL
  • UPay URL
  • UPay ID

Braintree

image-20240425-211840

Integration Requirements

  • Merchant ID
  • Account Merchant ID (Can use one per group if preferred)
  • Public Key
  • Private Key

CyberSource

image-20240425-211927

Integration Requirements

We use Hosted Checkout (not Checkout API - We are not calling any Cybersource API internally to make the payment). We use REST - Shared Secret (not REST-Certificate).

  • Key (i.e Profile ID)
  • Access Key (example is: b95feda023ab30ac8e3472dd6bfdabf4) - 32 characters
  • Secret Key (it should contains 256 character) to create the signature
  • Payment Tokenization does not need to be enabled since we are redirecting the user to the Cybersource gateway
  • The POST notifications must be sent to https://[tenantID].campusgroups.com/payment_confirmation
  • The Redirect After Checkout URL to be configured on client's end would be https://[tenantID].campusgroups.com/rsvp_paypal_confirm.

Authorize.NET

image-20240425-211951

Integration Requirements

  • API Login ID (available under API Credentials & Keys)
  • Signature Key (available under API Credentials & Keys)
  • Under Response/Receipt URLs add "https://[your_cg_url]/payment_confirmation" as the Default Relay Response URL (where [your_cg_url] is your CampusGroups url, eg http://myuni.campusgroups.com or campusgroups.university.edu)

Stripe

image-20240425-212109

Integration Requirements

Please read how to Configure Stripe as your Payment Gateway.

SecurePay

image-20240425-212236

Integration Requirements

  • Merchant Code (at least one required, may use one per group if preferred)
  • Client ID
  • Client Secret

CASHNet (Transact)

image-20240425-212330

Integration Requirements

Please read how to Configure CASHNet (Transact) as your Payment Gateway.

PayZen

PayZen_Logo

Integration Requirements

We do not have a standard integration with PayZen. Reach out to the Integrations Team at integrations@readyeducation.com.

Nelnet

Nelnet

Integration Requirements

CampusGroups supports two payment solutions from Nelnet:

  • Nelnet Commerce Manager
  • Nelnet Checkout

Below are the integration requirements for each solution.

Nelnet Commerce Manager

  • Commerce manager url (which should like quikpayasp.com or uatquikpayasp.com - for testing)
  • OrderType (only one is supported so typically campuses use something like "CampusGroups")
  • If a Redirect URL is required for creating the ordertype you may use "https://[school].campusgroups.com/payment_confirmation" with the following redirect parameters: transactionStatus, transactionId, orderNumber.
  • Secret Key for hashing (the Hash algorithm is SHA256)

Nelnet Checkout

  • Tenant ID
  • Order Definition ID

Xetta

logo-xetta

For Xetta our integrations team will need the following:

  • Base URL The base Xetta URL for the school (e.g. https://{xettaURI}/tranadd)
  • Transaction Type The transaction code we will be passing the detail to Xetta (e.g. T0011)
  • Secret Hash secret to be shared with us to query Xetta (e.g. 12345)

These should be provided to the school by Xetta during their implementation.