Skip to content

Rapyd Bytes: Webhooks

In this video, you’ll learn how to set up a callback URL for your webhooks, and receive webhooks after different actions like creating a payment or creating a refund.

hello and welcome to Rapid bites today we’re going to look at web hooks rapid as an API first company and here rapid bytes will show you how to work with our API to accept hold and disperse funds anywhere using local payment methods be sure to check out our developer community in the link below we’ve got some live events going on some virtual events uh hackathon and you can post anything fintech any questions in the thread below or on community.rapid.

net thanks for watching again we’re going to be walking through web hooks so web hooks are callback messages from Rapid to you the client triggered by internal or external events and so one example would be a synchronous trigger event in which anything created anything at that point in time you’d be sent a web hook with the relevant information for that web hook and so payment created uh customer created disperse created well maybe not Customer because the customer is uh would be an example of he’s inputting uh or that customer is

inputting their information but when you paint um uh create a payment or um basically anything that is at that point in time actually customer uh you know in respect to the action itself customer created would be asynchronous would be um you know something uh that the end user is kind of reliant on their action and so you create a bank transfer payment and then that requires a third party to kind of log in and Trigger that event information cache isn’t a great example of a request is created and then the customer needs to go to the

local point of sale location show their QR code or show their code to input and then they would pay cash and then that’s when kind of the trigger event would happen and so I’m going to head over to just different pages that I have we’re going to do a couple payments today and see how they trigger web hooks events create a payment we’re going to be using the API because it’s a little bit quicker we may use the checkout page once or twice but um here we’re going to capture um payments complete payments as well as

make a refund and so here I’m now in the client portal I’m on the developers tab under a credentials where webbox is and then you’re going to input your URL which will be the Callback URL where you want your web hook sent and so I’m just using uh just a webhook test site webhook.

site a lot of our developers are using the site to test so as well as different sites but this is just kind of for demos and so I have created the URL and so this is going to be sending all the URLs to this site you can take a look at all the webbook events these are all kind of spelled out in our API reference so if you search up some of these and and go to the correlated API calls there should be just a description of these web hooks on our documentation and so I’m going to head over to postman where I’m testing right now uh just some different uh card

payments here we just have a customer ID with about a hundred dollars in British pounds with a Visa card and information so I’m just going to send this in sandbox card payments immediately are closed and so that’s going to send all the WebEx here we’ve got three we’ve got customer payment method created this is the thing that I love about web hooks when you do we do have the API call you know Save card details and safe card details during the checkout process but when a card payment is made a webpack returns with that created and

the card ID and so I love that um that it passes to the client and then of course payment completed and payment succeeded you’ll see the difference between these payment completed would be um basically it shows the the hundred dollars um as well as uh kind of the information and then payment succeeded um is basically the same information but you’ll see as payment fails uh kind of what goes through and what will fail and so I’m going to stay on this and then but head back and so one thing we could do is

bank transfer let’s see if any failure um no that actually wouldn’t go through so let me go capture update all right actually we will do one uh checkout page and so we’ll spend the time uh let me go for that and let me just do a guest and this is um just in the UK and so here I have a bank um and that’s let’s do that test payment here and uh now I like this simulation and so here we’ll just go to an error and so that was a basically a failed

payment uh and so here is a customer created that the test email and name is just test here’s the payment method created here is payment succeeded and so that kind of went through you could see the status is active and so that is kind of information came through um but it does have steps uh and so that that would be kind of that uh synchronous payment now the asynchronous is related to uh when I chose error and used on the information to create an error and so this caused uh the payment failed as here and so we have the web hook ID

uh payment ID uh you know where it would go to uh and so let me now do a refund and so we have the succeeded payment here um with the card payment and I can do a refund here please refund no create refund um there we go create refund I’m gonna paste this is the payment ID for the card payment that we completed and now here is the refund um that we uh it says completed Here and Now refund completed and we have that information I’m gonna do another bank transfer payment but this will be

uh I’ll try and do API and so here’s a bank redirect and then just a success and so here and here is our new uh fancy website uh let me go to the web hook uh payment succeeded for the web hook um for this was the one I just did this Bank redirect I believe in Mexico um and payment completed and so yeah here we have uh just an example of some web hooks being passed after some completed payments some successful payments as well as uh failed payments um and refund and so um yeah web hooks are absolutely important uh to communicate to the

client as well as pass through to the customer and one thing I love it does create payment methods as payments are made with webhock I.T as well as some payment card information that I would save for cards as well as Banks and other payment methods and so yeah we walked through just kind of those steps and how to set it up in client portal if you have any questions Post in the thread below or you can post in community.rapid.

net thanks for watching and have a great day