pav_api

[placid ore]

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1248223439332966535

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

[glossy grail]

hi! not really in a consistent way I think, sorry.

AFAIK it looks at the the details/user-agents on the API request logs, and none of that is exposed in the public API

a workaround would be to set metadata on all payments that your own code creates, and then the absence of that metadata means a certain payment was not from your code.

[dawn flower]

Thank you in getting back me to me @glossy grail.

The problem is that team members add payments directly via the Payment page, so setting a Metadata field is going to be problematic as they will need to remember to set it each time.

I have noticed that the "Statement descriptor" gets set to the Account name, I could use that instead. The Description field will also be checked for a particular value. Was hoping that the Source field would be exposed as that would have made it more straightforward.