[ic] Unknown charge type

Michael Lehmkuhl interchange-users@icdevgroup.org
Wed Jul 17 13:50:01 2002


Hello.

We are rolling our own Interchange payment method for ECHO.  We've created a
Perl module that makes the connection and submits the request to ECHO.  That
part OpenECHO.pm is functional and tested.

We are getting the following error when we try to submit payment during the
checkout process:
    (openecho): Charge operation 'openecho' failed.

The error.log for the catalog has this message:
    Unknown charge type: openecho

The catalog.cfg has a Route set up for openecho:
    Route  openecho      id           "__ECHO_PAYMENT_ID__"
    Route  openecho      secret       "__ECHO_PAYMENT_SECRET__"
    Route  openecho      host         "__ECHO_PAYMENT_HOST__"

The catalog.cfg also requires the OpenECHO module, which is called
OpenECHO.pm in the lib directory of the Interchange root directory:
    # Enable OpenECHO payment processing
    Require module OpenECHO

The following variables are set in variable.txt:
    MV_PAYMENT_ID    1234682203    Payment
    MV_PAYMENT_MODE    custom openecho    Payment
    MV_PAYMENT_SECRET    ******    Payment
    ECHO_PAYMENT_ID    1234682203    Payment
    ECHO_PAYMENT_SECRET    ******    Payment
    ECHO_PAYMENT_MODE    custom openecho    Payment

In interchange.cfg, we include the globalsub:
    # Include OpenECHO payment method code
    include globalsub/openecho

We have a file called openecho in eg/globalsub that has the following code:
    GlobalSub <<EOS
    sub openecho {

    ::logDebug("openecho payment GlobalSub called");

Since debugging is turned on and we aren't getting an error in /tmp/icdebug,
it looks like Interchange isn't even realizing that the openecho routine
exists.

I've seen the "Unknown charge type:" error before, and it seems like the
problem that time was that our include statement in the interchange.cfg file
was looking for globalsubs rather than globalsub.  That isn't the problem
this time.

I've checked through the mailing list archives, but none of the solutions
mentioned there fixed this issue.

We are getting ready to launch this store very soon, so this is a somewhat
urgent issue, and I'd really appreciate anyone's help.

Thanks.

-- 
Michael Lehmkuhl <michael@electricpulp.com>
Partner, Electric Pulp

1.605.988.0177 : 1.888.722.PULP
electricpulp.com