Share
Report
20I should preface my question by acknowledging that I'm very new to working with HTTP requests in general. So apologies if this is a stupid or non-sensical question.
I'm using the "When a HTTP request is received" connector as a Callback URL to receive some JSON from a payment gateway service. Basically when a customer makes payment via the Gateway, some result parameters are sent to the Callback URL.
The gateway providers have said that the auto generated HTTP POST URL I've supplied is too long at 234 characters.
I'm wondering if there is any risk in using Bitly to shorten the POST URL? I've tested it using an online API testing tool and my flow receives the JSON just fine.
I should note that the result parameters being passed to this URL, include details about the payment, however card numbers are masked (first 6 and last 3 digits) and no other personal information is included as the process uses our internal customer number as the payment reference, rather than name, address, email, phone, etc.
Are there any risks/implications associated with doing this in the long term?
All responses (
Answers (
