Lots of questions here:
1. I'm assuming cups logs have been looked at to determine loosely why the job is pausing?
2. What OS is the print server running on? If it's windows server then your url for the queue should be lpd://servername/queue_name.
3. If you're using a straight IP address to a server then how will cups determine what queue to send the job to?
4. Continuation of question 3. I'm assuming the Papercut application server is running on the same box as your queues? If it's not and you're pointing the queue on this Mac to the Papercut application server then that's not correct it needs to point to a print server.

FYI under cups any queue name with a space in it will get an underscore added to it. You won't see it in the Printers & Scanners pref pane but when looked at in cups (localhost:631 in your browser) it will have the underscore.

OK @bodeo I'm going to list out how I do it over our way. There are many ways to do this as your'e seeing. I suspect I know where your issue is though. In amny event Here's our setup.

1) PaperCut Server (Running on Windows 2012r2, in VSphere).
-Set using Standard SMB print queues. I'm happy to give details.
-Universal drivers installed for both HP and Xerox (Our primary pritners/copiers)
-Option on each printer to "Render print jobs on client comptuers"
-Currently using TCP/IP ports. -Each port is configured as a "Standard TCP/IP port" and assigned to a specific IP number (Printers have static IPs here)

2) I deploy print drivers seperately from print queue isntallation. Either during enrollment or via a policy, using a smart group to identify machines without current drivers. I load ALL drivers for each manufacturer we support, where possible. This way, I only need to call the specific driver with each printer install policy

3) My JAMF policy simply uses an lpadmin command in a script. Here's an example

lpadmin -p PRINT_DISPLAY_NAME -E -v smb://your.papercut.domain.com/PRINT_QUEUE_NAME -P /Library/Printers/PPDs/Contents/Resources/Xerox WorkCentre 5945.gz -o auth-info-required=negotiate -o XRFinisher=OF -o XRTrays=FiveTraysHCTT -o XRHolePunch=TruePunch -o XRFinishing=Unspecified -o XRPunchOption=None -o XRStapleOption=None -o XROutputDestination=Auto  -o XRBiDiCommunication=Off

I am using two options that you may find important here. 1), "o auth-info-required=negotiate" and 2) "-o XRBiDiCommunication=Off"

-You could also set this globally with the following defautls write command.

defaults write /Library/Preferences/.GlobalPreferences.plist BiDi Off

4) Last but not least, I have a smart group that tracks units with paused print queues. I set the following an an EA (Found somewhere here)

#!/bin/bash

# echo $(lpstat -p | grep -EB1 "Paused")
# echo $(lpstat -p | grep -w "disabled" | awk '{print$2}')

RESULT=$(lpstat -p | grep -w "disabled" | awk '{print$2}')

echo "<result>$RESULT</result>"

I scope this to a policy that uses the following commands, in a script

#EMPTYS ALL PRINTER QUEUES THAT ARE PAUSED
sudo cancel -a `lpstat -t | grep disabled | awk '{print $2}'`
#UNPAUSES PAUSED PRINTERS
sudo cupsenable `lpstat -t | grep disabled | awk '{print $2}'`

This attempts to re-print anything the user may have caught in a paused print queue. It's heavy handed but it catches things before a user piles up 10 versions of the same print job in a paused queue.

@tjhall @mainelysteve @Chris_Hafner thanks guys for your comments, will try those and let you know. I am very new to Jamf we only just started using it and am still trying to figure things out. We primary have windows pcs and just about 25 macs.

The puzzling thing is that when I setup the printer via below, it works but not when deployed thru Jamf. I suspect the issue might be because the secure print share name has a space in it.

@Chris_Hafner can you explain how to create the smart group that tracks paused print queue

@bodeo I would highly suggest using the dns name of your print server rather than an IP address. Not a necessity by any means but it is good practice to do so.

@bodeo Listen to @mainelysteve and use DNS names. As for the scope question.

1) Create an Extension Attribute with the script I included above

#!/bin/bash

# echo $(lpstat -p | grep -EB1 "Paused")
# echo $(lpstat -p | grep -w "disabled" | awk '{print$2}')

RESULT=$(lpstat -p | grep -w "disabled" | awk '{print$2}')

echo "<result>$RESULT</result>"

2) Create a new SMART group as follows: CRITERIA of "NAME OF EXTENSION ATTRIBUTE"
OPERATOR: "is not"
VALUE: (leave blank)

It should look something like this:

Then scope that smart group to a policy that runs the script:

#EMPTYS ALL PRINTER QUEUES THAT ARE PAUSED
sudo cancel -a `lpstat -t | grep disabled | awk '{print $2}'`
#UNPAUSES PAUSED PRINTERS
sudo cupsenable `lpstat -t | grep disabled | awk '{print $2}'`

@Chris_Hafner thanks for that. Yes I did use the dns name in the configuration only just rather than the ip, just left the ip on the screenshot because I was posting it on a public forum.

So I have created the smart group and pushed out the policy, this has gone rid of the paused state - Thank You. However the print Job is still going to Paused state when you send a print

I also second Papercut. We use that for ton of reasons (no need to push out drivers, secure airprint requiring credentials, better printing metrics, etc). We also have Toshiba copiers that have a built in "Find Me" queue that require a user login or scan their ID in order to print. We also have done something similar in testing by using a Raspberry PI with a touch display for other printers and that has been successful too as a release station.

@bodeo Good point about the public post ;-) There's got to be something in the way there. Does the queue give you a reason for pausing? Perhaps you should push out the defaults write command I posted.

defaults write /Library/Preferences/.GlobalPreferences.plist BiDi Off

Let me know if that makes any difference!

@rhoward You have me VERY insterested in your rPi solution. What is that handling? Just prox card/smart cards, or is that doing something with the release itself? I ask because I find Papercut's release device licensing to be a little silly.

@Chris_Hafner it was only in testing purposes for just releasing jobs. The goal was to cut down on paper waste and for printing confidential information. I'm not sure about the licensing as I don't generally deal with that side of things. Ultimately it was going to be a costly solution and we decided against it, but it could work in some environments!

@rhoward Thanks for that! Yea, prox readers are cheap. Last I checked, ACDI (Our vendor for Papercut) wanted something like $800/release station for licnesing.

@bodeo Just to verify as your screenshot above shows you didn't add the printer share name to the URL field. So it should be lpd://servername/printer_share. It's probably pausing because of this config error.

You should check cups in your browser:
On the mac your testing with enter localhost:631 into Safari or whatever your favorite browser is. Click Printers and if prompted enter the command shown into terminal. Back in cups click the queue name created by the jamf Pro policy and ensure the connection field has a fully flushed out url and not just the print server address. If the queue/share name on the print server has spaces in it please use (-) dashes i.e. Office Printer should be entered as Office-Printer.
You may also have issues with the generic ppd you're using.

Again you may have already done this but I'm double checking as your previous posts show that jamf is sending out the incorrect url.

@Chris_Hafner @tjhall @mainelysteve @rhoward good morning and thanks for all your help. I seem to have got this working now (fingers crossed) like I said in my earlier post when I manually setup the printing to the papercut printing queue on the mac it works absolutely fine, - you send a print walk to any printer, scan your id badge and the print comes out but when i use the same setting via Jamf pro it goes to "paused" state when you print. So what I have just done this morning is added the secure print onto the mac manually again and upload it via Jamf admin and based on initially testing this seems to working as it should be.