Hi, I have an embed on Wix for checkout, it works fine for a normal plans. However, when I add a trial period to the cycle I get this message: There was a problem processing your payment Please try again later or using a different card This is using the sandbox test card provided.
Posted by Paul 7 days ago
Hi, I am working with the API to get custom fields. I have 3 custom fields but it's only returning the one of them. I am using Zapier Custom Request and everything up to this point has worked fine, but for some reason it's only returning 1 custom field and not the other 2. Any suggestions? Thanks in advance, Shawn
Posted by Shawn about a month ago
Hi there :) i am new to Billby and love it. The first thing i discovered, which isn't very convenient for the customer, is the small viewport of the iframe (either checkout or self service) I know that 3rd party iframes can't be modified, but is there any option for this available from your side? Something i stumbled on while searching was this: https://support.billsby.com/discuss/5f66844c36d5980030c04910 Mark mentions there that a solution is coming in a few weeks Thanks in advance :) Dimi
Posted by DIMITRIOS 3 months ago
When I use any "core" API I am successful (example): https://public.billsby.com/api/v1/rest/core/... When I try to use the api from "billing" (as shown here) https://public.billsby.com/api/v1/rest/billing/... I get the CORS error (shown below) : Access to fetch at 'https://public.billsby.com/api/v1/rest/billing/[companyName]/subscriptions/[subscriptionId]/addons' from origin 'http://localhost:65508' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. I used the APIs "Try It" function, which works on the billsby site. However, copying it directly into my scripting area, still produces the same error shown above. Please advise.
Posted by ConradBI 4 months ago
Hi there, We want to reward certain behaviour on our platform by giving the user their subscription for free for a X number of days. I thought we could simply update the nextBillingDate, but I can't find a PUT method to do so with the API. If you user has a subscription for $5 a month, how can I give them 3 days for free using the API? Thank you! - Sander
Posted by Sander 4 months ago
Hi there - we would like our cancellation policy to be to not issue a refund, but maintain access for the duration of the current billing cycle. The only issue with this is the wording on the cancellation self service page which at the top says 'You are about to cancel the following plan and lose XXX of paid usage.' Is there any way to customise this text that I have missed to remove the 'and lose XXX of paid usage'? Thanks
Posted by Douglas 6 months ago
I am trying to develop using the webhooks, however when I either use the test button or perform actions on the embedded checkout I only get an empty object in the body of the request. Has anyone else experienced this issue? All hooks seem to fire and arrive OK, just no data! Thanks for any help or advice
Posted by Douglas 8 months ago
I'm having a hard time understanding how to charge my clients a different price after their first month of service. Basically I just want to charge my clients a set up fee for the first month, then a different monthly recurring fee after, how do I do this? Also I'm transferring from Chargebee to you guys and I'm trying to figure out the best way to transfer all my clients data and subscriptions easy, fast and safe. Any advice?
Posted by Michael 8 months ago
On my dev server (localhost:3000) and on my production site (hosted by Vercel) I am getting either errors or a warning when using the href tag provided (aka the embed code). On my dev server, I'm getting these errors: Access to XMLHttpRequest at 'https://checkoutlib.billsby.com/config/config.json' from origin 'http://localhost:3000' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header has a value 'https://localhost:3000' that is not equal to the supplied origin. GET https://checkoutlib.billsby.com/config/config.json net::ERR_FAILED Uncaught DOMException: Failed to execute 'send' on 'XMLHttpRequest' On my live website, I'm getting this warning: [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. In both instances, clicking on the link does nothing else (doesn't bring up checkout, etc).
Posted by William 8 months ago