Payment as bank transfer only
This topic contains 5 replies, has 3 voices, and was last updated by joecam 6 years, 10 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket-
AuthorPosts
-
January 3, 2018 at 10:11 pm #1071
Hi,
I hope you can help me to find the solution for my case, I don’t know whether it is a feature request, or bug. wpinvoicing+GD…
I have to setup the payment option for Bank Payment only, without online gateways (I cannot choose payment gateways from the offered ones, need custom one with other language than english, so maybe later).
When somebody add a listing to the directory and directed to the Checkout they can complete the payment with your Bank Pre Transfer payment. So far so good…
If the user going into his profile or to the invoice history and check the invoices, the invoice is there and OK, so bank details displayed correctly.
But – and here is my problem – the Pay Now option also displayed, which will take the user back to the same payment option, so can pay by Bank Transfer again, which I would like to prevent, and not to confuse the users. Payment status is Pending Payment, so that is correct.1. question: is there any solution to hide the Pay Now button other than CSS? (I will find the way by CSS) If only one bank transfer option offered there is no reason to display it.
Let we go a step toward in the billing flow. So the user published his entry, the payment status is Pending Payment and his entry in the Geodirectory is in DRAFT status. If an administrator checking the Invoice in the backend, it is OK, but if checking the entry in the GD, then it says in the Invoice for Listing box: Create a new invoice for this listing with a package xxxxxxx. Invoice will be created with Pending Payment status.
I feel this box should display some more relevant info, so Invoice number, link to it, etc. as the invoice is already created but the status is PendingPayment. Confusing the administrator and will create a new one…2. question: I guess this is a bug, so the invoice detail should be displayed on the backend in the “Invoice for Listing” box, and not instruct the admin to create a new one.
I know that your Bank payment is created for pre-payment, but I would need your help to transform it into simple/post bank payment, so when the user post an entry into the GD, and pays with the Bank Transfer option, then the Entry would be published until due date automatically, even the payment status is still Pending Payment. If the user pays the bill before due date, than the administrator would set the payment to Paid status manually and everything fine… I found your Due Date Setting in the Email setting (I don’t know why there) with a checkbox saying: Check this to enable due date option for invoices. It works on the invoice (displays the correct due date), but I feel it should work with the Bank Transfer payment option as well, and allow to autopublish the entry even with Pending Payment status… does it make sense?
3. question: Is there any option or workaround to auto-publish the GD entry in case of Bank Transfer, even with Pending Payment Status and due date?
Thank you so much,
January 4, 2018 at 12:19 am #1073Hello!
Thank you for contacting us about these issues. We are working hard on making a great product and glad to hear your ideas.
1. CSS is the only option at this time. We will keep this in mind for future versions.
2. The invoice link is not displayed at this time, only a link to create a new invoice, for the purpose of convenience. We will keep this in mind for future versions.
3. Do you also want the listing to be unpublished if the invoice due date passes? We are looking into advanced workflows for future versions. This isn’t supported at this time, but, please provide us with additional details and confirm whether that is how you would want it to work and we will look into it.
January 4, 2018 at 1:00 am #1074Hi Alex,
Thank you for your reply.
1. OK, would be nice feature in the future, now it will be solved by CSS.
2. Yes, you are right, there is no Invoice link in the published entry (also would be nice in the future) – But now there is the Create Invoice Link and box in the Draft Entry, which should be not there at all. There is Invoice already created (but with pending status) – so i would say it is a bug, as it is not realizing that there is an attached and unpaid invoice for the entry.
3. Ideally, of course it would handle the the whole publish-control, let we say: Due Date is set for ex 10 days, but paid by bank transfer -> Invoice created and gets the Pending status, at the same time the entry published. -> if and when the payment arriving, the administrator set the status in the invoicing to Paid, and it allows the whole term which has been paid – if the payment status still Pending at the day+1 of the due date, than the entry status should be set back to unpublished (or set back to free package or whatever)
I guess this functionality would be useful for others as well, and it would bring up a new level of the bank transfer as payment.If we not talking the Ideal way, and take out the publish-control, the minimum function should be like this: user publish an entry and pay by bank transfer -> entry published and Invoice created with Pending status -> If the invoice will be not paid and not set to Paid status, there should be a sign “over due” or a list for those over due payment, or just leave it to the site admin to track manually…
I hope i was clear with the functions, please ask if need more explanation.
Now i would need at least a minimum functionality to be able to start my site with the Bank transfer only payment. The most important here is to auto publish the entry if the bank transfer has been used.
Please help me to find the right file/function to make these changes.Thanks,
January 4, 2018 at 6:06 am #1075Hello,
2. Yes, you are right, there is no Invoice link in the published entry
We have already added metabox in backend listing page to list invoices related to the listing.(check attachment) This will be in next release.
3. Ideally, of course it would handle the the whole publish-control…
Thanks for more explanations. It requires some extra code customization to implement feature that you want to achieve. We are working to make features more and more customer friendly, so i will discuss with our team for implementation this feature if it not require more core changes.
Thanks,
KiranJanuary 4, 2018 at 1:37 pm #1078Hello,
I have discussed your feature request with my team members. The feature request you asked requires more core codes changes and it affects the existing expire listing process.
We have decided to put your feature request on hold, but we will think to implement in future if more customers asking for the same.To implement this feature, you can find & hire GD Expert for customization at https://geodirectoryexperts.com/.
Thanks,
KiranJanuary 4, 2018 at 6:49 pm #1079Hi Kiran,
Thank you for your feedback, understood.
thanks,
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket