Custom payment links

Questions
1

Hello,

I have created a custom payment link with an API, connecting a POS software to a wallet. It gives a redirect by creating payment intent from the inputs and gives a redirect web link. How do I get Make to open a browser with the link on a specific devise so that customers can put their details in and make their payment? Is this possible?

image
image819×317 37.5 KB

3

Try a Webhook response module with a 301 or 302 redirect to the redirect_url.

Hope this helps! If you are still having trouble, please provide more details.

— @samliew

4

I guess to add to this, create a Header with a key of “Location” and the value is the URL.

It doesn’t get passed in the response body.

5

Hi have done it and it did not work. Browser did not open for me to see the form for entry.

image
image1189×543 57.7 KB

6

How is your webhook called? Is your form redirecting users to your webhook URL? Can you provide a link to your page that calls your webhook?

If not, the calling script on the web page needs to read the response from your scenario, and perform the redirect.

Hope this helps! If you are still having trouble, please provide more details.

— @samliew

7

I don’t really understand what you are asking, however, let me give further information.

  1. The custom Webhook is triggered from a POS software, which registered the sale
  2. I need collect payment. I am using something similar to Stripe to create a payment intent
  3. The output of the API gives a redirect URL for the person to enter their details for sale to complete.

Below is a copy of the “Headers” output: I am wondering if something there is preventing it from opening a browser with the URL given

image
image580×600 26.9 KB

8

Exactly this.

  1. The User clicks on a button on the website (frontend) to send/submit data to the POS software (backend).
  1. The POS software on the webserver (backend) sends a request to the Make Webhook.
  2. Your scenario replies using a Webhook Response module.
  1. The POS software (backend) reads the response from the Make Webhook, and extracts the URL.
  2. The POS software (backend) respond with the redirect/payment URL, to the buyer’s web browser (frontend) to redirect the User.

We can’t help with the last two steps, as the form wasn’t submitted directly from the User’s web browser to the Make scenario.

Hence, the Make scenario cannot redirect the user’s web browser (frontend), as the Webhook response returned the data to the caller (backend).

To proceed, you will need to hire a web developer to add additional code on your POS software to “tell” the user’s web browser to redirect the user to the received URL. Alternatively, check if your POS software can already do this for you.

Hope this helps! If you are still having trouble, please provide more details.

— @samliew

9
  1. I used a HTTP POST request using https://api-v2.ziina.com/api/payment_intent . This is totally different from the POS software. It gives a payment link when I run the scenario. This payment link is what a customer will use to put in their credit card details.

If it is not able to work as I would like it to. Can someone suggest an app that is in Make.com where I can send the URL to, as a manual work around. I can then have the app open to select the URL manually.

10

Yes, this is step 2a (in your scenario), before your scenario returns the data (url) using a Webhook Response module.

Here are the steps again, with the previous step 3 now shown as “2b”

  1. The User clicks on a button on the website (frontend) to send/submit data to the POS software (backend).
  1. (Trigger Scenario) The POS software on the webserver (backend) sends a request to the Make Webhook.
    2a. (Inside Scenario) HTTP POST request to https://api-v2.ziina.com/api/payment_intent.
    2b. (End of Scenario) Webhook Response module replies to the calling request (POS software), with the URL from (2a).
  1. The POS software (backend) reads the response from the Make Webhook, and extracts the URL.
  2. The POS software (backend) respond with the redirect/payment URL, to the buyer’s web browser (frontend) to redirect the User.

If you are still having trouble, please provide more details.

— @samliew

11

What about the manual work around? The POS is not owned by me. I am just a user.

12

Without knowledge about the POS system, you will need to contact the POS software supplier for more guidance on how to redirect the user using the response from the Webhook.

If you are still having trouble, please provide more details.

— @samliew