Jump to content
Sign in to follow this  
AdmiralRedBeard

Discount Info Type Fields for PayPal Express

Recommended Posts

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.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×