Paystack

Installation / Usage

To install use pip:

$ pip install --upgrade paystack

$ easy_install --upgrade paystack

Info

See http://www.pip-installer.org/en/latest/index.html for instructions
on installing pip. If you are on a system with easy_install but not
pip, you can use easy_install instead. If you’re not using
virtualenv,
you may have to prefix those commands with sudo. You can learn
more
about virtualenv at http://www.virtualenv.org/

To install from source, clone this repo and run:

$ git clone https://github.com/ojengwa/paystack.git

$ python setup.py install

Documentation

Please see https://developers.paystack.co/docs for the most up-to-date documentation for the Paystack API.

API Anatomy

Please see https://ojengwa.github.io/paystack/ for the most up-to-date documentation of the API Anatomy.

Testing

The package is compatible with Python 2.6+, Python 3.1+ and PyPy. We need to test against all of these environments to ensure compatibility. Travis CI will automatically run our tests on push. For local testing, we use nose to handle testing across environments.

To run the included test:

Clone the repo:

$ git clone https://github.com/ojengwa/paystack.git

Enter project directory:

$ cd paystack

Install dependencies using fabric:

$ fab install

Run the includded test using fabric:

$ fab test

TODO

Add Event hooks
Create Consumer Resource
Create Plan Resource

Example

from paystack.resource import TransactionResource

import random
import string

def main():
    rand = ''.join(
        [random.choice(
            string.ascii_letters + string.digits) for n in range(16)])
    secret_key = 'YOUR_SECRET_KEY'
    random_ref = rand
    test_email = 'TEST_EMAIL'
    test_amount = 'TEST_AMOUNT'
    plan = 'Basic'
    client = TransactionResource(secret_key, random_ref)
    response = client.initialize(test_amount,
                                 test_email,
                                 plan)
    print(response)
    client.authorize() # Will open a browser window for client to enter card details
    verify = client.verify() # Verify client credentials
    print(verify)
    print(client.charge()) # Charge an already exsiting client

Metadata

Release files for paystack 1.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for paystack 1.5.0
File	Size	Uploaded	Provenance
paystack-1.5.0.tar.gz	10.8 kB	Feb 25, 2016	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for paystack 1.5.0
File	Interpreter	ABI	Platform	Reset
paystack-1.5.0-py2.7.egg 26.1 kB Feb 25, 2016 Without provenance	Legacy Egg format	-	-	Details

Total release size: 36.9 kB

Release files / paystack-1.5.0.tar.gz

Download URL	paystack-1.5.0.tar.gz
Size	10.8 kB
Tags	Source
SHA-256 checksum How to use checksums	`95eafecbc763bc49b5ece0f7bf12472c1e0cf610df837067ea88841130a6a2e7`
BLAKE2b-256 checksum How to use checksums	`7e55babf7e2564618d705443f2b1d79862adca9570542bd0e7f4aade87b3f15f`
Upload date	Feb 25, 2016
Uploaded using Trusted Publishing? What is trusted publishing?	No

Release files / paystack-1.5.0-py2.7.egg

Download URL	paystack-1.5.0-py2.7.egg
Size	26.1 kB
Tags	Egg
SHA-256 checksum How to use checksums	`e9709e204ffcef54ba7a0732002e67cd147ceb13ac4d09c0361d9a6873021a36`
BLAKE2b-256 checksum How to use checksums	`51a9826cb77603d4724b316e181fb255eae5947000c3968cd3e334ebaaca785e`
Upload date	Feb 25, 2016
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for paystack 1.5.0

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.