Jump to content

Search the Community

Showing results for tags 'oscommerce 2.3.4'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News and Announcements
    • News and Announcements
  • osCommerce Online Merchant v2.x
    • General Support
    • osCommerce Online Merchant Community Bootstrap Edition
    • Add-Ons
  • Development
  • General
    • General Discussions
    • Live Shop Reviews
    • Security
    • Developer Feedback
  • PayPal's Announcements
  • Sage Pay's Announcements
  • Solomono - new level osCommerce templates's Announcements
  • German Community's OSCOM v2.x
  • German Community's Allgemein

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Real Name


Location


Interests


Website

Found 4 results

  1. Has anyone tested this addon? I don't want to change a working site if there are problems with this addon but I do want to implement limited access for certain administrators.
  2. TomB01

    Stripe vs Braintree?

    I'm building a replacement web store based on 2.3.4 (not going to try the upgrade route from 2.2). All of the extra capability over 2.2 is exciting, but it's confusing, too. I've been using simple Paypal for the last 7 years with great success, but would love to start taking credit cards. Both Stripe and Braintree have what I'd like: simple fees per transaction only, no monthly charges or other extras, and credit card acceptance totally contained on my store site - no switching to another site and back again. So, what are the advantages/disadvantages of either one? Is there another one out there that's better given the preferences above? I have noticed that Braintree is already inserting random adds on my regular web surfing, so I'm not sure I like an outfit that appears to be that aggressive with marketing. I only visited their site once!?
  3. AdmiralRedBeard

    Discount Info Type Fields for PayPal Express

    Hi, I'm trying to figure out how to pass the data values from the CCGV and the Reward Points addons to PayPal. In using the sandbox environment, even though the total that is passed may be correct in deducting used discounts, vouchers, points; the discounts are not getting deducted from the total that PayPal is collecting from the customer. So if my sub total is 40.00 and have 10.00 worth of discounts, a total of 30.00 is getting passed and displayed in PayPal. I continue the transaction and go into the sandbox transaction log and find that a total of 40.00 was deducted from my sandbox account. In researching PayPal developer website I found the following for using DiscountInfo fields. How can I incorporate any of this into my 2.3.4 store? DiscountInfoType Fields Describes discount information. Field / Description PAYMENTREQUEST_nREDEEMEDOFFERNAME (Optional) The name of the buyer's wallet item offer redeemed in this transaction, such as, a merchant coupon or a loyalty program card. Character length and limitations: 127 single-byte characters PAYMENTREQUEST_nREDEEMEDOFFERDESCRIPTION xs:string (Optional) Description of the offer redeemed in this transaction, such as, a merchant coupon or a loyalty program. Character length and limitations: 127 single-byte characters PAYMENTREQUEST_nREDEEMEDOFFERAMOUNT (Optional) Amount of the offer redeemed in this transaction. Character length and limitations: Value is typically a positive number which cannot exceed 10,000.00 USD or the per transaction limit for the currency. It includes no currency symbol. Most currencies require two decimal places; the decimal separator must be a period (.), and the optional thousands separator must be a comma (,). Some currencies do not allow decimals. See the currency codes page for details.. PAYMENTREQUEST_nREDEEMEDOFFERTYPE (Optional) Type of the offer redeemed in this transaction. It is one of the following: LOYALTY_CARD MERCHANT_COUPON PAYMENTREQUEST_nREDEEMEDOFFERID xs:string (Optional) Unique ID of the offer redeemed in this transaction or the buyer's loyalty card account number. Character length and limitations: 64 single-byte characters. PAYMENTREQUEST_nREDEEMEDOFFERPOINTSACCRUED (Optional) The number of loyalty points accrued in this transaction. PAYMENTREQUEST_nCUMMULATIVEPOINTSNAME (Optional) The name of the loyalty points program in which the buyer earned points in this transaction. Character length and limitations: 127 single-byte characters PAYMENTREQUEST_nCUMMULATIVEPOINTSDESCRIPTION xs:string (Optional) Description of the loyalty points program. Character length and limitations: 127 single-byte characters PAYMENTREQUEST_nCUMMULATIVEPOINTSTYPE (Optional) Type of discount or loyalty program. It is one of the following: LOYALTY_CARD PAYMENTREQUEST_nCUMMULATIVEPOINTSID xs:string (Optional) Unique ID of the buyer's loyalty points account. Character length and limitations: 64 single-byte characters. PAYMENTREQUEST_nCUMMULATIVEPOINTSACCRUED (Optional) The cummulative number of loyalty points the buyer has accrued. PAYMENTREQUEST_nMERCHANTDATAKEYm (Optional) Key name of a merchant data key-value pair passed with the transaction. You can pass up to 16 key-value pairs (where m is between 0 and 15 inclusive) with each payment, and up to 10 payments in each request (where n is between 0 and 9 inclusive). Character length and limitations: 64 single-byte characters. You can specify up to 10 payments in each request. The character n, in the field name, is the payments array index and should be replaced with an integer between 0 and 9, inclusive. For example, if you are passing only one payment in the request, then replace n with the digit 0. For multiple payments within a single request, you must order the payments sequentially. Note If you are using Digital Goods, you can send only a single payment in each request. This field also allows you to pass an array of information for each payment. Replace the character m, in the field name, with an integer (an array key). The keys must be ordered sequentially, beginning with 0. PAYMENTREQUEST_nMERCHANTDATAVALUEm (Optional) Merchant data value, part of a key-value pair, passed with the transaction. You can pass up to 16 key-value pairs (where m is between 0 and 15 inclusive) with each payment, and up to 10 payments in each request (where n is between 0 and 9 inclusive). Character length and limitations: 8192 single-byte characters. You can specify up to 10 payments in each request. The character n, in the field name, is the payments array index and should be replaced with an integer between 0 and 9, inclusive. For example, if you are passing only one payment in the request, then replace n with the digit 0. For multiple payments within a single request, you must order the payments sequentially. Note If you are using Digital Goods, you can send only a single payment in each request. This field also allows you to pass an array of information for each payment. Replace the character m, in the field name, with an integer (an array key). The keys must be ordered sequentially, beginning with 0.
  4. I am trying to get ccgv to work with osc 2.3.4, and it seems so close to working for me but I seem to be having one issue. If I use a gift certificate and it covers the entire amount then I get to the checkout_confirmation but without any payment method selected (probably intended?) But then when I click to confirm the order, I am trown back to the checkout payment with the message that no payment method has been selected. Does anyone have a clue on how to solve this? I have another issue, which is not a bug but I also use quantity discounts, however it doesn't make sense to have quantity discounts when buying a gift certificate since the quantity discount is also applied when using it. Currently I am without any ideas how to solve this.
×