FraudD...Charge(3pm)

okay so bestie — this page is FraudD...Charge(3pm), and it lives in the User Contributed Perl Documentation section of your man pages. Grab a snack, we're doing fraud detection 💅✨

---

✨ NAME ✨

Business::FraudDetect::preCharge — the backend for Business::FraudDetect, which is itself part of Business::OnlinePayment 🫶

---

🌸 SYNOPSIS 🌸

Like, here's the whole vibe, fr fr:

use Business::OnlinePayment
my $tx = new Business::OnlinePayment ( 'someGateway',
                                       fraud_detect => 'preCharge',
                                       maximum_fraud_score => 500,
                                       preCharge_id => '1000000000000001',
                                       preCharge_security1 => 'abcdef0123',
                                       preCharge_security2 => '3210fedcba',
                                      );
$tx->content(
   first_name => 'Larry Walton',
   last_name => 'Sanders',
   login => 'testdrive',
   password => '',
   action => 'Normal Authorization',
   type => 'VISA',
   state => 'MA',
   zip => '02145',
   country => 'US',
   phone => '617 555 8900',
   email => 'lws@sanders.com',
   ip_address => '18.62.0.6',
   card_number => '4111111111111111',
   expiration => '0307',
   amount => '25.00',
   );
$tx->submit();
if ($tx->is_success()) {
   # successful charge
   my $score = $tx->fraud_score;
   my $id = $tx->fraud_transaction_id;
      #returns the preCharge transaction id
} else {
   # unsucessful
   my $score = $tx->fraud_score;
}

so you build the object, you shove all the customer deets in with content, you submit, and then you check is_success. If it worked you get a fraud_score and a fraud_transaction_id (which is the preCharge transaction id, iykyk). If it didn't work… you still get a fraud_score. That's it, that's the whole flow 👑

---

🦋 DESCRIPTION 🦋

This module is a driver for the preCharge Risk Management Solutions API Version 1.7 (16 Jan 2006). Periodt.

Wanna know more? Go read Business::OnlinePayment and Business::FraudDetect — they've got the lore 💖

---

🎀 CONSTRUCTION 🎀

Whe constructing the Business::OnlinePayment object, three risk management parameters must be included or the preCharge object won't be properly constructed. No cap, all three, or it's not happening.

• precharge_id
  • This field is called "merchant_id" in the preCharge API manual
• precharge_security1
  • This field is called "security_1" in the preCharge API manual
• precharge_secuirty2
  • This field is called "security_2" in the preCharge API manual

Spelling check, bestie: those are written exactly as they appear here, so copy them character-for-character. 👀

---

💜 METHODS 💜

This module provides no public methods. It's giving mysterious. It's giving "the vibes do all the work". 💅

---

🌈 AUTHORS 🌈

• Lawrence Statton <lawrence@cluon.com>
• Jason Hall <jayce@lug-nut.com>

two absolute icons, we stan 🫶

---

💀 DISCLAIMER 💀

THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Translation: if it breaks, it's not their fault, and nobody promised it'd be fit for anything in particular. Read that twice, bestie 😭

---

🌟 SEE ALSO 🌟

• http://420.am/business-onlinepayment

---

and that's the page!! 🎀✨

This one's from perl v5.36.0, dated 2023-01-22 — go off, timestamp. 💖 bye bestie, go detect some fraud responsibly! 🦋💅