Announcement

Collapse
No announcement yet.

Linkpoint MvCommerce

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Linkpoint MvCommerce



    Can someone please point me to a reference, explaining the fields used in
    the MvCommerce tag for Linkpoint. I've looked for several hours on the
    Linkpoint site, on the Miva site, and on the message boards. I've downloaded
    about 25 PDF's, explaining everything from creating API's to using the UPS
    library.

    I'm sure the developers didn't slave over a commerce library without
    recording the how-to's along the way. Why is it such a secret?

    Please, oh, please, help me.


    Bill Stanley
    Webnician



    Tags: None
    #2
    Linkpoint MvCommerce



    This works for me. The .pem file should be located in a subdirectory in
    your root data directory. The sub should be called LinkPoint - I'm not
    completely certain on this one, but I >think< that's the one I use. I
    havent' cleaned up the code, so there are variables that I used in
    there, but I think this will give you a good starting point.

    Scot
    <A HREF ="http://www.scotsscripts.com">http://www.scotsscripts.com</A>

    <MvIF EXPR = "{g.payment_type EQ 'linkpoint'}">

    <MvASSIGN NAME = "l.order_bname" VALUE = "{ g.order_bname }">
    <MvASSIGN NAME = "l.order_sname" VALUE = "{ g.order_bname }">
    <MvASSIGN NAME = "l.order_baddr1" VALUE = "{ g.req_addr }">
    <MvASSIGN NAME = "l.order_saddr1" VALUE = "{ g.req_addr }">
    <MvASSIGN NAME = "l.order_bzip" VALUE = "{ g.req_zip }">
    <MvASSIGN NAME = "l.order_szip" VALUE = "{ g.req_zip }">
    <MvASSIGN NAME = "l.req_zip" VALUE = "{ g.req_zip }">
    <MvASSIGN NAME = "l.req_addr" VALUE = "{ g.req_addr }">
    <MvASSIGN NAME = "l.order_bcompany" VALUE = "{ g.order_bcompany }">
    <MvASSIGN NAME = "l.order_bcity" VALUE = "{ g.order_bcity}">
    <MvASSIGN NAME = "l.order_scity" VALUE = "{ g.order_bcity}">
    <MvASSIGN NAME = "l.order_bstate" VALUE = "{ g.order_bstate }">
    <MvASSIGN NAME = "l.order_sstate" VALUE = "{ g.order_bstate }">
    <MvASSIGN NAME = "l.order_bcountry" VALUE = "{ g.order_bcountry}">
    <MvASSIGN NAME = "l.order_scountry" VALUE = "{ g.order_bcountry}">
    <MvASSIGN NAME = "l.order_phone" VALUE = "{ g.order_phone}">
    <MvASSIGN NAME = "l.req_email" VALUE = "{ g.req_email}">
    <MvASSIGN NAME = "l.order_fax" VALUE = "{ g.order_fax}">
    <MvASSIGN NAME = "l.order_shipping" VALUE = "{ g.order_shipping}">

    <MvIF EXPRESSION = "{tolower(g.order_bstate) EQ tolower(g.tax_state)}">
    <MvASSIGN NAME = "l.order_tax" VALUE = "{ (g.tax * .01 * l.total)
    ROUND 2}">
    <MvELSE>
    <MvASSIGN NAME = "l.order_tax" VALUE = "{ 0 }">
    </MvIF>

    <MvASSIGN NAME = "l.order_subtotal" VALUE = "{ g.order_subtotal}">
    <MvASSIGN NAME = "l.order_comments" VALUE = "{ g.order_comments}">
    <MvASSIGN NAME = "l.req_cardnumber" VALUE = "{ g.req_cardnumber}">
    <MvASSIGN NAME = "l.req_expmonth" VALUE = "{ g.req_expmonth}">
    <MvASSIGN NAME = "l.req_expyear" VALUE = "{ g.req_expyear}">
    <MvASSIGN NAME = "g.req_chargetotal" VALUE = "{ g.total }">

    <MvASSIGN NAME = "l.fields" VALUE = "order_bname, order_bcompany,
    order_baddr1, order_bcity, order_bstate, order_bzip, order_bcountry,
    order_sname, order_saddr1, order_scity, order_sstate, order_szip,
    order_scountry, order_phone, order_fax, order_total, order_shipping,
    order_tax, order_subtotal, order_comments, req_cardnumber, req_expmonth,
    req_expyear, req_chargetotal, req_zip, req_addr, req_email,
    req_configfile, req_chargetype, req_keyfile, req_host, req_port,
    req_result">


    <MvASSIGN NAME = "l.req_configfile" VALUE = "{ '600410' }">
    <MvASSIGN NAME = "l.req_chargetype" VALUE = "SALE">
    <MvASSIGN NAME = "l.req_keyfile" VALUE = "{ 'xxx.pem' }">
    <MvASSIGN NAME = "l.req_host" VALUE = "{ 'secure.linkpt.net' }">
    <MvASSIGN NAME = "l.req_port" VALUE = "{ '1139' }">


    <MvCOMMERCE METAMETHOD = "LinkPoint" FIELDS = "{ l.fields }">
    <MvIF EXPR = "{s.ch_approved EQ 'APPROVED'}">
    <MvASSIGN NAME = "l.success" VALUE = "{ 1 }">



    <MvELSE>
    Your transaction has not been approved. Please go back and verify
    your information.



    Transaction Error Message: <MvEVAL EXPRESSION = "{ch_error}">
    </MvIF>
    </MvCOMMERCE>
    </MvIF>
    </MvIF>


    Webnician wrote:
    > Can someone please point me to a reference, explaining the fields used in
    > the MvCommerce tag for Linkpoint. I've looked for several hours on the
    > Linkpoint site, on the Miva site, and on the message boards. I've downloaded
    > about 25 PDF's, explaining everything from creating API's to using the UPS
    > library.
    >
    > I'm sure the developers didn't slave over a commerce library without
    > recording the how-to's along the way. Why is it such a secret?
    >
    > Please, oh, please, help me.
    >
    >
    > Bill Stanley
    > Webnician
    >
    >
    >

    Comment

      #3
      Linkpoint MvCommerce



      - - - Scot Ranney ([email protected]) - - -

      > <MvASSIGN NAME = "l.fields" VALUE = "order_bname, order_bcompany,
      > order_baddr1, order_bcity, order_bstate, order_bzip, order_bcountry,
      > order_sname, order_saddr1, order_scity, order_sstate, order_szip,
      > order_scountry, order_phone, order_fax, order_total, order_shipping,
      > order_tax, order_subtotal, order_comments, req_cardnumber, req_expmonth,
      > req_expyear, req_chargetotal, req_zip, req_addr, req_email,
      > req_configfile, req_chargetype, req_keyfile, req_host, req_port,
      > req_result">


      THANKS, Scot. You've greatly amended my list of known variables.

      I already had my configurations straight because since was documentation for
      it. I even got a working payment processor with Ben's help yesterday.

      HOWEVER, there are STILL many variables not accounted for. So far, all the
      fields I've come up with, correspond to the ones in the API manual, but with
      no clear naming convention.

      Where did you get your information in the first place?


      Does anyone know where there is a complete list of fields that can be passed
      by the Linkpoint Miva commerce library? ...a manual to that end would be
      even better.


      Bill Stanley
      Webnician


      Comment

        #4
        Linkpoint MvCommerce



        I got my info from one of the old uncompiled linkpoint payment modules
        for Miva Merchant.

        Scot

        Webnician wrote:
        > - - - Scot Ranney ([email protected]) - - -
        >
        >
        >><MvASSIGN NAME = "l.fields" VALUE = "order_bname, order_bcompany,
        >>order_baddr1, order_bcity, order_bstate, order_bzip, order_bcountry,
        >>order_sname, order_saddr1, order_scity, order_sstate, order_szip,
        >>order_scountry, order_phone, order_fax, order_total, order_shipping,
        >>order_tax, order_subtotal, order_comments, req_cardnumber, req_expmonth,
        >>req_expyear, req_chargetotal, req_zip, req_addr, req_email,
        >>req_configfile, req_chargetype, req_keyfile, req_host, req_port,
        >>req_result">
        >
        >
        >
        > THANKS, Scot. You've greatly amended my list of known variables.
        >
        > I already had my configurations straight because since was documentation for
        > it. I even got a working payment processor with Ben's help yesterday.
        >
        > HOWEVER, there are STILL many variables not accounted for. So far, all the
        > fields I've come up with, correspond to the ones in the API manual, but with
        > no clear naming convention.
        >
        > Where did you get your information in the first place?
        >
        >
        > Does anyone know where there is a complete list of fields that can be passed
        > by the Linkpoint Miva commerce library? ...a manual to that end would be
        > even better.
        >
        >
        > Bill Stanley
        > Webnician
        >
        >

        Comment

          #5
          Linkpoint MvCommerce



          The way linkpoint works is that some of the variables are required, and
          others are not. The ones that are required as far as I remember start
          with the "req_" string. It's just a way to keep in mind which variables
          you definitely need. The other ones are also important if the linkpoint
          account in question uses various types of anti-fraud checking such as
          the billing address fields.

          I originally figured this out by looking at the linkpoint payment module
          that came with uncompiled versions of Merchant.

          Scot


          <A HREF ="http://www.scotsscripts.com">http://www.scotsscripts.com</A>


          Patrick Locke wrote:
          > This post I found from a while back along with another. Both use req_
          > beforethe variable name for some variables and this example uses order_
          > before some other fields. Are these prefixes required? I have never delt
          > with linkpoint before and their API uses just the field name no req_ or
          > order_ prefix. Any suggestions or links to other documnetation would be
          > appreciated. BTW this is for a NON-Merchant Application.
          >
          > TIA
          > Patrick
          > ----- Original Message -----
          > From: "Scot Ranney" <[email protected]>
          > To: "Webnician" <[email protected]>
          > Cc: "Miva Users" <[email protected]>
          > Sent: Thursday, October 07, 2004 2:41 PM
          > Subject: Re: [meu] Linkpoint MvCommerce
          >
          >
          >
          >>This works for me. The .pem file should be located in a subdirectory in
          >>your root data directory. The sub should be called LinkPoint - I'm not
          >>completely certain on this one, but I >think< that's the one I use. I
          >>havent' cleaned up the code, so there are variables that I used in
          >>there, but I think this will give you a good starting point.
          >>
          >>Scot
          >><A HREF ="http://www.scotsscripts.com">http://www.scotsscripts.com</A>
          >>
          >><MvIF EXPR = "{g.payment_type EQ 'linkpoint'}">
          >>
          >><MvASSIGN NAME = "l.order_bname" VALUE = "{ g.order_bname }">
          >><MvASSIGN NAME = "l.order_sname" VALUE = "{ g.order_bname }">
          >><MvASSIGN NAME = "l.order_baddr1" VALUE = "{ g.req_addr }">
          >><MvASSIGN NAME = "l.order_saddr1" VALUE = "{ g.req_addr }">
          >><MvASSIGN NAME = "l.order_bzip" VALUE = "{ g.req_zip }">
          >><MvASSIGN NAME = "l.order_szip" VALUE = "{ g.req_zip }">
          >><MvASSIGN NAME = "l.req_zip" VALUE = "{ g.req_zip }">
          >><MvASSIGN NAME = "l.req_addr" VALUE = "{ g.req_addr }">
          >><MvASSIGN NAME = "l.order_bcompany" VALUE = "{ g.order_bcompany }">
          >><MvASSIGN NAME = "l.order_bcity" VALUE = "{ g.order_bcity}">
          >><MvASSIGN NAME = "l.order_scity" VALUE = "{ g.order_bcity}">
          >><MvASSIGN NAME = "l.order_bstate" VALUE = "{ g.order_bstate }">
          >><MvASSIGN NAME = "l.order_sstate" VALUE = "{ g.order_bstate }">
          >><MvASSIGN NAME = "l.order_bcountry" VALUE = "{ g.order_bcountry}">
          >><MvASSIGN NAME = "l.order_scountry" VALUE = "{ g.order_bcountry}">
          >><MvASSIGN NAME = "l.order_phone" VALUE = "{ g.order_phone}">
          >><MvASSIGN NAME = "l.req_email" VALUE = "{ g.req_email}">
          >><MvASSIGN NAME = "l.order_fax" VALUE = "{ g.order_fax}">
          >><MvASSIGN NAME = "l.order_shipping" VALUE = "{ g.order_shipping}">
          >>
          >><MvIF EXPRESSION = "{tolower(g.order_bstate) EQ tolower(g.tax_state)}">
          >><MvASSIGN NAME = "l.order_tax" VALUE = "{ (g.tax * .01 * l.total)
          >>ROUND 2}">
          >><MvELSE>
          >><MvASSIGN NAME = "l.order_tax" VALUE = "{ 0 }">
          >></MvIF>
          >>
          >><MvASSIGN NAME = "l.order_subtotal" VALUE = "{ g.order_subtotal}">
          >><MvASSIGN NAME = "l.order_comments" VALUE = "{ g.order_comments}">
          >><MvASSIGN NAME = "l.req_cardnumber" VALUE = "{ g.req_cardnumber}">
          >><MvASSIGN NAME = "l.req_expmonth" VALUE = "{ g.req_expmonth}">
          >><MvASSIGN NAME = "l.req_expyear" VALUE = "{ g.req_expyear}">
          >><MvASSIGN NAME = "g.req_chargetotal" VALUE = "{ g.total }">
          >>
          >><MvASSIGN NAME = "l.fields" VALUE = "order_bname, order_bcompany,
          >>order_baddr1, order_bcity, order_bstate, order_bzip, order_bcountry,
          >>order_sname, order_saddr1, order_scity, order_sstate, order_szip,
          >>order_scountry, order_phone, order_fax, order_total, order_shipping,
          >>order_tax, order_subtotal, order_comments, req_cardnumber, req_expmonth,
          >>req_expyear, req_chargetotal, req_zip, req_addr, req_email,
          >>req_configfile, req_chargetype, req_keyfile, req_host, req_port,
          >>req_result">
          >>
          >>
          >><MvASSIGN NAME = "l.req_configfile" VALUE = "{ '600410' }">
          >><MvASSIGN NAME = "l.req_chargetype" VALUE = "SALE">
          >><MvASSIGN NAME = "l.req_keyfile" VALUE = "{ 'xxx.pem' }">
          >><MvASSIGN NAME = "l.req_host" VALUE = "{ 'secure.linkpt.net' }">
          >><MvASSIGN NAME = "l.req_port" VALUE = "{ '1139' }">
          >>
          >>
          >><MvCOMMERCE METAMETHOD = "LinkPoint" FIELDS = "{ l.fields }">
          >><MvIF EXPR = "{s.ch_approved EQ 'APPROVED'}">
          >><MvASSIGN NAME = "l.success" VALUE = "{ 1 }">
          >>


          >><MvELSE>
          >>Your transaction has not been approved. Please go back and verify
          >>your information.
          >>


          >>Transaction Error Message: <MvEVAL EXPRESSION = "{ch_error}">
          >></MvIF>
          >></MvCOMMERCE>
          >></MvIF>
          >></MvIF>
          >>
          >>
          >>Webnician wrote:
          >>
          >>>Can someone please point me to a reference, explaining the fields used
          >
          > in
          >
          >>>the MvCommerce tag for Linkpoint. I've looked for several hours on the
          >>>Linkpoint site, on the Miva site, and on the message boards. I've
          >
          > downloaded
          >
          >>>about 25 PDF's, explaining everything from creating API's to using the
          >
          > UPS
          >
          >>>library.
          >>>
          >>>I'm sure the developers didn't slave over a commerce library without
          >>>recording the how-to's along the way. Why is it such a secret?
          >>>
          >>>Please, oh, please, help me.
          >>>
          >>>
          >>>Bill Stanley
          >>>Webnician
          >>>
          >>>
          >>>

          Comment

            #6
            Linkpoint MvCommerce



            This post I found from a while back along with another. Both use req_
            beforethe variable name for some variables and this example uses order_
            before some other fields. Are these prefixes required? I have never delt
            with linkpoint before and their API uses just the field name no req_ or
            order_ prefix. Any suggestions or links to other documnetation would be
            appreciated. BTW this is for a NON-Merchant Application.

            TIA
            Patrick
            ----- Original Message -----
            From: "Scot Ranney" <[email protected]>
            To: "Webnician" <[email protected]>
            Cc: "Miva Users" <[email protected]>
            Sent: Thursday, October 07, 2004 2:41 PM
            Subject: Re: [meu] Linkpoint MvCommerce


            > This works for me. The .pem file should be located in a subdirectory in
            > your root data directory. The sub should be called LinkPoint - I'm not
            > completely certain on this one, but I >think< that's the one I use. I
            > havent' cleaned up the code, so there are variables that I used in
            > there, but I think this will give you a good starting point.
            >
            > Scot
            > <A HREF ="http://www.scotsscripts.com">http://www.scotsscripts.com</A>
            >
            > <MvIF EXPR = "{g.payment_type EQ 'linkpoint'}">
            >
            > <MvASSIGN NAME = "l.order_bname" VALUE = "{ g.order_bname }">
            > <MvASSIGN NAME = "l.order_sname" VALUE = "{ g.order_bname }">
            > <MvASSIGN NAME = "l.order_baddr1" VALUE = "{ g.req_addr }">
            > <MvASSIGN NAME = "l.order_saddr1" VALUE = "{ g.req_addr }">
            > <MvASSIGN NAME = "l.order_bzip" VALUE = "{ g.req_zip }">
            > <MvASSIGN NAME = "l.order_szip" VALUE = "{ g.req_zip }">
            > <MvASSIGN NAME = "l.req_zip" VALUE = "{ g.req_zip }">
            > <MvASSIGN NAME = "l.req_addr" VALUE = "{ g.req_addr }">
            > <MvASSIGN NAME = "l.order_bcompany" VALUE = "{ g.order_bcompany }">
            > <MvASSIGN NAME = "l.order_bcity" VALUE = "{ g.order_bcity}">
            > <MvASSIGN NAME = "l.order_scity" VALUE = "{ g.order_bcity}">
            > <MvASSIGN NAME = "l.order_bstate" VALUE = "{ g.order_bstate }">
            > <MvASSIGN NAME = "l.order_sstate" VALUE = "{ g.order_bstate }">
            > <MvASSIGN NAME = "l.order_bcountry" VALUE = "{ g.order_bcountry}">
            > <MvASSIGN NAME = "l.order_scountry" VALUE = "{ g.order_bcountry}">
            > <MvASSIGN NAME = "l.order_phone" VALUE = "{ g.order_phone}">
            > <MvASSIGN NAME = "l.req_email" VALUE = "{ g.req_email}">
            > <MvASSIGN NAME = "l.order_fax" VALUE = "{ g.order_fax}">
            > <MvASSIGN NAME = "l.order_shipping" VALUE = "{ g.order_shipping}">
            >
            > <MvIF EXPRESSION = "{tolower(g.order_bstate) EQ tolower(g.tax_state)}">
            > <MvASSIGN NAME = "l.order_tax" VALUE = "{ (g.tax * .01 * l.total)
            > ROUND 2}">
            > <MvELSE>
            > <MvASSIGN NAME = "l.order_tax" VALUE = "{ 0 }">
            > </MvIF>
            >
            > <MvASSIGN NAME = "l.order_subtotal" VALUE = "{ g.order_subtotal}">
            > <MvASSIGN NAME = "l.order_comments" VALUE = "{ g.order_comments}">
            > <MvASSIGN NAME = "l.req_cardnumber" VALUE = "{ g.req_cardnumber}">
            > <MvASSIGN NAME = "l.req_expmonth" VALUE = "{ g.req_expmonth}">
            > <MvASSIGN NAME = "l.req_expyear" VALUE = "{ g.req_expyear}">
            > <MvASSIGN NAME = "g.req_chargetotal" VALUE = "{ g.total }">
            >
            > <MvASSIGN NAME = "l.fields" VALUE = "order_bname, order_bcompany,
            > order_baddr1, order_bcity, order_bstate, order_bzip, order_bcountry,
            > order_sname, order_saddr1, order_scity, order_sstate, order_szip,
            > order_scountry, order_phone, order_fax, order_total, order_shipping,
            > order_tax, order_subtotal, order_comments, req_cardnumber, req_expmonth,
            > req_expyear, req_chargetotal, req_zip, req_addr, req_email,
            > req_configfile, req_chargetype, req_keyfile, req_host, req_port,
            > req_result">
            >
            >
            > <MvASSIGN NAME = "l.req_configfile" VALUE = "{ '600410' }">
            > <MvASSIGN NAME = "l.req_chargetype" VALUE = "SALE">
            > <MvASSIGN NAME = "l.req_keyfile" VALUE = "{ 'xxx.pem' }">
            > <MvASSIGN NAME = "l.req_host" VALUE = "{ 'secure.linkpt.net' }">
            > <MvASSIGN NAME = "l.req_port" VALUE = "{ '1139' }">
            >
            >
            > <MvCOMMERCE METAMETHOD = "LinkPoint" FIELDS = "{ l.fields }">
            > <MvIF EXPR = "{s.ch_approved EQ 'APPROVED'}">
            > <MvASSIGN NAME = "l.success" VALUE = "{ 1 }">
            >


            > <MvELSE>
            > Your transaction has not been approved. Please go back and verify
            > your information.
            >


            > Transaction Error Message: <MvEVAL EXPRESSION = "{ch_error}">
            > </MvIF>
            > </MvCOMMERCE>
            > </MvIF>
            > </MvIF>
            >
            >
            > Webnician wrote:
            > > Can someone please point me to a reference, explaining the fields used
            in
            > > the MvCommerce tag for Linkpoint. I've looked for several hours on the
            > > Linkpoint site, on the Miva site, and on the message boards. I've
            downloaded
            > > about 25 PDF's, explaining everything from creating API's to using the
            UPS
            > > library.
            > >
            > > I'm sure the developers didn't slave over a commerce library without
            > > recording the how-to's along the way. Why is it such a secret?
            > >
            > > Please, oh, please, help me.
            > >
            > >
            > > Bill Stanley
            > > Webnician
            > >
            > >
            > >

            Comment

              #7
              Linkpoint MvCommerce



              During the transaction I'm pretty sure it needs to be in a directory
              called LinkPoint (not sure if it's case sensitive).

              For security reasons, you would normally store it encrypted in a
              database and then export it when used and delete the export file when
              you are finished. That's basically how the merchant linkpoint module
              does it.

              Patrick Locke wrote:
              > In the code I find this line
              >
              > <MvASSIGN NAME = "l.req_keyfile" VALUE = "{ 'xxx.pem' }">
              >
              > I understand that I get this file from linkpoint, but where do I save it?
              > Data Directory? HTML Directory? Certificates Directory?
              >
              > TIA
              > Patrick
              >
              > ----- Original Message -----
              > From: "Scot Ranney" <[email protected]>
              > To: "Patrick Locke" <[email protected]>
              > Cc: "Miva Users" <[email protected]>
              > Sent: Friday, January 14, 2005 10:43 AM
              > Subject: Re: [meu] Linkpoint MvCommerce
              >
              >
              >
              >>The way linkpoint works is that some of the variables are required, and
              >>others are not. The ones that are required as far as I remember start
              >>with the "req_" string. It's just a way to keep in mind which variables
              >>you definitely need. The other ones are also important if the linkpoint
              >>account in question uses various types of anti-fraud checking such as
              >>the billing address fields.
              >>
              >>I originally figured this out by looking at the linkpoint payment module
              >>that came with uncompiled versions of Merchant.
              >>
              >>Scot
              >>
              >>
              >><A HREF ="http://www.scotsscripts.com">http://www.scotsscripts.com</A>
              >>
              >>
              >>Patrick Locke wrote:
              >>
              >>>This post I found from a while back along with another. Both use req_
              >>>beforethe variable name for some variables and this example uses order_
              >>>before some other fields. Are these prefixes required? I have never
              >
              > delt
              >
              >>>with linkpoint before and their API uses just the field name no req_ or
              >>>order_ prefix. Any suggestions or links to other documnetation would be
              >>>appreciated. BTW this is for a NON-Merchant Application.
              >>>
              >>>TIA
              >>>Patrick
              >>>----- Original Message -----
              >>>From: "Scot Ranney" <[email protected]>
              >>>To: "Webnician" <[email protected]>
              >>>Cc: "Miva Users" <[email protected]>
              >>>Sent: Thursday, October 07, 2004 2:41 PM
              >>>Subject: Re: [meu] Linkpoint MvCommerce
              >>>
              >>>
              >>>
              >>>
              >>>>This works for me. The .pem file should be located in a subdirectory in
              >>>>your root data directory. The sub should be called LinkPoint - I'm not
              >>>>completely certain on this one, but I >think< that's the one I use. I
              >>>>havent' cleaned up the code, so there are variables that I used in
              >>>>there, but I think this will give you a good starting point.
              >>>>
              >>>>Scot
              >>>><A HREF ="http://www.scotsscripts.com">http://www.scotsscripts.com</A>
              >>>>
              >>>><MvIF EXPR = "{g.payment_type EQ 'linkpoint'}">
              >>>>
              >>>><MvASSIGN NAME = "l.order_bname" VALUE = "{ g.order_bname }">
              >>>><MvASSIGN NAME = "l.order_sname" VALUE = "{ g.order_bname }">
              >>>><MvASSIGN NAME = "l.order_baddr1" VALUE = "{ g.req_addr }">
              >>>><MvASSIGN NAME = "l.order_saddr1" VALUE = "{ g.req_addr }">
              >>>><MvASSIGN NAME = "l.order_bzip" VALUE = "{ g.req_zip }">
              >>>><MvASSIGN NAME = "l.order_szip" VALUE = "{ g.req_zip }">
              >>>><MvASSIGN NAME = "l.req_zip" VALUE = "{ g.req_zip }">
              >>>><MvASSIGN NAME = "l.req_addr" VALUE = "{ g.req_addr }">
              >>>><MvASSIGN NAME = "l.order_bcompany" VALUE = "{ g.order_bcompany }">
              >>>><MvASSIGN NAME = "l.order_bcity" VALUE = "{ g.order_bcity}">
              >>>><MvASSIGN NAME = "l.order_scity" VALUE = "{ g.order_bcity}">
              >>>><MvASSIGN NAME = "l.order_bstate" VALUE = "{ g.order_bstate }">
              >>>><MvASSIGN NAME = "l.order_sstate" VALUE = "{ g.order_bstate }">
              >>>><MvASSIGN NAME = "l.order_bcountry" VALUE = "{ g.order_bcountry}">
              >>>><MvASSIGN NAME = "l.order_scountry" VALUE = "{ g.order_bcountry}">
              >>>><MvASSIGN NAME = "l.order_phone" VALUE = "{ g.order_phone}">
              >>>><MvASSIGN NAME = "l.req_email" VALUE = "{ g.req_email}">
              >>>><MvASSIGN NAME = "l.order_fax" VALUE = "{ g.order_fax}">
              >>>><MvASSIGN NAME = "l.order_shipping" VALUE = "{ g.order_shipping}">
              >>>>
              >>>><MvIF EXPRESSION = "{tolower(g.order_bstate) EQ tolower(g.tax_state)}">
              >>>><MvASSIGN NAME = "l.order_tax" VALUE = "{ (g.tax * .01 * l.total)
              >>>>ROUND 2}">
              >>>><MvELSE>
              >>>><MvASSIGN NAME = "l.order_tax" VALUE = "{ 0 }">
              >>>></MvIF>
              >>>>
              >>>><MvASSIGN NAME = "l.order_subtotal" VALUE = "{ g.order_subtotal}">
              >>>><MvASSIGN NAME = "l.order_comments" VALUE = "{ g.order_comments}">
              >>>><MvASSIGN NAME = "l.req_cardnumber" VALUE = "{ g.req_cardnumber}">
              >>>><MvASSIGN NAME = "l.req_expmonth" VALUE = "{ g.req_expmonth}">
              >>>><MvASSIGN NAME = "l.req_expyear" VALUE = "{ g.req_expyear}">
              >>>><MvASSIGN NAME = "g.req_chargetotal" VALUE = "{ g.total }">
              >>>>
              >>>><MvASSIGN NAME = "l.fields" VALUE = "order_bname, order_bcompany,
              >>>>order_baddr1, order_bcity, order_bstate, order_bzip, order_bcountry,
              >>>>order_sname, order_saddr1, order_scity, order_sstate, order_szip,
              >>>>order_scountry, order_phone, order_fax, order_total, order_shipping,
              >>>>order_tax, order_subtotal, order_comments, req_cardnumber, req_expmonth,
              >>>>req_expyear, req_chargetotal, req_zip, req_addr, req_email,
              >>>>req_configfile, req_chargetype, req_keyfile, req_host, req_port,
              >>>>req_result">
              >>>>
              >>>>
              >>>><MvASSIGN NAME = "l.req_configfile" VALUE = "{ '600410' }">
              >>>><MvASSIGN NAME = "l.req_chargetype" VALUE = "SALE">
              >>>><MvASSIGN NAME = "l.req_keyfile" VALUE = "{ 'xxx.pem' }">
              >>>><MvASSIGN NAME = "l.req_host" VALUE = "{ 'secure.linkpt.net' }">
              >>>><MvASSIGN NAME = "l.req_port" VALUE = "{ '1139' }">
              >>>>
              >>>>
              >>>><MvCOMMERCE METAMETHOD = "LinkPoint" FIELDS = "{ l.fields }">
              >>>><MvIF EXPR = "{s.ch_approved EQ 'APPROVED'}">
              >>>><MvASSIGN NAME = "l.success" VALUE = "{ 1 }">
              >>>>


              >>>><MvELSE>
              >>>>Your transaction has not been approved. Please go back and verify
              >>>>your information.
              >>>>


              >>>>Transaction Error Message: <MvEVAL EXPRESSION = "{ch_error}">
              >>>></MvIF>
              >>>></MvCOMMERCE>
              >>>></MvIF>
              >>>></MvIF>
              >>>>
              >>>>
              >>>>Webnician wrote:
              >>>>
              >>>>
              >>>>>Can someone please point me to a reference, explaining the fields used
              >>>
              >>>in
              >>>
              >>>
              >>>>>the MvCommerce tag for Linkpoint. I've looked for several hours on the
              >>>>>Linkpoint site, on the Miva site, and on the message boards. I've
              >>>
              >>>downloaded
              >>>
              >>>
              >>>>>about 25 PDF's, explaining everything from creating API's to using the
              >>>
              >>>UPS
              >>>
              >>>
              >>>>>library.
              >>>>>
              >>>>>I'm sure the developers didn't slave over a commerce library without
              >>>>>recording the how-to's along the way. Why is it such a secret?
              >>>>>
              >>>>>Please, oh, please, help me.
              >>>>>
              >>>>>
              >>>>>Bill Stanley
              >>>>>Webnician
              >>>>>
              >>>>>
              >>>>>

              Comment

                #8
                Linkpoint MvCommerce



                In the code I find this line

                <MvASSIGN NAME = "l.req_keyfile" VALUE = "{ 'xxx.pem' }">

                I understand that I get this file from linkpoint, but where do I save it?
                Data Directory? HTML Directory? Certificates Directory?

                TIA
                Patrick

                ----- Original Message -----
                From: "Scot Ranney" <[email protected]>
                To: "Patrick Locke" <[email protected]>
                Cc: "Miva Users" <[email protected]>
                Sent: Friday, January 14, 2005 10:43 AM
                Subject: Re: [meu] Linkpoint MvCommerce


                > The way linkpoint works is that some of the variables are required, and
                > others are not. The ones that are required as far as I remember start
                > with the "req_" string. It's just a way to keep in mind which variables
                > you definitely need. The other ones are also important if the linkpoint
                > account in question uses various types of anti-fraud checking such as
                > the billing address fields.
                >
                > I originally figured this out by looking at the linkpoint payment module
                > that came with uncompiled versions of Merchant.
                >
                > Scot
                >
                >
                > <A HREF ="http://www.scotsscripts.com">http://www.scotsscripts.com</A>
                >
                >
                > Patrick Locke wrote:
                > > This post I found from a while back along with another. Both use req_
                > > beforethe variable name for some variables and this example uses order_
                > > before some other fields. Are these prefixes required? I have never
                delt
                > > with linkpoint before and their API uses just the field name no req_ or
                > > order_ prefix. Any suggestions or links to other documnetation would be
                > > appreciated. BTW this is for a NON-Merchant Application.
                > >
                > > TIA
                > > Patrick
                > > ----- Original Message -----
                > > From: "Scot Ranney" <[email protected]>
                > > To: "Webnician" <[email protected]>
                > > Cc: "Miva Users" <[email protected]>
                > > Sent: Thursday, October 07, 2004 2:41 PM
                > > Subject: Re: [meu] Linkpoint MvCommerce
                > >
                > >
                > >
                > >>This works for me. The .pem file should be located in a subdirectory in
                > >>your root data directory. The sub should be called LinkPoint - I'm not
                > >>completely certain on this one, but I >think< that's the one I use. I
                > >>havent' cleaned up the code, so there are variables that I used in
                > >>there, but I think this will give you a good starting point.
                > >>
                > >>Scot
                > >><A HREF ="http://www.scotsscripts.com">http://www.scotsscripts.com</A>
                > >>
                > >><MvIF EXPR = "{g.payment_type EQ 'linkpoint'}">
                > >>
                > >><MvASSIGN NAME = "l.order_bname" VALUE = "{ g.order_bname }">
                > >><MvASSIGN NAME = "l.order_sname" VALUE = "{ g.order_bname }">
                > >><MvASSIGN NAME = "l.order_baddr1" VALUE = "{ g.req_addr }">
                > >><MvASSIGN NAME = "l.order_saddr1" VALUE = "{ g.req_addr }">
                > >><MvASSIGN NAME = "l.order_bzip" VALUE = "{ g.req_zip }">
                > >><MvASSIGN NAME = "l.order_szip" VALUE = "{ g.req_zip }">
                > >><MvASSIGN NAME = "l.req_zip" VALUE = "{ g.req_zip }">
                > >><MvASSIGN NAME = "l.req_addr" VALUE = "{ g.req_addr }">
                > >><MvASSIGN NAME = "l.order_bcompany" VALUE = "{ g.order_bcompany }">
                > >><MvASSIGN NAME = "l.order_bcity" VALUE = "{ g.order_bcity}">
                > >><MvASSIGN NAME = "l.order_scity" VALUE = "{ g.order_bcity}">
                > >><MvASSIGN NAME = "l.order_bstate" VALUE = "{ g.order_bstate }">
                > >><MvASSIGN NAME = "l.order_sstate" VALUE = "{ g.order_bstate }">
                > >><MvASSIGN NAME = "l.order_bcountry" VALUE = "{ g.order_bcountry}">
                > >><MvASSIGN NAME = "l.order_scountry" VALUE = "{ g.order_bcountry}">
                > >><MvASSIGN NAME = "l.order_phone" VALUE = "{ g.order_phone}">
                > >><MvASSIGN NAME = "l.req_email" VALUE = "{ g.req_email}">
                > >><MvASSIGN NAME = "l.order_fax" VALUE = "{ g.order_fax}">
                > >><MvASSIGN NAME = "l.order_shipping" VALUE = "{ g.order_shipping}">
                > >>
                > >><MvIF EXPRESSION = "{tolower(g.order_bstate) EQ tolower(g.tax_state)}">
                > >><MvASSIGN NAME = "l.order_tax" VALUE = "{ (g.tax * .01 * l.total)
                > >>ROUND 2}">
                > >><MvELSE>
                > >><MvASSIGN NAME = "l.order_tax" VALUE = "{ 0 }">
                > >></MvIF>
                > >>
                > >><MvASSIGN NAME = "l.order_subtotal" VALUE = "{ g.order_subtotal}">
                > >><MvASSIGN NAME = "l.order_comments" VALUE = "{ g.order_comments}">
                > >><MvASSIGN NAME = "l.req_cardnumber" VALUE = "{ g.req_cardnumber}">
                > >><MvASSIGN NAME = "l.req_expmonth" VALUE = "{ g.req_expmonth}">
                > >><MvASSIGN NAME = "l.req_expyear" VALUE = "{ g.req_expyear}">
                > >><MvASSIGN NAME = "g.req_chargetotal" VALUE = "{ g.total }">
                > >>
                > >><MvASSIGN NAME = "l.fields" VALUE = "order_bname, order_bcompany,
                > >>order_baddr1, order_bcity, order_bstate, order_bzip, order_bcountry,
                > >>order_sname, order_saddr1, order_scity, order_sstate, order_szip,
                > >>order_scountry, order_phone, order_fax, order_total, order_shipping,
                > >>order_tax, order_subtotal, order_comments, req_cardnumber, req_expmonth,
                > >>req_expyear, req_chargetotal, req_zip, req_addr, req_email,
                > >>req_configfile, req_chargetype, req_keyfile, req_host, req_port,
                > >>req_result">
                > >>
                > >>
                > >><MvASSIGN NAME = "l.req_configfile" VALUE = "{ '600410' }">
                > >><MvASSIGN NAME = "l.req_chargetype" VALUE = "SALE">
                > >><MvASSIGN NAME = "l.req_keyfile" VALUE = "{ 'xxx.pem' }">
                > >><MvASSIGN NAME = "l.req_host" VALUE = "{ 'secure.linkpt.net' }">
                > >><MvASSIGN NAME = "l.req_port" VALUE = "{ '1139' }">
                > >>
                > >>
                > >><MvCOMMERCE METAMETHOD = "LinkPoint" FIELDS = "{ l.fields }">
                > >><MvIF EXPR = "{s.ch_approved EQ 'APPROVED'}">
                > >><MvASSIGN NAME = "l.success" VALUE = "{ 1 }">
                > >>


                > >><MvELSE>
                > >>Your transaction has not been approved. Please go back and verify
                > >>your information.
                > >>


                > >>Transaction Error Message: <MvEVAL EXPRESSION = "{ch_error}">
                > >></MvIF>
                > >></MvCOMMERCE>
                > >></MvIF>
                > >></MvIF>
                > >>
                > >>
                > >>Webnician wrote:
                > >>
                > >>>Can someone please point me to a reference, explaining the fields used
                > >
                > > in
                > >
                > >>>the MvCommerce tag for Linkpoint. I've looked for several hours on the
                > >>>Linkpoint site, on the Miva site, and on the message boards. I've
                > >
                > > downloaded
                > >
                > >>>about 25 PDF's, explaining everything from creating API's to using the
                > >
                > > UPS
                > >
                > >>>library.
                > >>>
                > >>>I'm sure the developers didn't slave over a commerce library without
                > >>>recording the how-to's along the way. Why is it such a secret?
                > >>>
                > >>>Please, oh, please, help me.
                > >>>
                > >>>
                > >>>Bill Stanley
                > >>>Webnician
                > >>>
                > >>>
                > >>>

                Comment

                Previous template Next
                Working...
                X