PayConnect(3pm)

πŸ“¦
version 0.02 Β· 2 versions
  • 0.02 Β· debian bookworm, debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking (latest)
  • 0.02 Β· ubuntu jammy
, in debian bookworm, debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking

πŸ’– 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 🌈

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