<font size='4'><a href='http://www.paymentresource.com'>Payment Resources International</a></font> <font size='3'>provides this Credit Card Processing Web Service for its customers. <BR>In order to process a credit card you will need to have a valid Merchant Account with us. <BR>However, two methods below can be tested without supplying a MerchantID nor RegKey.<BR>WebMethods CreditCardSale,CreditCardCredit, and VoidCreditCardSale will return sample results if you leave MerchantID and RegKey blank(you will need to fill in the other fields). CreditCardSale will return a fictitious authorization if the amount is even(ie 2.00,1.02). Otherwise it will return a decline. <BR> For more information on this service go to <a href='CreditCardProcessing.htm'>Processing Credit Cards</a></font> For credit card settle processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use.CreditID is only required for closing batch for Credit. A CreditID will be returned when a Credit Card Credit is authrorized with WebMethod CreditCardCredit.Credit Amounts can not exceed the original amount. For credit card settle processing. Required Fields are MerchantID, RegKey For credit card settle processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use. Credit Amounts can not exceed the original sale amount. For credit card Account Verifications. Required Fields are MerchantID, RegKey, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. CVV2, Address, ZipCode, AuthCharInd, InstallmentNum,InstallmentOf,MCC,MerchZIP,PaymentDesc,StoreNum,eCommerce,MerchCustPNum, TaxIndicator are optional fields. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For debit card authorizations. Required fields are MerchantID, RegKey, Amount, CardNumber, Expiration, EncryptedPIN, SMID, PINFormat, TrackData (always should be Track2).VoucherNumber is required for EBT/FoodStamp transaction.RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. Possible values for PINFormat are (01 = ANSI standard ,02 = PIN length/PIN/fill characters, 03 = PIN/Fill characters).SMID = System Management Information Data Commonly referred to as DUKPT - (Derived Unique Key Per Transaction) is a 12 or 20 character data block containing a Base Derivation Key (BDK) ID, Terminal ID and Transaction Counter.UsrDef is reserved for feature use For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For credit card credit processing. Required Fields are MerchantID, RegKey, Amount, Card Number, Expiration Date. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use For credit card credit processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use. Credit Amounts can not exceed the original sale amount. For Debit card credit processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Debit Card Sale is authrorized with WebMethod DebitCardSale. RefID is for your determined use. Credit Amounts can not exceed the original sale amount. For voiding a credit card sale. Required Fields are MerchantID, RegKey and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. A Credit Card Sale can only be voided if it has not been settled. Payment Resources settles all transactions approximately 9PM Pacific Time. To determine if a transaction is voidable(ie not settled yet) you can use the WebMethod GetBankCardDebitStatus. For voiding a Debit card sale. Required Fields are MerchantID, RegKey and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Debit Card Sale is authrorized with WebMethod DebitCardSale. A Debit Card Sale can only be voided if it has not been settled. Payment Resources settles all transactions approximately 9PM Pacific Time. To determine if a transaction is voidable(ie not settled yet) you can use the WebMethod GetBankCardDebitStatus. For Determining the current status of a credit card sale. For Determining the current status of a credit card credit For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. TrackData is for Swiped Transactions.<br>For corporate purchase card additional required Fields are SaleTaxAmount, PONumber. <br>CVV2, Address, ZipCode, UserID are optional fields.UsrDef1, UsrDef2, UsrDef3, UsrDef4 are reserved for feature use For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. TrackData is for Swiped Transactions.<br>For corporate purchase card additional required Fields are SaleTaxAmount, PONumber. <br>CVV2, Address, ZipCode, UserID are optional fields.UsrDef1, UsrDef2, UsrDef3, UsrDef4 are reserved for feature use For credit card authorizations. Required Fields are MerchantID, RegKey,RefID, PostedDate and Amount. PostedDate is in the form of either MM/DD/YY or MM/DD/YYYY ie 01/12/09 or 01/12/2009. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. CVV2, Address, ZipCode, AuthCharInd, InstallmentNum,InstallmentOf,MCC,MerchZIP,PaymentDesc,StoreNum,eCommerce,MerchCustPNum, TaxIndicator are optional fields. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. CVV2, Address, ZipCode, AuthCharInd, InstallmentNum,InstallmentOf,MCC,MerchZIP,PaymentDesc,StoreNum,eCommerce,MerchCustPNum, TaxIndicator are optional fields. For credit card Auto Refund or Void Required Fields are MerchantID, RegKey and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardAutoRefundorVoid. A CreditID will be returned when a Credit Card Credit is authorized. For credit card settle processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use.CreditID is only required for closing batch for Credit. A CreditID will be returned when a Credit Card Credit is authrorized with WebMethod CreditCardCredit.Credit Amounts can not exceed the original amount. For credit card settle processing. Required Fields are MerchantID, RegKey For credit card settle processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use. Credit Amounts can not exceed the original sale amount. For credit card Account Verifications. Required Fields are MerchantID, RegKey, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. CVV2, Address, ZipCode, AuthCharInd, InstallmentNum,InstallmentOf,MCC,MerchZIP,PaymentDesc,StoreNum,eCommerce,MerchCustPNum, TaxIndicator are optional fields. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For debit card authorizations. Required fields are MerchantID, RegKey, Amount, CardNumber, Expiration, EncryptedPIN, SMID, PINFormat, TrackData (always should be Track2).VoucherNumber is required for EBT/FoodStamp transaction.RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. Possible values for PINFormat are (01 = ANSI standard ,02 = PIN length/PIN/fill characters, 03 = PIN/Fill characters).SMID = System Management Information Data Commonly referred to as DUKPT - (Derived Unique Key Per Transaction) is a 12 or 20 character data block containing a Base Derivation Key (BDK) ID, Terminal ID and Transaction Counter.UsrDef is reserved for feature use For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For credit card credit processing. Required Fields are MerchantID, RegKey, Amount, Card Number, Expiration Date. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use For credit card credit processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use. Credit Amounts can not exceed the original sale amount. For Debit card credit processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Debit Card Sale is authrorized with WebMethod DebitCardSale. RefID is for your determined use. Credit Amounts can not exceed the original sale amount. For voiding a credit card sale. Required Fields are MerchantID, RegKey and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. A Credit Card Sale can only be voided if it has not been settled. Payment Resources settles all transactions approximately 9PM Pacific Time. To determine if a transaction is voidable(ie not settled yet) you can use the WebMethod GetBankCardDebitStatus. For voiding a Debit card sale. Required Fields are MerchantID, RegKey and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Debit Card Sale is authrorized with WebMethod DebitCardSale. A Debit Card Sale can only be voided if it has not been settled. Payment Resources settles all transactions approximately 9PM Pacific Time. To determine if a transaction is voidable(ie not settled yet) you can use the WebMethod GetBankCardDebitStatus. For Determining the current status of a credit card sale. For Determining the current status of a credit card credit For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. TrackData is for Swiped Transactions.<br>For corporate purchase card additional required Fields are SaleTaxAmount, PONumber. <br>CVV2, Address, ZipCode, UserID are optional fields.UsrDef1, UsrDef2, UsrDef3, UsrDef4 are reserved for feature use For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. TrackData is for Swiped Transactions.<br>For corporate purchase card additional required Fields are SaleTaxAmount, PONumber. <br>CVV2, Address, ZipCode, UserID are optional fields.UsrDef1, UsrDef2, UsrDef3, UsrDef4 are reserved for feature use For credit card authorizations. Required Fields are MerchantID, RegKey,RefID, PostedDate and Amount. PostedDate is in the form of either MM/DD/YY or MM/DD/YYYY ie 01/12/09 or 01/12/2009. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. CVV2, Address, ZipCode, AuthCharInd, InstallmentNum,InstallmentOf,MCC,MerchZIP,PaymentDesc,StoreNum,eCommerce,MerchCustPNum, TaxIndicator are optional fields. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. CVV2, Address, ZipCode, AuthCharInd, InstallmentNum,InstallmentOf,MCC,MerchZIP,PaymentDesc,StoreNum,eCommerce,MerchCustPNum, TaxIndicator are optional fields. For credit card Auto Refund or Void Required Fields are MerchantID, RegKey and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardAutoRefundorVoid. A CreditID will be returned when a Credit Card Credit is authorized. For credit card settle processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use.CreditID is only required for closing batch for Credit. A CreditID will be returned when a Credit Card Credit is authrorized with WebMethod CreditCardCredit.Credit Amounts can not exceed the original amount. For credit card settle processing. Required Fields are MerchantID, RegKey For credit card settle processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use. Credit Amounts can not exceed the original sale amount. For credit card Account Verifications. Required Fields are MerchantID, RegKey, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. CVV2, Address, ZipCode, AuthCharInd, InstallmentNum,InstallmentOf,MCC,MerchZIP,PaymentDesc,StoreNum,eCommerce,MerchCustPNum, TaxIndicator are optional fields. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For debit card authorizations. Required fields are MerchantID, RegKey, Amount, CardNumber, Expiration, EncryptedPIN, SMID, PINFormat, TrackData (always should be Track2).VoucherNumber is required for EBT/FoodStamp transaction.RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. Possible values for PINFormat are (01 = ANSI standard ,02 = PIN length/PIN/fill characters, 03 = PIN/Fill characters).SMID = System Management Information Data Commonly referred to as DUKPT - (Derived Unique Key Per Transaction) is a 12 or 20 character data block containing a Base Derivation Key (BDK) ID, Terminal ID and Transaction Counter.UsrDef is reserved for feature use For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it here. TrackData is for Swiped Transactions. For credit card credit processing. Required Fields are MerchantID, RegKey, Amount, Card Number, Expiration Date. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use For credit card credit processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. RefID is for your determined use. Credit Amounts can not exceed the original sale amount. For Debit card credit processing. Required Fields are MerchantID, RegKey, Amount and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Debit Card Sale is authrorized with WebMethod DebitCardSale. RefID is for your determined use. Credit Amounts can not exceed the original sale amount. For voiding a credit card sale. Required Fields are MerchantID, RegKey and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardSale. A Credit Card Sale can only be voided if it has not been settled. Payment Resources settles all transactions approximately 9PM Pacific Time. To determine if a transaction is voidable(ie not settled yet) you can use the WebMethod GetBankCardDebitStatus. For voiding a Debit card sale. Required Fields are MerchantID, RegKey and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Debit Card Sale is authrorized with WebMethod DebitCardSale. A Debit Card Sale can only be voided if it has not been settled. Payment Resources settles all transactions approximately 9PM Pacific Time. To determine if a transaction is voidable(ie not settled yet) you can use the WebMethod GetBankCardDebitStatus. For Determining the current status of a credit card sale. For Determining the current status of a credit card credit For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. TrackData is for Swiped Transactions.<br>For corporate purchase card additional required Fields are SaleTaxAmount, PONumber. <br>CVV2, Address, ZipCode, UserID are optional fields.UsrDef1, UsrDef2, UsrDef3, UsrDef4 are reserved for feature use For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. TrackData is for Swiped Transactions.<br>For corporate purchase card additional required Fields are SaleTaxAmount, PONumber. <br>CVV2, Address, ZipCode, UserID are optional fields.UsrDef1, UsrDef2, UsrDef3, UsrDef4 are reserved for feature use For credit card authorizations. Required Fields are MerchantID, RegKey,RefID, PostedDate and Amount. PostedDate is in the form of either MM/DD/YY or MM/DD/YYYY ie 01/12/09 or 01/12/2009. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. CVV2, Address, ZipCode, AuthCharInd, InstallmentNum,InstallmentOf,MCC,MerchZIP,PaymentDesc,StoreNum,eCommerce,MerchCustPNum, TaxIndicator are optional fields. For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. ie february 2003 would be 0203. RefID is for your determined use. If you have a unique tracking ID for purchases you might want to place it as RefID. CVV2, Address, ZipCode, AuthCharInd, InstallmentNum,InstallmentOf,MCC,MerchZIP,PaymentDesc,StoreNum,eCommerce,MerchCustPNum, TaxIndicator are optional fields. For credit card Auto Refund or Void Required Fields are MerchantID, RegKey and TransID. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authrorized with WebMethod CreditCardAutoRefundorVoid. A CreditID will be returned when a Credit Card Credit is authorized. <font size='4'><a href='http://www.paymentresource.com'>Payment Resources International</a></font> <font size='3'>provides this Credit Card Processing Web Service for its customers. <BR>In order to process a credit card you will need to have a valid Merchant Account with us. <BR>However, two methods below can be tested without supplying a MerchantID nor RegKey.<BR>WebMethods CreditCardSale,CreditCardCredit, and VoidCreditCardSale will return sample results if you leave MerchantID and RegKey blank(you will need to fill in the other fields). CreditCardSale will return a fictitious authorization if the amount is even(ie 2.00,1.02). Otherwise it will return a decline. <BR> For more information on this service go to <a href='CreditCardProcessing.htm'>Processing Credit Cards</a></font>