Checkout API Ideas

Merchants looking for their statements look under “Reports”. I know that it’s under “Billing” which makes sense; however, why not have “Statements” in both places.

Be able to see which team member created an invoice (MX 4 used to do this). History events are logged when the invoice is created but it doesn't say who it was created by.

Hello,I was hoping that there would be a way that you could add more detailed chargeback information to your chargeback report?

When a batch is closed have a settlement report e-mailed to the merchant Virtual Terminal settlement report, one feature we have been missing for years in mx4 is when a batch is closed we have a settlement report e-mailed to the merchant. Would be...

Coding needs to exist to add things like Invoice number, Customer Name/Company Name (for B2B sales) fields in the link2pay screen that customers see when clicking on the payment link. This info should then be seen on the receipt as well.

It should be a total no-brainer to be able to generate/export a detailed list of the given transactions in a particular settlement, day, device, etc.--and to be able to filter that detailed list by different criteria, such as type of card. (For in...

In MX4 when at the payment screen, it was defaulted that the card info would be vaulted. However, if you did not want the CC info to be vaulted you could simply uncheck that box. When merchants have multiple recurring customers but pay with differ...

My identifying information (e.g.., license #, tax ID #) used to be located under my business name, address, and phone #. Now it won't go there-- It can only be placed on the opposite side of the page or along the center. Looks out of place. Also, ...

When a merchant is printing a receipt, the items being sold are not displaying on receipt. If we go into the transaction detail we do show a breakdown of items. But the customer doesn't get a description of what they bought. Merchant is using reta...

Currently one of the things limiting Link2Pay from its full potential is that we have no way of adding any custom fields - other than a memo field which is vague - and cannot be set as a required field. merchants often require certain info to be...