Register, rename, remove, and use a payment device

How to use

Open Registered Devices, use the device registration code and a recognizable nickname, and verify registration succeeds. Use the edit action to rename a device or the authorized removal action to remove it. For a supported staff-assisted payment, select the intended device and follow its prompts.

Rules

The duplicate-serial error instructs the user to generate a new pairing code and re-register. Device payment handling separates sending the payment to a device, checking status, and attempting cancellation of an in-progress action.

Troubleshooting

A successful send-to-device result is not proof the payment completed. Inspect the returned payment/device status. Canceling an in-progress device action is not a refund of an already completed gift. Check the gift record before retrying an uncertain transaction.

Availability and limitations

Use the approved documentation for your device model for pairing menus and physical connection requirements.

GC Connect access versus MOTO access

The administrator Notifications table exposes GC Connect Access when the school has the relevant device feature. An authorized administrator enables it on the intended fundraising administrator record; that update generates the device access key and notification. Connect login checks that fundraising record, enabled terminal access and a valid active key. Removing the checkbox expires its device keys.

MOTO is separate: listing/registering/editing/removing registered devices requires Manage Financial School Settings. Using a MOTO device for payment accepts that permission or GC GO MOTO. Therefore Connect-only access is not the same as granting MOTO or financial settings management. Confirm the product/device and intended setup versus payment duties before granting access.

Still receiving gift alerts with administrator notifications unchecked

The recipient calculation combines the school's donation-notification administrator list with the individual project/form's notification recipients. Turning off the school-level checkbox does not remove a separate form-specific entry. Identify the campaign/form that received the gift, including the Campaign Backup Form for a general-gift alert, and review its notification recipients with an authorized administrator.

Where the Giving Form Notifications screen is available, uncheck the relevant recipient and save. Verify the intended scope: removing one form's recipient does not unsubscribe the person from every notification type. Support should inspect any remaining recipient source rather than treating this as an Outreach marketing unsubscribe.

Include payment type in a gift-notification template

The contribution merge map supports $PAYMENT_TYPE$ in custom campaign/general gift-notification templates that use that map. Use that exact token and test the actual notification template. Its value uses the recorded payment-method subtype when available and otherwise falls back to the stored card/payment type. It is not a guarantee that every gift has a populated or equally detailed label, and it does not indicate settlement or deposit status.

Use a registered MOTO device from another computer

The MOTO registration stores the device for the school and its processor terminal location; it is not registered separately to each computer. On another computer, sign in with the appropriate school access and select the school's registered device in the giving-form payment flow. The last selected device is remembered locally by the browser, so a new browser/computer may require selecting it again. This describes the server-connected MOTO flow, not every card reader or GC Connect hardware pairing method.

MOTO availability requires a giving form, school MOTO access and payment permission. Device management requires financial school-settings permission; payment access can also come from the dedicated MOTO permission. A generic administrator title alone is not the exact permission test. If the device is unavailable, verify school, permissions and device status instead of registering it repeatedly for each laptop.