Skip to content

Home

Jump to bottom
Jason Sylvestre edited this page Aug 3, 2022 · 9 revisions

API

https://payments.ucdavis.edu/api-docs/index.html

Invoice stuck in Processing

An invoice gets set to processing from paid with the money movement job. There was one invoice which was set to processing, but the fees transactions were not created in sloth for some reason, so every time the job ran to move to completed it couldn't find the fee transactions. Fix is to confirm the missing transactions in sloth, set back to Paid status with SSMS, and let the job run. Confirm transactions are created in sloth.

Note, the status in sloth is scheduled and I believe that a job in sloth then moves the money in KFS and updates the status in sloth.

The money movement job in Payments should then look for the completed fees transactions and then set the status in Payments to Completed

Invoice Paid in sloth, but not in Payments

So this can happen if the provider notify fails for some reason. Sloth will be updated because it pulls from the CyberSource reports

Steps to fix:

  1. Confirm info exists is sloths transactions, search by merchant id.
  2. Copy the Processor Tracking Number (Like this 58146xxxxxxxxxxx03242)
  3. Create a PaymentEvents Record with SSMS
  4. Mark invoice as paid in payments UI (This will set the invoice status to completed and will need to be changed in step 6)
  5. Set Processor to Manual, ProcessorId optionally to the Processor Tracking number, the Amount, Decision to ACCEPT, and occuredDate, InvoiceId,
  6. Edit the Invoice record. Set the Status to Paid, and the PaymentType to Manual if it is null, and the PaymentProcessorId
  7. Run the moneyMovement job in azure to make sure you didn't break something. (If you did, fix it or set the Status back to paid).
  8. Confirm status is Processing.
  9. Confirm transactions were created in sloth

Customer said they paid:

  1. Look in the payment events table in payments for any trascactions
  2. Look in sloth for any successful payments for the merchant id (Invoice number)
  3. Look in the CyberSource portal and search for any transactions.
  4. CC Brian on tickets if needed.

Scheduled Tax Report

  1. Stored in Payments folder of our on-prem report server (reports.caes.ucdavis.edu). Schedule set to send report out monthly.
  2. You may need to download the stand alone report builder. A dialog will prompt you in the report server.
  3. Report RDLs are in the reports folder in github. If you make changes on the server, update github

Generalized Payments Flow Diagram

Payment Flow

Clone this wiki locally