Billing & Payment Ideas

TrixabelleCP · ‎02-11-2020

When someone reverses an invoice this is a one-way action that's impossible to undo. This in turn means we can't unpost > cancel > delete the invoice, which in turn means we can't delete the associated order. This is something that's occassionally caused us a real headache as we then need to work out how to do a corrective order to try and undo the effects of the previous one (which is possible in some cases but not in all including undoing a renewal). It would therefore be very helpful if it was possible to undo an invoice reversal.

jdande · ‎04-12-2019

The Invoice merge field, Payment.CreditCardNumberMasked was deprecated, and now there is no way to make the last four digits of the credit card used to pay the due amount of an invoice visible - please make this possible once more.

KrisGalata · ‎01-28-2020

Modern browsers have a feature to remember credit cards. Our Sales team is using hosted payment pages to setup information for our customers . We would like to prevent credit card save in browser because it would remember cards of our customers and it is PCI DSS issue for us. Setting the ‘autocomplete’ value on the html form and input tag should turn off this feature for browser. So our suggestion is to add an ability to specify value for form and input autocomplete attribute via Hosted Payment Page setup screen or javascript configuration using Z-pages More information - https://www.w3schools.com/howto/howto_html_autocomplete_off.asp Similar request - https://community.zuora.com/t5/Billing-Payment-Ideas/HPM-Suggestion-autocomplete-quot-off-quot/idi-p/4574

TrixabelleCP · ‎02-04-2020

