OCS Itemised Invoice for Manual Payments

@MikeL wrote:

Hi

At present the manual payment method for a conference shows the payer when they click [Register] a paragraph listing the rego payment options and the total amount to pay.

The Conference Manager gets an email saying:
A manual payment needs to be processed for the conference Blah....
and the user Foo Bar (username "foobar").
The item being paid for is "Registration".
The cost is 600 (AUD).
This email was generated by Open Conference Systems' Manual Payment plugin.

The Conf Manager can see what the items are only by going into the Registrations section and clicking Edit for that user. They had better not accidentally change anything.

This is what we need in Australia to make it a valid invoice.
When the payer clicks [Register] an itemised list with the amount per item and the total is displayed rather than just the plain paragraph of the purchased items..

INVOICE
Rego                $ 400.00
Excursion 1     $ 250.00
Conf T shirt     $    15.00
                        --------------
                         $ 665.00

This is displayed to the payee and emailed to the payee and is either mailed to conf manager or can be viewed on a page as read-only by the conf manager.

I see that the total amount is in the data field of the queued_payments table.
(s:12 being a string of 12 chars, etc )
O:16:"OCSQueuedPayment":9:
{
s:12:"conferenceId"; s:1:"1";
s:11:"schedConfId"; s:1:"1";
s:4:"type"; i:1;
s:10:"requestUrl"; s:75:"http:/myconf/index.php/blah-blah/payment/landing";
s:9:"paymentId"; N;
s:6:"amount"; i:600;
s:12:"currencyCode"; s:3:"AUD";
s:6:"userId"; s:1:"3";
s:7:"assocId"; s:2:"12";
}

Clearly some pulling out the item prices from the other tables would be needed. Then formatting into a table.

Producing an itemised invoice is quite important for us at present.

Thanks
Mike

Posts: 1

Participants: 1

Read full topic