Payment Resources International provides this Credit Card Processing Web Service for its customers.
In order to process a credit card you will need to have a valid Merchant Account with us.
However, two methods below can be tested without supplying a MerchantID nor RegKey.
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.
For more information on this service go to Processing Credit Cards

The following operations are supported. For a formal definition, please review the Service Description.

• BlindCredit
  For credit card credit processing. Required Fields are MerchantID, RegKey, Amount, CardNumber, Expiration. TransID is the TransID of the original sale. A TransID will be returned when a Credit Card Sale is authorized with WebMethod CreditCardSale. RefID is for your determined use
• CCAutoRefundorVoidSuspectedFraud
  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 authorized with WebMethod CreditCardAutoRefundorVoid. A CreditID will be returned when a Credit Card Credit is authorized.
• CCSale
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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, GoodsSoldInd, InstallmentNum, InstallmentOf, MCC, MerchZIP, PaymentDesc, StoreNum, eCommerce, MerchCustPNum, and TaxIndicator are optional fields.
• CCSaleGoodsSold
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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, GoodsSoldInd, InstallmentNum, InstallmentOf, MCC, MerchZIP, PaymentDesc, StoreNum, eCommerce, MerchCustPNum, and TaxIndicator are optional fields.
• CCSaleMobile
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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, GoodsSoldInd, InstallmentNum, InstallmentOf, MCC, MerchZIP, PaymentDesc, StoreNum, eCommerce, MerchCustPNum, TaxIndicator are optional fields. IsMobileDevice can be 'N' or 'Y' to indicate a mobile POS device. MobileDeviceType is a 2 character identifier in the format 00-99
• CCSaleMobileRSP
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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, GoodsSoldInd, InstallmentNum, InstallmentOf, MCC, MerchZIP, PaymentDesc, StoreNum, eCommerce, MerchCustPNum, TaxIndicator are optional fields. IsMobileDevice can be 'N' or 'Y' to indicate a mobile POS device. MobileDeviceType is a 2 character identifier in the format 00-99
• CCSaleRSP
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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, GoodsSoldInd, InstallmentNum, InstallmentOf, MCC, MerchZIP, PaymentDesc, StoreNum, eCommerce, MerchCustPNum, and TaxIndicator are optional fields.
• CCSaleRSPGoodsSold
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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, GoodsSoldInd, InstallmentNum, InstallmentOf, MCC, MerchZIP, PaymentDesc, StoreNum, eCommerce, MerchCustPNum, and TaxIndicator are optional fields.
• CCSaleRSPTransit
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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, TransitTypeIndicator, and TransitMode Indicator are optional fields. The Possible values for TransitTypeIndicator is between 01-99 and TransitModeIndicator is between 00-99
• CCSaleRSPWithShipping
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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, GoodsSoldInd, InstallmentNum, InstallmentOf, MCC, MerchZIP, PaymentDesc, StoreNum, eCommerce, MerchCustPNum, and TaxIndicator are optional fields.
• CCVoidCreditSuspectedFraud
  For voiding or cancelling a refund (full or partial) or blind credit that has been sent out for authorization. Required Fields are MerchantID, RegKey CreditID and SuspectFraud. CreditID is the CreditID of the refund or credit that was sent for authorization. A refund or credit can only be voided if it has not been settled. Payment Resources settles all transactions approximately 9PM Pacific Time. To determine if a Credit is voidable (ie not settled yet) you can use the WebMethod GetBankCardCreditStatus.
• CCVoidSaleSuspectedFraud
  For voiding a credit card sale or Debit Card Sale. Required Fields are MerchantID, RegKey and TransID. TransID is the TransID of the original sale. Possible values for SuspectFraud are Y (TRUE) or N (FALSE). A TransID will be returned when a Credit Card Sale is authorized 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.
• CloseBatch
  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 authorized 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 cannot exceed the original amount.
• CreditCardAutoRefundorVoid
  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 authorized with WebMethod CreditCardAutoRefundorVoid. A CreditID will be returned when a Credit Card Credit is authorized.
• CreditCardAutoSettle
  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 authorized with WebMethod CreditCardSale. RefID is for your determined use. Credit Amounts cannot exceed the original sale amount.
• CreditCardCredit
  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 authorized with WebMethod CreditCardSale. RefID is for your determined use. Credit Amounts cannot exceed the original sale amount.
• CreditCardSale
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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.
• CreditCardSaleAll
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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.
  For corporate purchase card additional required Fields are SaleTaxAmount, PONumber.
  CVV2, Address, ZipCode, UserID are optional fields. UsrDef1, UsrDef2, UsrDef3, UsrDef4 are reserved for feature use
• CreditCardSaleAllRSP
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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.
  For corporate purchase card additional required Fields are SaleTaxAmount, PONumber.
  CVV2, Address, ZipCode, UserID are optional fields. UsrDef1, UsrDef2, UsrDef3, UsrDef4 are reserved for feature use
• CreditCardSaleAllTransit
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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.
  For corporate purchase card additional required Fields are SaleTaxAmount, PONumber.
  CVV2, Address, ZipCode, UserID, TransitTypeIndicator and TransitModeIndicator are optional fields. The Possible values for TransitTypeIndicator is between 01-99 and TransitModeIndicator is between 00-99UsrDef1, UsrDef2, UsrDef3, UsrDef4 are reserved for feature use
• CreditCardSaleUser
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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.
• CreditCardVoiceAuthorization
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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.
• CreditCardVoiceAuthorizationUser
  For credit card debit authorizations. Required Fields are MerchantID, RegKey, Amount, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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.
• DebitCardCredit
  Method has been deprecated and is not supported. Do not use.
• DebitCardSale
  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
• DebitCardSaleTransit
  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. TransitTypeIndicator and TransitMode Indicator are optional fields and Possible values for TransitTypeIndicator is 01-99 and Possible values for TransitModeIndicator is 00-99.UsrDef is reserved for feature use
• GetBankCardCreditStatus
  For determining the current status of a credit card credit
• GetBankCardDebitStatus
  For determining the current status of a credit card sale.
• GetTransactionDetails
  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 e.g. 01/12/09 or 01/12/2009.
• ReleaseBatch
  For credit card settle processing. Required Fields are MerchantID and RegKey
• VerifyAccount
  For credit card Account Verifications. Required Fields are MerchantID, RegKey, CardNumber and Expiration. Expiration is in the form mmyy. e.g. 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 and TaxIndicator are optional fields.
• VoidCreditCardSale
  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 authorized 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.
• VoidDebitCardSale
  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 authorized 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.