Implementation

Can Payit™ be integrated into an app?

If you own the app infrastructure, you can easily add Payit to your app which will redirect to our site to complete the payment; your customer will then be redirected back to your app once the payment is complete.

If you would like the customer to stay in your app for longer, you could integrate the browser into your app using Web view/In app browser. This will mean our webpage renders within your app.

Note – to authorise the payment via the banking app or online banking, you will need to relinquish control after the bank is selected for that redirect to happen. You may want to add browser navigation to your app so that your customers can view the terms easily before continuing with the journey.

If you would like to encourage your customers to use Payit via an app rather than a web browser, you may utilise Web view/In app browser which will mean our webpage renders within your app. However, for an improved customer experience you may want to adopt our direct embedded integration of Payit. This will prevent the need for re-directs to Payit hosted pages and enable you to control pages such as the bank selection and payment confirmation screens, allowing you more control over the customer interface of such pages. Although this may enable a more desirable customer experience for some merchants, it will require more development by your technology teams when integrating with Payit.

What technical resource is required to integrate?

The technical integration is relatively straightforward, and we have a readily accessible sandbox which you can use to safely develop and test in. For a standard eCommerce integration, we estimate that technical integration work and testing should take up to 20 weeks. We also have a Payit Plug-in that is available for both WooCommerce WordPress and Adobe ecommerce users, where merchants can include Payit in their shopping cart payment options, simplifying the integration process. More information on these can be found by contacting [email protected]

Can you set up Collecting Payments online and Collecting Payments by Request on the same Payit brand?

No, you will need to complete separate brand onboarding forms and a separate brand and brand ID will be created. This means the reconciliation file will show separate brands for each method. If the bill is broken down at brand level, it will show the different methods separately.

The backend process for receiving payment status notifications will also differ. For Collecting Payments, you must provide a Merchant API endpoint URL for Payit to send the payment status to. With Collecting Payments by Request, your API endpoint URL must be the PLG URL so that PLG can receive the payment status update. The merchant will also receive notification of the payment status as they will be required to provide a URL for this within the individual payment request.

How are pay-outs created?

Payouts can be created within our Bankline proposition, which means no technical work is required on your side.

This is powered through a templated email, which is sent to the payee through the details you provided, and they simply click the link to claim their funds.

Alternatively, we have other options available which would allow you to embed Payit within your existing business systems through our API solution, which would allow you to deliver the claim link through your method of choice – be that through our email, your email, or potentially your own SMS, app or website – creating a fantastic experience for your payees.

What’s the implementation support?

Customers are provided with a dedicated implementation manager to support onboarding.

However, customers would need to procure their own IT resources to undertake any integration or development to their own system if they wish to use the API.

What happens if a customer does not claim their funds?

Customers have a maximum number of 30 days to claim their funds before the link becomes inactive.

You can reduce the number of days if you wish, however you cannot extend it beyond the 30-day maximum.