This is the starting point for payday. It is structured such that it can be run again safely (with a newly-instantiated Payday object

Given a Participant or username, and amount as str, returns a dict. We INSERT instead of UPDATE, so that we have history to explore. The

Sets member's take from the team pool.

Given a participant (or their id), returns an `Object`.

(Re)schedule this donor's future payments.

This is called when 1) Adding a new email address 2) Resending the verification email for an unverified email add

Return an existing participant based on username.

Add a member to this team.

Return an existing participant based on id.

Compute transfer amounts. Args: available_amount (Money): the payin amount to split into transfer amounts base_amount

Start a new session for the user. Args: suffix (str): the session type, preceded by a dot: '.

Given a Participant object, return a boolean.

Update the status and other attributes of a payment. Args: pt_id (int): the ID of the payment in our database remote_id (str): th

This function reminds donors to renew their donations. The notifications are sent two weeks before the due date.

Given an AccountElsewhere or a tuple (platform_name, domain, user_id), associate an elsewhere account. Returns None or raises NeedCon

This daily cron job notifies donors who are about to be debited. The notifications are sent at most once a month, 14 days before the first pa

Get the participant's "primary" email address, even if it hasn't been confirmed yet.

Close the participant's account.

Update the status and other attributes of a charge. Args: payin_id (int): the ID of the charge in our database remote_id (str): t

Given a `path` (e.g. /users/foo), this function sends a GET request to the platform's API (e.g. https://api.github.com/users/foo).