Hey! I can't reproduce it in our test environment either - the only thing I was able to reproduce was sending payType to an OD instance that didn't support payType, and the response I received still showed the payType I had configured rather than the default - so the response is misleading as it's not actually telling me what was written back, just spitting back what I sent.
We have a separate table to keep track of the definition.DefNum per OD instance - we'll check if it exists first, then create it if needed, and then write back, so that angle is covered.
As for whether an employee is changing it - I did consider that, but they're saying it's a lot of payments (I'm waiting for them to check other pay types for me). I'll follow up on this angle again.
I'll need to get a hand from a developer for json, however, in the meantime, I've pulled the response from our logs (card last 4 has been obscured):
Code: Select all
Response: {"PayNum":18291,"PayType":71,"payType":"Credit Card","PayDate":"2023-11-16","PayAmt":"2885","CheckNum":"","BankBranch":"","PayNote":"ID: 01HFCGK8P68VFR149CVHVT2KJ9 Credit / Debit ending in XXXX","PatNum":5396,"ClinicNum":0,"DateEntry":"2023-11-16","DepositNum":0,"Receipt":"","IsRecurringCC":"false","PaymentSource":"API","ProcessStatus":"OfficeProcessed","RecurringChargeDate":"0001-01-01","IsCcCompleted":"false","serverDateTime":""}