Django App for WePay http://www.wepay.com
About
If you start using WePay API you realize that there is a bunch of stuff needs to be stored locally, so that was an actual motivation for creation of this app. There is functionality for storing information for all objects in the database. For each object you can choose to store only minimal fields, all fields and/or add custom fields required for your app. It also handles IPN (instant payment notifications) for all supported objects.
Status
Beta. Although it is used in production, some objects like credit card and subscriptions haven’t been thoroughly tested.
TODO
Full Documentation.
More tests.
Admin pages for all objects.
Requirements
Registered Application with WePay. (tailored for versions >= ‘2014-01-08’)
Cache framework properly configured for django
Features
Supports all WePay API calls.
Customizable models for all objects.
Ability to make API calls right from the model instance.
All lookup and create API calls automatically save changes in the database.
IPN calls handling for all objects.
Signals upon state change an objects as well as for an IPN call.
Ability to change backend (communication module with WePay). Default backend features: * Protection from throttling (threadsafe with memcache) * Automatic storing of batch calls for later invocation. * Logging
Configuration
Add ‘djwepay’ to INSTALLED_APPS
(Optionally) Extend and customize models, point to their location in WEPAY_MODELS, run syncdb (or migrations). If this step omitted all models will be created.
Add your WePay App either in admin or directly into database. Set correct WEPAY_APP_ID.
Settings
Required:
WEPAY_APP_ID - WePay Application Client ID (and associated entry in database for this id).
Optional:
WEPAY_MODELS - a list of tuples (‘object_name’, ‘app_name.ModelName’) for objects you will be working with, ex:
WEPAY_MODELS = ( ('app', 'myapp.WePayApp'), ('user', 'myapp.WePayUser'), ('account', 'myapp.WePayAccount'), ('checkout', 'myapp.WePayCheckout'), ('preapproval', 'myapp.WePayPreapproval'), ('withdrawal', 'myapp.WePayWithdrawal'), ('credit_card', None), ('subscription_plan', None), ('subscription', None), ('subscription_charge', None) )API_BACKEND - backend to be used for communication with WePay. Default is ‘djwepay.backends.default.WePay’
DEFAULT_SCOPE - default WePay permissions, full by default.
Default backend settings
WEPAY_DEBUG - if set to True and logging is setup will log every API call. Defaults to the DEBUG setting.
WEPAY_THROTTLE_PROTECT - turns on/off throttle protection.
WEPAY_THROTTLE_CALL_LIMIT - number of calls before your app will be throttled after. Default is 30.
WEPAY_THROTTLE_TIMEOUT - throttle timespan. Default is 10 seconds.
WEPAY_THROTTLE_CALL_KEY - cache key for storing throttling info.
WEPAY_CACHE_BATCH_KEY_PREFIX - cache key prefix for storing batch calls and associated callbacks in cache, for later processing.
WEPAY_DOMAIN - your site’s domain, if None will use django’s sites app.
Metadata
Release files for django-wepay 1.0.3
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 | |
|---|---|---|---|---|
| django-wepay-1.0.3.tar.gz | 19.8 kB | Without provenance | Details |
Release files / django-wepay-1.0.3.tar.gz
| Download URL | django-wepay-1.0.3.tar.gz |
|---|---|
| Size | 19.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f057839838cea99584ab1a40666a579013b060c5358bff93c8b56ed034929f5
|
|
BLAKE2b-256 checksum How to use checksums |
b219f899ad1fe4c16248ddb5b21303cbbe7bc9b05b6d9cf290b86b5839837ea9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-wepay 1.0.3
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.