user1774

I sell products that are USD and products that are CAD as many do. However I have some larger clients that pay in the actual currency for each service and do not want me doing the conversion. I.e., they will make me two separate payments per month, they may pay the CAD balance by bank transfer or creditcard, and pay the USD balance by PayPal. The default behavior of Blesta appears to be to bill all renewals in the clients preferred currency, based on an exchange rate of the product did not have a term in their currency. My solution so far is: I’ve added a custom field to clients called “Invoice Group by Currency”, and if this is not checked off cron.php operates as usual default behavior of blesta and will pass all the services into invoiceServices with the default currency for the group or client etc. However if it is checked, in createRenewingServiceInvoices() I iterate through the services to be invoiced, group them by currency then call a separate $this->invoiceServices() for each group of invoices of the same currency. Can you suggest if I am going to run into problems with this? These clients are not autobilled so I do not need to worry about having a way to specify/assign payments account to currencies for now, I think I Just need to clean up the client dashboard a bit to show a more organized view of the currencies grouped and flow to paying them.

I dont think you are actually reading what I am saying. The gateway module has various methods, such as processCc, authorizeCc, captureCc, voidCc, etc. However Blesta is only ever using the processCc, so I am asking in what situation does Blesta actually make use of the authorize/capture, because the module I have written based on the sdk clearly supports it, and looking in other modules that ship with blesta such as authorize_net they support it, however I did configure authorize_net to try and set it, and again i could not get it to authorize, it always went straight for a sale not authorization.

Yes, I have already created an orderform which requires manual approval which is great. The issue is, during the order process it is always calling processCc for the payment which is a capture, despite the fact the gateway has authorizeCc capabilities. so my question is, what situation is required for blesta to only execute an authorization, and then then later complete it with a capture. I even tried having my gateway return "Pending" for payment status, however this cause unfavorable situation where there order did not appear as waiting for approval but only as pending, and when I approved it nothing was done with the payment.... even if i went into the payment and changed it from Pending to Approved, no option came up to execute this change via the gateway.

Is Blesta able to, out of the box, only preauth payments for new orders, and only capture when the order is accepted? I have also started a post in the dev section, as I was writing my own merchant gateway module, however I feel like Blesta maybe does not actually function this way and maybe it was intended for the future? I tried reading through the code looking for anywhere there are references to authorizepayment / authorizecc vs processpayment/processcc etc. Thanks,

I am looking to start using blesta what i was hoping blesta would do is, when an order comes in, it would do the preauthorization call, and if the order was approved it would do the capture. when I look at the UI and workings of blesta, i see no mention of preauth/capture, however I do see the methods in the sdk for a gateway. so i am wondering, if I implement these functions in my gateway to the merchant, what logic is blesta using for when to authorize and when to capture.