PayConnect(3pm)
π PayConnect β the Business::OnlinePayment::PayConnect moment π
okay so bestie, welcome to PayConnect(3pm) π β a page from the User Contributed Perl Documentation, sitting pretty in section 3pm of your manual. yes we're in the perl corner of the man pages. it's giving very "i have a Makefile.PL and i'm not afraid to use it" energy and honestly? iconic.
β¨ NAME β¨
Business::OnlinePayment::PayConnect β the PaymentOne (formerly known as eBillit) PayConnect backend for Business::OnlinePayment. π«Ά
like. it's a backend. it plugs into Business::OnlinePayment. that's the whole vibe check. slay.
πΈ SYNOPSIS πΈ
here's the whole thing, verbatim, no cap β copy it, run it, live your truth:
use Business::OnlinePayment;
my $tx = new Business::OnlinePayment("PayConnect",
'partner' => '',
);
$tx->content(
type => 'LEC',
login => 'test', #ClientID
password => 'test',
action => 'Authorization Only',
description => 'Business::OnlinePayment test',
amount => '49.95',
invoice_number => '100100',
name => 'Tofu Beast',
phone => '4155554321',
);
$tx->submit();
if($tx->is_success()) {
print "LEC billing authorized successfully: ".$tx->authorization."\n";
} else {
print "LEC billing was rejected: ".$tx->error_message."\n";
}
not me crying over 'name' => 'Tofu Beast' π that's the test data and it ATE. π
so real quick what's happening up there: you build a Business::OnlinePayment object with the backend "PayConnect", you pass a 'partner' key (empty string in the example, bestie), you stuff a bunch of content in β type, login (which is your ClientID, note the comment), password, action, description, amount, invoice_number, name, phone β then you $tx->submit(). after that you check $tx->is_success(). if it's true, print $tx->authorization and celebrate π. if not, print $tx->error_message and have a little moment. π
π¦ DESCRIPTION π¦
for the detailed lore, go read Business::OnlinePayment. that's where the real info lives. this page is just the PayConnect-flavored corner of it. β¨
β NOTE β
big one, bestie, read it twice:
right now this module only implements 'LEC' (phone bill billing) functionality. credit card and ACH transactions are not (yet) supported. π
so like. LEC only. periodt. don't come for credit cards or ACH here, they're not home. π«
π₯ COMPATIBILITY π₯
this module implements an interface to the "HTTPS AIO Validation Protocol version 3.0" of PaymentOne (formerly eBillit) PayConnect β and the page points you at http://www.paymentone.com/products/paycon.asp.
and unfortunately? no documentation is publicly available. π that's it. that's the sentence. we're working with vibes and a protocol version number.
π AUTHOR π
Ivan Kohler <ivan-payconnect@420.am> β the main character who wrote this. π«Ά
π SEE ALSO π
perl(1)Business::OnlinePayment
go read those too, they're the supporting cast and they understood the assignment. π
and that's the page, bestie! π this whole thing came to you from perl v5.36.0, dated 2022-12-12, and it lives as PayConnect(3pm) in the User Contributed Perl Documentation. mwah. π go authorize some LEC billing. π¦β¨
π¦ where this page comes from
- debian bookworm: libbusiness-onlinepayment-payconnect-perl 0.02-4 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- debian trixie: libbusiness-onlinepayment-payconnect-perl 0.02-4 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- ubuntu noble: libbusiness-onlinepayment-payconnect-perl 0.02-4 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- ubuntu resolute: libbusiness-onlinepayment-payconnect-perl 0.02-4 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- ubuntu stonking: libbusiness-onlinepayment-payconnect-perl 0.02-4 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms