What goes in the Payment API Settings Field?

[kengary]

I'm working on a modification for our own Payment API, like PayPal and I've run into a wall. I'm looking for some help.

I've added a new payment api through the admin control panel called Sonlight. I've added the phrases, the template and I've uploaded a class_sonlight.php file. I've activated this type and I can send the potential subscriber information to my external gateway where it is processed.

The external gateway calls the payments.php program and it gets the correct return value of 1, just like PayPal.

All of that is there, implemented and seems to be working fine...but nothing happens.

The subscriber does not get their subscription so I figure I'm definitely missing a piece of the puzzle.

I cannot find much in the way of a comprehensive how-to tutorial covering every step necessary to implement a new payment api. It looks to me like I've covered all of the bases except possibly in one place.

When I look at the actual MySQL paymentapi table there is a column called settings. For all of the other api's there are some very cryptic settings there. For my new one it is just null. I can see that at least part of those settings are for custom fields like email addresses, etc. which I don't need to set up for my gateway. Is there more to that field? How does it get set and where?

Or is there some other hook that is missing causing something else to happen when a payment api calls the verify_payment() function? Cause like I said, it's getting called and returning the successful value correctly but the subscriptions themselves aren't happening.

If you have the answer I'd sure appreciate hearing from you. I'm looking everywhere and cannot find it.

(It'll probably be in the last place I look! ;-D)