The Transaction Service provides clients transactional functionalities such as deposits, claims, and viewing transaction history. This allows Administrators the ability to integrate their existing systems with BPS in real time with the flex accounts POS system. This version provides enhanced methods that take request objects modified to include Plan Id. This provides for Employee Portability.

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

• DepositPayroll
  This method is used to deposit funds to an employee’s benefit account by way of a payroll deposit.
• DepositPrefunded
  This method is used to deposit funds to an employee’s benefit account by way of prefunded deposits.
• GetDisbursableBalanceAffectingTotal
  This method provides the most up to date disbursable balance affecting total available in BPS at the time of the request.
• GetDisbursableBalanceAffectingTxns
  This method provides the most up to date disbursable balance affecting transaction data available in BPS at the time of the request.
• GetTransactionDetails
  This method is used to retrieve a cardholder’s transactional information for a specific transaction.
• GetTransactionHistory
  This method is used to retrieve a cardholder’s transactional information for an employee’s benefit account.
• OtherDeposit
  This method is used to do a special / other deposit to an employee’s benefit account. This is basically an employer deposit made to employee's account like incentives or interest.
• SubmitManualClaim
  When processing manual claims (non-POS claims), you must import the claim into BPS to verify available funds prior to cutting a check to the employee.
• SubmitManualRefund
  When processing manual refunds (non-POS refund), you must import the claim into BPS to verify available funds prior to cutting a check to the employee.
• SubmitRxManualClaim
  The SubmitRxManualClaim method should be call when a transaction is required against the cardholder’s FSA account. If the transaction is successful, the method will return a status code of (P), paid, and a denial reason code of 0. If the transaction was partially paid, the method will return a status code of (P), paid, and a denial reason code of 1074. If the transaction had been submitted before, but has not been completed yet, the method will return a status code of (I), in progress, and a denial reason code of 11055. Finally, if the transaction had already been submitted the method will return the original status code and denial reason code with the addition of a warning in the SOAP header which indicates a duplicate attempt to submit the transaction 101006.
• VoidRxManualClaim
  The VoidRxManualClaim method should be call when a transaction needs to be reversed by the pharmacy. Transactions can be voided within 30 days. If the transaction has not been completed yet, the method will return a status code of (I), in progress, and a denial reason code of 11055. If the transaction either can not be found within the system or had original failed, the method will return a status code of (R), rejected with a denial reason code of 100537. If the transaction was successfully voided (reversed), then the method will return a status code of (V), voided, and a denial reason code of 0 (success). Finally, if the transaction had already been voided, the method will return a status code of (V), voided, and a denial reason code of 0 (success) with the addition of a warning in the SOAP header which indicates a duplicate attempt to void the transaction 101006.