Payment notification not sent to webhook

Question

question

ivan-canales asked Dec 31, '20 David Marginian Deactivated commented Jan 5, '21

Payment notification not sent to webhook

I subscribed to Inventory, Order, Payment events on the sandbox. Notifications are sent to https://hookbin.com/1gePjogJ3Qsj002ykzMW. I am receiving events for the order and item but not for payments.

I am using the REST API endpoint

/v2/merchant/{mId}/pay

with mId BQK6WVCRQ8931 to create the payment for my order 0RZDBTDEG5ET4. I get a notification when creating the order but not for the payment. However I can use

/v3/merchants/{mId}/orders/{orderId}?expand=payments

and I can see the payment listed. But no event on my webhook.

My App ID is FPN8HDJ8Z7BC6.

Payments Webhooks

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community

Answer 1 · 2020-12-31T04:06:48Z

David Marginian Deactivated answered Dec 31, '20 David Marginian Deactivated commented Jan 5, '21

I don't believe our Developer Pay API (which is deprecated) fires webhooks. I think our new ecomm API does (but I am not certain and can't test it now).

4

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ivan-canales commented · Dec 31, 2020 at 02:29 PM

Thanks for the quick reply.

I also tried using

/v3/merchants/mId/orders/orderId/payments

and no webhook event either.

Also does that mean that users using an old POS device or using the old API will not send payment data when they connect? Is there a way to make sure we get the data everytime?

Edit: I tested with the E-Commerce API and it is sending the webhook notification. I still wonder what happens if a merchant has an old POS. Will those send the notification?

0 ·

David Marginian ♦♦ ivan-canales commented · Jan 02, 2021 at 03:09 PM

No, there is nothing you can do if we don't call the webhook. Developer Pay is deprecated and the majority of our integrators are moving over to our new Ecomm APIs, which does fire a payment hook. The /v3/merchants/mId/orders/orderId/payments end point creates a payment record in our system and is used by apps that are taking payments outside of Clover (3rd party tenders) hence we do not fire a payment hook. I am not sure what you mean by "old POS device", payments taken on all Clover POSs should fire a webhook.

0 ·

ivan-canales David Marginian ♦♦ commented · Jan 05, 2021 at 03:07 AM

Do you know a percentage of people using the older APIs? We would like to know what margin of the merchants we will not cover in this cases. Maybe it would be best to implement a workaround for people using older APIs, for example polling.

0 ·

Show more comments

question