Export possibilities: CSV and XML

You can export Orders, Subscriptions, Transactions, Customers and Recurring Payments now also as XML. It’s a different way of exporting data and it is often useful if you use certain ERP systems that accept such data import file types.

Delay Stripe payments

Typical payment logic: when someone goes through your checkout after selecting a product they want to rent, the first transaction/payment is made as soon as the customer gives his payment details and proceeds through the checkout process. Additionally, the card and the payment method are validated as part of the checkout process.

Delayed payments: when a customer goes through the checkout process everything remains the same that is a validation of the card and the payment method, but the transaction is not charged or to put it into other words, is delayed (if desired). The time duration of the delay can be adjusted to anything based on your business needs.

Use case: some products are available in limited quantities and therefore when such products are demanded by the customer, then the vendor first needs to check if the product is available for renting or not.

The said setting can be enabled for any company using Stripe as their PSP. A credit check is independent of the transaction or payment being charged which means that even though technically there is no transaction happening, the credit check still remains in place.

Send payment failed emails to your customer

When payments/transactions fail to go through due to XYZ reasons, the customer is notified about the failed payment via email. You can enable or disable this feature. By default, it is disabled and if you wish to enable then you can get in touch with circuly via the Service Desk to enable it for your operations backend. You can also decide upon the frequency of the retries and also when the email should be sent to this customer. After x (the number defined by you for failed payment retries) no. of retrials have been made, your connected inbox is informed about the failed retries. You can then proceed to get in touch with the customer and if the customer has updated their payment details then you can try to do a manually retry. To do a manual retry of a failed transaction, read this article: How to retry failed payments?

Return product email after multiple payment retrieval attempts

After two payment retrial cycles two months in a row, the unpaying customer is sent an automated email to return the unpaid product. The email contains the return instructions that can be used by the customer to send the product back to you in case the customer goes through two retrial payment cycles, two months in a row.

CSV Exports to Notification

Export notifications that is update about your export file being ready pop up in the notification panel. Make sure to check the notification panel to download your requested data. In case the notification doesnt pop up, then that’s because your session has timed out. Simply login again and proceed to checking the notification panel.

‍

Read more: How to export data from your circuly operations backend?

Add defined extra info to Subscriptions

You can add additional meta fields to the Create Subscription window. You can set up multiple fields and they can also be made to show up on the invoice. To enable it, get in touch with circuly via the Service desk.

‍

Edit customer email address from operations backend

In case your customer submits a wrong email address, you can now easily edit it in your circuly operations backend.

Read more: How to edit an email address and phone number?

Filter Recurring Payment by tries and status.

Use case: if you want to see how many payments went through in the first payment attempt, how many went through in the second payment attempt and so on. It’s useful if you want to see some data points and make some key decisions.

The period the payment was charged for is also shown on the invoice for more clarity.