---
title: v2.32 (Summer '25)
slug: payments/v232-summer-25
docTags: 
createdAt: 2025-07-23T14:59:57.162Z
---

:::CtaButton{label="Install v2.32 (Summer '25) Package " externalHref="https://login.salesforce.com/packagingSetupUI/ipLanding.app?apvId=04tJ7000000PjAQIA0" openInNewTab="true"}

:::

::::hint{type="danger"}
:::ExpandableHeading
**Important notice on using guest user access to Unaric Payments**

We’re aware that some clients have been using Guest Users with our package. Guest Users have never been an officially supported use case and whilst certain functionality may have worked previously, this is not guaranteed going forward.

With the Summer 25 release and onwards, our security controls in line with Salesforce best practices may affect existing Guest User configurations. We advise clients to carefully check before upgrading any integration with us which uses Guest Users. Our recommended approach is to use Experience Cloud (community) user licences, which are fully supported, secure, and compatible with protected package components.

Contact support at [support@unaric.com](mailto\:payment-support@unaric.com) if you have any questions or concerns.
:::
::::

## New features: PayTo support

We’re excited to introduce support for **PayTo,** a next-generation payment method enabled by the New Payments Platform (NPP) in Australia and powered by **GoCardless**.

### How it works

**PayTo** allows customers to authorise real-time, pull-based payments directly from their bank accounts, offering improved speed, transparency, and control over recurring or one-off transactions.

Unlike traditional direct debits:

- PayTo mandates are established and managed digitally.
- Provides immediate verification and greater visibility to the customer.

### Activate PayTo

If upgrading from a previous Asperato version, you need to update the **Page Layouts **of these Asperato objects to include PayTo fields**.**

:::::Tabs
::::Tab{title="Asperato Authorisation"}
:::hint{type="warning"}
Except for **Start** **Date **and **End Date**, all fields are mandatory for PayTo mandates.
:::

- **PayTo Description**
- **PayTo Start Date**
- **PayTo End Date**
- **PayTo Maximum Amount Per Payment**
- **PayTo Maximum Number of Payments**
- **PayTo Period**
- **PayTo Purpose Code**
::::

::::Tab{title="Asperato Payment Object"}
:::hint{type="info"}
These fields are required only for standalone payments. Otherwise, values default from Authorisation records.
:::

- **PayTo Description**
- **PayTo Purpose Code**
::::
:::::

You also need to add** PayTo** to **Picklist Value Set**:

1. On **Setup**, navigate to** Objects and Fields > Picklist Value Sets > Payment Route Options.**
2. Click **New**.
3. In the text area, type *PayTo *and click **Save**. You should now see PayTo listed among the available values for **Payment Route Options**.

***

Next, you will need to assign **PayTo **to the *Inbound* **Record Type Picklist** for **Payment Route Selected **and **Payment Route Options **picklist field on **Asperato Payment,** **Asperato Authorisation and Asperato Refund** objects:

1. On Setup, navigate to** Object Manager**.
2. In the list of objects, select **Asperato Payment**.
3. On the **Asperato Payment** object detail page, click **Record Types** in the left-hand menu.
4. Click on the *Inbound* **Record Type** name to access its details and edit it.
5. Scroll down to the **Picklists available for Editing** section and locate the picklist field named **Payment Route Options**. Click the **Edit** link next to it.
6. Select *Payto* under the **Available Values** column and click the** Add** button. This should move it to the **Selected Values** column. Optionally, use the dropdown box below to set a default value.
7. Click **Save**.
8. Return to the *Inbound* **Record Type **page and repeat the process with the **Payment Route Selected **picklist field. Lastly, do the same with the **Asperato Authorisation and Asperato Refund** objects.

### Setup PayTo as payment method

1. Navigate to the **Asperato Setup** tab under your chosen **Merchant Group** and click the **New PSP Connection** button.
2. Set these parameters:
   - **PSP**: *GoCardless.*
   - **Mode**: *PayTo.*
3. Click **Create PSP Connection**.
4. Enter your GoCardless credentials.
5. Create your Payment and/or Authorisation records with PayTo included in the Payment Route Options.

### How to use

1. Create your **Authorisation **or** Payment record** with PayTo in the **Payment Route Options** field.
2. Populate the required **PayTo fields** on the **Authorisation/Payment record**.
3. For Payments with **In Force Authorisations**:
   - You can omit the PayTo Description and Purpose Code on the Payment (they will be inherited).
   - If included manually, they **must match** the attached Authorisation.
4. For **combined Authorisation and Payment**:
   - Set PayTo Description and Purpose Code on **both records**, and they **must match**.
5. Send the customer the **eCommerce URL** — the PayTo option will appear on the PayPage.

### Important notes

- The **PayTo payment flow** redirects to a GoCardless-hosted interface.
- If embedded in your web journey, **align styling** with GoCardless branding guidelines for a seamless user experience.
- PayTo is **not available** via **MOTO mode** due to required customer bank app authentication.
- As PayTo is still being rolled out and adopted, if the bank doesn't support it yet, GoCardless will automatically revert to using the older, established **BECS Direct Debit** system for that payment. If so, the payment details will switch to:
  - **Payment Route Option** = *PayTo*
  - **Payment Route Selected** = *Direct Debit*