Skip Menu |

This queue is for tickets about the Business-OnlinePayment-InternetSecure CPAN distribution.

Report information
The Basics
Id: 18620
Status: rejected
Priority: 0/
Queue: Business-OnlinePayment-InternetSecure

People
Owner: Nobody in particular
Requestors: ivan-cpan-rt [...] 420.am
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.01
Fixed in: (no value)



Subject: Please map B:OP standard "login" field to merchant_id
Hi, Please map the Business::OnlinePayment standard "login" field (in the content) to InternetSecure merchant_id rather than requiring a non-standard "merchant_id" parameter when creating a new object. Please feel free to contact me and/or join the Business::OnlinePayment mailing list if you have any questions. Thanks!
Subject: Re: [rt.cpan.org #18620] Please map B:OP standard "login" field to merchant_id
Date: Fri, 21 Sep 2007 18:10:08 -0400
To: Guest via RT <bug-Business-OnlinePayment-InternetSecure [...] rt.cpan.org>
From: Frédéric Brière <fbriere [...] fbriere.net>
On Sun, Apr 09, 2006 at 06:25:44PM -0400, Guest via RT wrote: Show quoted text
> Please map the Business::OnlinePayment standard "login" field (in the > content) to InternetSecure merchant_id rather than requiring a > non-standard "merchant_id" parameter when creating a new object.
Your ::BankOfAmerica was my inspiration. :) It's been a while since I worked with IS (we ended up choosing another provider instead), but from what I remember, all they give you is a dinky 4-digit merchant ID, and rely on IP addresses for authentication. The BoA merchant_id parameter seemed more appropriate to me than trying to pretend there's a login going on somewhere. That, and if they ever do add a login procedure like BoA did, there won't be any clash over parameter names. Do feel free to reopen this ticket if you're not convinced. -- Double *sigh*. _04 is going onto thousands of CDs even as we speak, so to speak. -- Larry Wall in <199710221718.KAA24299@wall.org>