Customer have 14 days to change their mind on a purchase and therefore a renewal may need to be rolled back / undone (this happens in our business from time to time). Out the box the only way to achieve this is to delete the renewal order. This has several downsides. The first and most important is that it's not tracked in any way so we can't report on it. Secondly, if we accidentally reverses the invoice for the renawal, the invoice can't be deleted and therefore you can't delete the order either (we've seen this a few times). We can't cancel the subscription because we sell perpeptual licenses for some of our products and cancelling a subscription cancels the license. Also the customer still may come back and purchase support at a future date. Our current workaround is to create a "corrective order" and assuming the renewal term ran from 1st Jan 2020 to 31st Dec 2020, then you can change the current term so it's only 1 day long (eg 1st Jan 2020 to 2nd Jan 2020) and then write off the resultant invoice. However ideally Zuora would provide a way to either: - delete an order (but make that an audited/traceable action) or - set the dates back to what they were before the renewal was done

akarattu

Current behaviour: When doing hosted payment page 2.0 advanced implementation, which is inline style with external button the callback method in z.render method is not called on success. instead the payment form is replaced with a callback page. What is issue with current behavior? Replacing the credit card form with callback page on submit is a very odd behavior. Also when user gets an error he cannot edit the already entered data becasue the form needs a rerender and data is not persisted. Proposed solution: When user submits form using external button, if payment method is created the callback method provided as second param of z.render/ z.renderWithErrorHandler method should be called instead of rendering the callback page inside the iframe similar to how internal submit button works.

akarattu

This is a UI improvent for Hosted payment page 2.0 with inline style and external button. Current behaviour : Credit card fields are validated on submiting the payment form. Then user can enter correct values. But the errors don't go away. On next submit fields gets validated again and submit action works if all forms are valid. Proposed behaviour: Make the basic field validations happen when a user leaves an input by chnaging focus to next field by pressing tab or clicking somewhere else. This will also clear the errors immediately if field is valid. This can be a configurable option in the parameters of z.render method.

akarattu

This is an improvement to expiry month dropdwon in hosted payment page 2.0 Current behavior: User is able to select a passed. For example i can select 01 (Jan) as card expiry month when current month is Feb(02). Proposed behavior: There is no point in adding an expired credit card for payment. So probably the months befoer current month should be disabled/hidden.

klee34 · ‎02-25-2020

I think it would be very helpful to be able to forecast future billings/invoices. I understand that we are able to see the future invoices generated by a Billing Run, but I am speaking more of a report that will include the Preview Invoices as seen under Subscription Preview. Thanks, Kevin

Jbakker · ‎02-11-2020

It would be nice to be able to specifically select a due date for invoices. We are a due upon receipt company however we charge monthly rent that we bill ahead of time due on the first. Our invoice date is then the first so our due date can be the first instead of the invoice date being today and the due date being the first. We went the rest of our invoices to be due upon receipt however.

a_sichwart · ‎02-11-2020

We create the billing document pdf ourselves outside from Zuora. When we attach our pdf to the invoice object in Zuora, we want it to be the only and most recent pdf attached to the invoice. Thus, automated pdf generation by Zuora needs to be disabled. Because it would only create pdf files we do not want and it would fill up the activity history.

christang · ‎02-06-2020

Within a Lockbox upload, it currently shows the Reference ID, Invoice Number, Payment Amount, Payment Date, Status and Details. If Status = "Processed", there should also be a column showing the Payment Number that was generated.

ConnorRoebuck · ‎12-04-2019

A feature in addition to sending pdf invoices in emails to customers would be to send additional pdf's in the same email. For example, we are in the process of changing platforms for one of our services, and a great way to inform our customers would be to send a pdf document alongside invoices explaining the circumstance and any FAQ's. I understand the invoice template can be amended to include additional information, but a seperate pdf attachment would allow quicker customization. and different updates without cluttering the invoice.

rlacorne · ‎02-04-2020

I think this should be fixed as console errors lower consumer trust. It is unclear to me what exactly causes this error, so I'll gladly take under consideration steps I could do on my end to fix it, if possible. Note that the same error also appears on Preview Hosted Payment Method Page.

rlacorne · ‎02-04-2020

For accessibility purpose, it is critical that iframes are titled or labeled. While it is possible to bind a mutation observer on a webpage to detect when the iframe has loaded and then set an attribute, this method requires additional process and is not optimal. See : https://dequeuniversity.com/tips/provide-iframe-titles for information.

tamaratamarara · ‎01-31-2020

Curerntly the Bill Run and Billing Preview are not taking into the account upcoming suspension. It would be nice if it did. E.g: the monthly subscription BCD =10. The person already paid from 1/10 till 2/10. Suspension is scheduled to be effective on 2/15. Resume is scheduled to be effective on 3/15. If I'll create invoice or request a Billing Preview with the target date before the suspension begin date, the customer will be charged for the whole month and getting a credit memo in the next invoice. In that example this customers next payment will occur on 2/10. With that target date the customer will be charged from 2/10 till 3/9 when he will be suspended from 2/15-3/15. it's be nice to pass the target of 2/10 and have customer to be prorated (2/10-2/15) because these are the only dates his subscription will be active during that month.

rlacorne · ‎01-31-2020

As of right now, the iframe only changes its height when first rendered and on input error validation. This behavior should also be called when the user triggers a resize event of the browser (zoom or manual resize). CSS alone is not enough to make an iframe responsive, and therefore there should be a way for the developpers who integrate the iframe to either receive a message about the measured height of the iframe's dom, or that the iframe handles it's own measuring and resizing by itself. While it is understandable that the will not allow cross domain communication for security purpose, it should use its already eaxisting sizing function to make itself responsive.

rlacorne · ‎01-31-2020

The select elements (country, state, and especially the expiration fieldset) are currently not properly labeled and accessible to the cognitively or visually impaired. This is a major issue for accessibility and drastically lowers the trust between user and merchant.

rlacorne · ‎01-31-2020

It is a very common pattern nowadays to have multiple step forms, with the possibility to navigate backwards and forwards between steps. It would be a very useful inclusion to add an optional button before the already implemented submit button, in which the developper could provide custom functions, in the same way we can customize the callback function at the moment. This would allow the iframe to fit more naturally within many more web environments and ux flows.

rlacorne · ‎01-31-2020

Right now, the submit button within hpm2's iframe is an Anchor tag. (<a>) This is a very bad pattern for accessibility, as visually impaired users will read this as being a link, while for all intents and purposes, it only manages javascript functions. It should therefore be a <button> to make sure the user understands what they are activating and cognitively understand the expected behavior.

nmartelliere · ‎11-12-2019

Hi, Slimpay payment gateway for bank transfer payment type is available in Zuora to create SEPA mandates (https://www.europeanpaymentscouncil.eu/) however some features lack as the mandate revocation function. In Zuora, if electronic payment method is changed to Closed status there is no automatism leading to the revocation of the mandate in the Slimpay back office. Users must manually revoke the mandate in the Slimpay back office. The integration of the Slimpay mandate revocation functionality is one of the important elements for the consistency of the SEPA mandate repository. Nicolas Martelliere VIDAL France SA vidal.fr

Happy Business Starts Here

Vision

Products

Zuora Central Platform

Products

Zuora Marketplace

Solutions

By Industry

By Role

Customers

Resources

Resources

Subscribed

Support

Company

Billing & Payment Ideas

Ability to undo an invoice reversal

Add Deprecated Invoice Merge Field Back - Payment.CreditCardNumberMasked

Request for autocomplete

Provide a (tracked) way to roll back a renewal if customer changes their mind

Use js callback instead of url redirect in Hosted payment page 2.0 advanced implementation

Error validation on TAB out for hosted payment page 2.0

Disable previous month from expiry month dropdown in HPM 2.0

Forecast Billing/Invoices

Select invoice due date

Disable automated pdf generation completely

Configurable Lockbox - Provide Payment Numbers

Additional PDF in invoice email

Console error from HPM2Preload

HPM2's iframe tag should have a customizable title or aria-label attribute.

Take upcoming suspension into account for invoice generation and billing preview

HPM2's iframe should resize itself on resize events

Accessibility issues in HPM's iframe form

Add an optional "Cancel" button to HPM2's iframe

The submit button in the iframe should be a button, not an anchor

SEPA - Slimpay - revoke mandate

Invoice PDF: CreditMemoApplication.AppliedAmount should be an available merge field

Billing an Account on specific weeks

Edit Invoice DAte