From e9e60bf7385b651e4f7532237783477b5c8f0d11 Mon Sep 17 00:00:00 2001 From: Paul Whelan <5592632+whelanp@users.noreply.github.com> Date: Wed, 31 Jul 2024 09:51:06 +0100 Subject: [PATCH] Update ob_pispimplementationmerch.md removed the section on saying that the SELF_HOSTED_CALLBACK was not on prod which was not true --- pages/prodOpenBanking/ob_pispimplementationmerch.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/pages/prodOpenBanking/ob_pispimplementationmerch.md b/pages/prodOpenBanking/ob_pispimplementationmerch.md index 679472c..ca9234e 100644 --- a/pages/prodOpenBanking/ob_pispimplementationmerch.md +++ b/pages/prodOpenBanking/ob_pispimplementationmerch.md @@ -18,9 +18,6 @@ Your PISP checkout page may be implemented in one of the following ways: |**Self-Hosted**| The user interface is handled by you, the merchant (or partner, acting on behalf of a merchant) for Bank Selection; callback handling is through the Nuapay TPP, you process the merchantPostAuth on your system when the payment flow is completed.| |**Self-Hosted-Callback**| In this mode the user interface is handled by you, the merchant (or partner, acting on behalf of a merchant) and you manage the PSU's experience after interacting with an ASPSP: the Callback bypasses the Nuapay TPP, you manage the callback URL that is required for each ASPSP interaction, upon receiving the callback you send the details back to Nuapay for processing.| -{% include warning.html content="SELF_HOSTED_CALLBACK mode is currently only available in the Nuapay Test environment." %} - - ## What is the Best Approach? Each approach has its advantages and disadvantages - the table below summarises the different implementations