Page Menu
Home
GnuPG
Search
Configure Global Search
Log In
Files
F25703740
README
No One
Temporary
Actions
View File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Award Token
Size
1 KB
Subscribers
None
README
View Options
Payproc - A local payment processor
-------------------------------------
To run the daemon:
payprocd --stripe-key /etc/payproc/stripe.testkey \
--verbose --log-file /var/log/payproc/payprocd.log \
--journal /var/log/payproc/journal --live
Payprocd creates the socket /var/run/payproc/daemon and expect the CA
root certificate in /etc/payproc/tls-ca.pem . The given journal file
name will be suffixed with the current date and ".log". The time
stamp in the journal is given in UTC.
You should also add a cron job for the payproc user to run
/usr/lib/payproc/geteuroxref each day at about 16:00 CET.
To add access restrictions to certain user ids in addition to the file
permissions of the communication socket, the options --allow-uids/-U
and --admin-uid may be used. They take an UID or a username as
argument. Setting an --admin-uid implicitly uses the uid for
--allow-uid. If any UID has been specified payprocd checks all
connection attempts against this uids. To use the admin-required commands
--admin-uid must have been given. Thus a common list of options is
"-U www-data --admin-uid OPERATOR" to allow OPERATOR to make use of
all features.
To run payproc in a test environment replace the keys with the test
keys and use the option --test instead of --live. In test mode
payprocd creates a socket /var/run/payproc-test/daemon
See doc/api-ref.org for a description of supported commands.
File Metadata
Details
Attached
Mime Type
text/plain
Expires
Tue, Jul 8, 12:34 PM (4 h, 35 m)
Storage Engine
local-disk
Storage Format
Raw Data
Storage Handle
7d/9c/9e1cc92bc6125b0a8357a4ce4ed6
Attached To
rPAY Payproc
Event Timeline
Log In to Comment