Multi-Site setup & Silent URLs

[rauli]

I am wondering how s2member handles silent URLs for IPN submissions from payment processors with Multi-Site installs.

I can see in each sites s2member options for a payment processor it gives a separate URL based on the sites own URL however you can only set one IPN address for say Authorize.net

Am I correct when I think that this does not matter, that the main Sites silent URL is enough to use as the IPN silent URL in the payment processors configuration as s2member captures all events and probably handles each transaction appropriately in that each transactions resulting username is then applied into the same site they began the checkout process from?

Thanks,
Rauli

[Cristián Lávaque]

The parent blog doesn't handle the payments for the child blogs. Each blog gets its own instance of s2Member which gets configured independently, including the gateway.

[rauli]

Thanks for the reply.

Ok, but if one instance of the s2member indicates to set the silent URL to say:-
http://www.website.org/blog1/?s2member_pro_authnet_notify=1

and another s2member options page site in the multi site indicates:-
http://www.website.org/blog2/?s2member_pro_authnet_notify=1

But the silent URL is set in the Authorize.NET account settings as (and only can only set one silent URL in the account):-
http://www.website.org/blog1/?s2member_pro_authnet_notify=1

Won't the blog1 site s2member instance receive all IPN notices and create users for that blog instead regardless of which blog has had a transaction occur?

Can the Authorize.net forms be made to have custom Silent URL set for each site? Because I think the Paypal buttons do support that.

Thanks,
Rauli

[Cristián Lávaque]

I thought the child blogs belonged to other users, so they'd have their own gateway accounts. I understand now that you're talking about your own and will use the same gateway.

I don't know if the Auth.Net pro-forms can set the IPN/Silent URLs for that blog based on your s2Member Auth.Net account details, and have the settings over at Auth.Net be the default. You'll have to run a couple of tests to be sure.

I know it works for PayPal, though. viewtopic.php?f=36&t=2905