Copyright (c) 2010, 2011 Quixotix Software, LLC All Rights Reserved.
Quixotix Payment is a set of classes for abstract interfacing with online payment gateways used to process credit card transactions.
Supported Gateways
Authorize.NET AIM - http://www.authorize.net
PSiGate XML Messenger - http://www.psigate.com
Quantam Gateway Authorize.Net Emulation - http://www.quantamgateway.com
Installation
easy_install quix.pay
Example Usage
Simple authorize request using Authorize.NET in test mode:
from quix.pay.transaction import CreditCard
from quix.pay.gateway.authorizenet import AimGateway
card = CreditCard(
number = '4111111111111111',
month = '10',
year = '2020',
first_name = 'John',
last_name = 'Doe',
code = '123'
)
gateway = AimGateway('YOUR API LOGIN', 'YOUR API PASSWORD')
gateway.use_test_mode = True
gateway.use_test_url = True
response = gateway.authorize(1, card)
print "Authorize Request: %s" % gateway.get_last_request().url
print "Transaction %s = %s: %s" % (response.trans_id,
response.status_strings[response.status],
response.message)
The author has posted an article on using quix.pay with the Authroize.Net AIM gateway on his blog: http://www.micahcarrick.com/python-authorize-net-payment-gateway.html
Metadata
Release files for quix.pay 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| quix.pay-0.1.4.tar.gz | 9.8 kB | Without provenance | Details |
Release files / quix.pay-0.1.4.tar.gz
| Download URL | quix.pay-0.1.4.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e19b7a6cb2554799188788361a675ea6b7012e36259d249ce340d3d0378f446
|
|
BLAKE2b-256 checksum How to use checksums |
3066c751259f018f5334088fbab7a948dc259975a0f9ae013bd46c0056d63050
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for quix.pay 0.1.4
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.