This doesn't seem to be a very good option mainly due to the Terms and Conditions of Use that most people might skip over.

* User agrees to use the USPS Web site, APIs and USPS data to facilitate USPS shipping transactions only.
* User may not use USPS Web Tools APIs in connection with any other payment system other than the USPS Pay@Delivery Service.
* Developer may package software which interfaces with any or all USPS APIs with password and ID for resale or distribution to others only after registering with USPS as a Developer and agreeing to these Terms and Conditions of Use.

So you can only use the API to get info if you're using USPS shipping and you must use their services to handle monetary transactions. This solution doesn't seem to help with the problem at hand, unless he wants to dump his cc processing service. Furthermore, this particular problem doesn't require anyone to verify that the address exists but rather compensate for the expected data format of his processing service's AVS. As for your modules that you're releasing to CPAN, be certain to include the terms of use as it is yet another requirement for use of the API.

antirice    
The first rule of Perl club is - use Perl
The ith rule of Perl club is - follow rule i - 1 for i > 1

In reply to Re: Re: Address conversion by antirice
in thread Address conversion by tcf22

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.