Laravel Cashier (Stripe)
- Introduction
- Upgrading Cashier
- Installation
- Configuration
- Customers
- Payment Methods
- Subscriptions
- Subscription Trials
- Handling Stripe Webhooks
- Single Charges
- Invoices
- Handling Failed Payments
- Strong Customer Authentication (SCA)
- Stripe SDK
- Testing
Introduction
Laravel Cashier provides an expressive, fluent interface to Stripe's subscription billing services. It handles almost all of the boilerplate subscription billing code you are dreading writing. In addition to basic subscription management, Cashier can handle coupons, swapping subscription, subscription "quantities", cancellation grace periods, and even generate invoice PDFs.
Upgrading Cashier
When upgrading to a new version of Cashier, it's important that you carefully review the upgrade guide.
{note} To prevent breaking changes, Cashier uses a fixed Stripe API version. Cashier 12 utilizes Stripe API version
2020-03-02
. The Stripe API version will be updated on minor releases in order to make use of new Stripe features and improvements.
Installation
First, install the Cashier package for Stripe using the Composer package manager:
composer require laravel/cashier
{note} To ensure Cashier properly handles all Stripe events, remember to set up Cashier's webhook handling.
Database Migrations
Cashier's service provider registers its own database migration directory, so remember to migrate your database after installing the package. The Cashier migrations will add several columns to your users
table as well as create a new subscriptions
table to hold all of your customer's subscriptions:
php artisan migrate
If you need to overwrite the migrations that ship with Cashier, you can publish them using the vendor:publish
Artisan command:
php artisan vendor:publish --tag="cashier-migrations"
If you would like to prevent Cashier's migrations from running entirely, you may use the ignoreMigrations
method provided by Cashier. Typically, this method should be called in the register
method of your AppServiceProvider
:
use Laravel\Cashier\Cashier;
/**
* Register any application services.
*
* @return void
*/
public function register()
{
Cashier::ignoreMigrations();
}
{note} Stripe recommends that any column used for storing Stripe identifiers should be case-sensitive. Therefore, you should ensure the column collation for the
stripe_id
column is set toutf8_bin
when using MySQL. More information regarding this can be found in the Stripe documentation.
Configuration
Billable Model
Before using Cashier, add the Billable
trait to your billable model definition. Typically, this will be the App\Models\User
model. This trait provides various methods to allow you to perform common billing tasks, such as creating subscriptions, applying coupons, and updating payment method information:
use Laravel\Cashier\Billable;
class User extends Authenticatable
{
use Billable;
}
Cashier assumes your billable model will be the App\Models\User
class that ships with Laravel. If you wish to change this you can specify a different model in your .env
file:
CASHIER_MODEL=App\Models\User
{note} If you're using a model other than Laravel's supplied
App\Models\User
model, you'll need to publish and alter the Cashier migrations provided to match your alternative model's table name.
API Keys
Next, you should configure your Stripe API keys in your application's .env
file. You can retrieve your Stripe API keys from the Stripe control panel:
STRIPE_KEY=your-stripe-key
STRIPE_SECRET=your-stripe-secret
Currency Configuration
The default Cashier currency is United States Dollars (USD). You can change the default currency by setting the CASHIER_CURRENCY
environment variable within your application's .env
file:
CASHIER_CURRENCY=eur
In addition to configuring Cashier's currency, you may also specify a locale to be used when formatting money values for display on invoices. Internally, Cashier utilizes PHP's NumberFormatter
class to set the currency locale:
CASHIER_CURRENCY_LOCALE=nl_BE
{note} In order to use locales other than
en
, ensure theext-intl
PHP extension is installed and configured on your server.
Logging
Cashier allows you to specify the log channel to be used when logging all Stripe related exceptions. You may specify the log channel by defining the CASHIER_LOGGER
environment variable within your application's .env
file:
CASHIER_LOGGER=stack
Customers
Retrieving Customers
You can retrieve a customer by their Stripe ID using the Cashier::findBillable
method. This method will return an instance of the billable model:
use Laravel\Cashier\Cashier;
$user = Cashier::findBillable($stripeId);
Creating Customers
Occasionally, you may wish to create a Stripe customer without beginning a subscription. You may accomplish this using the createAsStripeCustomer
method:
$stripeCustomer = $user->createAsStripeCustomer();
Once the customer has been created in Stripe, you may begin a subscription at a later date. You may provide an optional $options
array to pass in any additional customer creation parameters that are supported by the Stripe API:
$stripeCustomer = $user->createAsStripeCustomer($options);
You may use the asStripeCustomer
method if you want to return the Stripe customer object for a billable model:
$stripeCustomer = $user->asStripeCustomer();
The createOrGetStripeCustomer
method may be used if you would like to retrieve the Stripe customer object for a given billable model but are not sure whether the billable model is already a customer within Stripe. This method will create a new customer in Stripe if one does not already exist:
$stripeCustomer = $user->createOrGetStripeCustomer();
Updating Customers
Occasionally, you may wish to update the Stripe customer directly with additional information. You may accomplish this using the updateStripeCustomer
method. This method accepts an array of customer update options supported by the Stripe API:
$stripeCustomer = $user->updateStripeCustomer($options);
Billing Portal
Stripe offers an easy way to set up a billing portal so that your customer can manage their subscription, payment methods, and view their billing history. You can redirect your users to the billing portal by invoking the redirectToBillingPortal
method on the billable model from a controller or route:
use Illuminate\Http\Request;
Route::get('/billing-portal', function (Request $request) {
return $request->user()->redirectToBillingPortal();
});
By default, when the user is finished managing their subscription, they will be able to return to the home
route of your application via a link within the Stripe billing portal. You may provide a custom URL that the user should return to by passing the URL as an argument to the redirectToBillingPortal
method:
use Illuminate\Http\Request;
Route::get('/billing-portal', function (Request $request) {
return $request->user()->redirectToBillingPortal(route('billing'));
});
If you would like to generate the URL to the billing portal without generating an HTTP redirect response, you may invoke the billingPortalUrl
method:
$url = $request->user()->billingPortalUrl(route('billing'));
Payment Methods
Storing Payment Methods
In order to create subscriptions or perform "one off" charges with Stripe, you will need to store a payment method and retrieve its identifier from Stripe. The approach used to accomplish this differs based on whether you plan to use the payment method for subscriptions or single charges, so we will examine both below.
Payment Methods For Subscriptions
When storing a customer's credit card information for future use by a subscription, the Stripe "Setup Intents" API must be used to securely gather the customer's payment method details. A "Setup Intent" indicates to Stripe the intention to charge a customer's payment method. Cashier's Billable
trait includes the createSetupIntent
method to easily create a new Setup Intent. You should invoke this method from the route or controller that will render the form which gathers your customer's payment method details:
return view('update-payment-method', [
'intent' => $user->createSetupIntent()
]);
After you have created the Setup Intent and passed it to the view, you should attach its secret to the element that will gather the payment method. For example, consider this "update payment method" form:
<input id="card-holder-name" type="text">

<button id="card-button" data-secret="{{ $intent->client_secret }}">
Update Payment Method
</button>
Next, the Stripe.js library may be used to attach a Stripe Element to the form and securely gather the customer's payment details:

Next, the card can be verified and a secure "payment method identifier" can be retrieved from Stripe using Stripe's confirmCardSetup
method:
const cardHolderName = document.getElementById('card-holder-name');
const cardButton = document.getElementById('card-button');
const clientSecret = cardButton.dataset.secret;
cardButton.addEventListener('click', async (e) => {
const { setupIntent, error } = await stripe.confirmCardSetup(
clientSecret, {
payment_method: {
card: cardElement,
billing_details: { name: cardHolderName.value }
}
}
);
if (error) {
// Display "error.message" to the user...
} else {
// The card has been verified successfully...
}
});
After the card has been verified by Stripe, you may pass the resulting setupIntent.payment_method
identifier to your Laravel application, where it can be attached to the customer. The payment method can either be added as a new payment method or used to update the default payment method. You can also immediately use the payment method identifier to create a new subscription.
{tip} If you would like more information about Setup Intents and gathering customer payment details please review this overview provided by Stripe.
Payment Methods For Single Charges
Of course, when making a single charge against a customer's payment method, we will only need to use a payment method identifier once. Due to Stripe limitations, you may not use the stored default payment method of a customer for single charges. You must allow the customer to enter their payment method details using the Stripe.js library. For example, consider the following form:
<input id="card-holder-name" type="text">

<button id="card-button">
Process Payment
</button>
After defining such a form, the Stripe.js library may be used to attach a Stripe Element to the form and securely gather the customer's payment details:

Next, the card can be verified and a secure "payment method identifier" can be retrieved from Stripe using Stripe's createPaymentMethod
method:
const cardHolderName = document.getElementById('card-holder-name');
const cardButton = document.getElementById('card-button');
cardButton.addEventListener('click', async (e) => {
const { paymentMethod, error } = await stripe.createPaymentMethod(
'card', cardElement, {
billing_details: { name: cardHolderName.value }
}
);
if (error) {
// Display "error.message" to the user...
} else {
// The card has been verified successfully...
}
});
If the card is verified successfully, you may pass the paymentMethod.id
to your Laravel application and process a single charge.
Retrieving Payment Methods
The paymentMethods
method on the billable model instance returns a collection of Laravel\Cashier\PaymentMethod
instances:
$paymentMethods = $user->paymentMethods();
To retrieve the customer's default payment method, the defaultPaymentMethod
method may be used:
$paymentMethod = $user->defaultPaymentMethod();
You can retrieve a specific payment method that is attached to the billable model using the findPaymentMethod
method:
$paymentMethod = $user->findPaymentMethod($paymentMethodId);
Determining If A User Has A Payment Method
To determine if a billable model has a default payment method attached to their account, invoke the hasDefaultPaymentMethod
method:
if ($user->hasDefaultPaymentMethod()) {
//
}
You may use the hasPaymentMethod
method to determine if a billable model has at least one payment method attached to their account:
if ($user->hasPaymentMethod()) {
//
}
Updating The Default Payment Method
The updateDefaultPaymentMethod
method may be used to update a customer's default payment method information. This method accepts a Stripe payment method identifier and will assign the new payment method as the default billing payment method:
$user->updateDefaultPaymentMethod($paymentMethod);
To sync your default payment method information with the customer's default payment method information in Stripe, you may use the updateDefaultPaymentMethodFromStripe
method:
$user->updateDefaultPaymentMethodFromStripe();
{note} The default payment method on a customer can only be used for invoicing and creating new subscriptions. Due to limitations imposed by Stripe, it may not be used for single charges.
Adding Payment Methods
To add a new payment method, you may call the addPaymentMethod
method on the billable model, passing the payment method identifier:
$user->addPaymentMethod($paymentMethod);
{tip} To learn how to retrieve payment method identifiers please review the payment method storage documentation.
Deleting Payment Methods
To delete a payment method, you may call the delete
method on the Laravel\Cashier\PaymentMethod
instance you wish to delete:
$paymentMethod->delete();
The deletePaymentMethods
method will delete all of the payment method information for the billable model:
$user->deletePaymentMethods();
{note} If a user has an active subscription, your application should not allow them to delete their default payment method.
Subscriptions
Subscriptions provide a way to set up recurring payments for your customers. Stripe subscriptions managed by Cashier provide support for multiple subscription plans, subscription quantities, trials, and more.
Creating Subscriptions
To create a subscription, first retrieve an instance of your billable model, which typically will be an instance of App\Models\User
. Once you have retrieved the model instance, you may use the newSubscription
method to create the model's subscription:
use Illuminate\Http\Request;
Route::post('/user/subscribe', function (Request $request) {
$request->user()->newSubscription(
'default', 'price_premium'
)->create($request->paymentMethodId);
// ...
});
The first argument passed to the newSubscription
method should be the name of the subscription. If your application only offers a single subscription, you might call this default
or primary
. The second argument is the specific plan the user is subscribing to. This value should correspond to the plan's price identifier in Stripe.
The create
method, which accepts a Stripe payment method identifier or Stripe PaymentMethod
object, will begin the subscription as well as update your database with the billable model's Stripe customer ID and other relevant billing information.
{note} Passing a payment method identifier directly to the
create
subscription method will also automatically add it to the user's stored payment methods.
Quantities
If you would like to set a specific quantity for the plan when creating the subscription, you should invoke the quantity
method on the subscription builder before creating the subscription:
$user->newSubscription('default', 'price_monthly')
->quantity(5)
->create($paymentMethod);
Additional Details
If you would like to specify additional customer or subscription options supported by Stripe, you may do so by passing them as the second and third arguments to the create
method:
$user->newSubscription('default', 'price_monthly')->create($paymentMethod, [
'email' => $email,
], [
'metadata' => ['note' => 'Some extra information.'],
]);
Coupons
If you would like to apply a coupon when creating the subscription, you may use the withCoupon
method:
$user->newSubscription('default', 'price_monthly')
->withCoupon('code')
->create($paymentMethod);
Or, if you would like to apply a Stripe promotion code, you may use the withPromotionCode
method:
$user->newSubscription('default', 'price_monthly')
->withPromotionCode('promo_code')
->create($paymentMethod);
Adding Subscriptions
If you would like to add a subscription to a customer who already has a default payment method you may invoke the add
method on the subscription builder:
use App\Models\User;
$user = User::find(1);
$user->newSubscription('default', 'price_premium')->add();
Checking Subscription Status
Once a customer is subscribed to your application, you may easily check their subscription status using a variety of convenient methods. First, the subscribed
method returns true
if the customer has an active subscription, even if the subscription is currently within its trial period. The subscribed
method accepts the name of the subscription as its first argument:
if ($user->subscribed('default')) {
//
}
The subscribed
method also makes a great candidate for a route middleware, allowing you to filter access to routes and controllers based on the user's subscription status:
<?php
namespace App\Http\Middleware;
use Closure;
class EnsureUserIsSubscribed
{
/**
* Handle an incoming request.
*
* @param \Illuminate\Http\Request $request
* @param \Closure $next
* @return mixed
*/
public function handle($request, Closure $next)
{
if ($request->user() && ! $request->user()->subscribed('default')) {
// This user is not a paying customer...
return redirect('billing');
}
return $next($request);
}
}
If you would like to determine if a user is still within their trial period, you may use the onTrial
method. This method can be useful for determining if you should display a warning to the user that they are still on their trial period:
if ($user->subscription('default')->onTrial()) {
//
}
The subscribedToPlan
method may be used to determine if the user is subscribed to a given plan based on a given Stripe plan's price identifier. In this example, we will determine if the user's default
subscription is actively subscribed to the application's "monthly" plan. The given Stripe plan price identifier should correspond to one of your plan's price identifiers in the Stripe dashboard:
if ($user->subscribedToPlan('price_monthly', 'default')) {
//
}
By passing an array to the subscribedToPlan
method, you may determine if the user's default
subscription is actively subscribed to the application's "monthly" or "yearly" plan:
if ($user->subscribedToPlan(['price_monthly', 'price_yearly'], 'default')) {
//
}
The recurring
method may be used to determine if the user is currently subscribed and is no longer within their trial period:
if ($user->subscription('default')->recurring()) {
//
}
{note} If a user has two subscriptions with the same name, the most recent subscription will always be returned by the
subscription
method. For example, a user might have two subscription records nameddefault
; however, one of the subscriptions may be an old, expired subscription, while the other is the current, active subscription. The most recent subscription will always be returned while older subscriptions are kept in the database for historical review.
Cancelled Subscription Status
To determine if the user was once an active subscriber but has cancelled their subscription, you may use the cancelled
method:
if ($user->subscription('default')->cancelled()) {
//
}
You may also determine if a user has cancelled their subscription but are still on their "grace period" until the subscription fully expires. For example, if a user cancels a subscription on March 5th that was originally scheduled to expire on March 10th, the user is on their "grace period" until March 10th. Note that the subscribed
method still returns true
during this time:
if ($user->subscription('default')->onGracePeriod()) {
//
}
To determine if the user has cancelled their subscription and is no longer within their "grace period", you may use the ended
method:
if ($user->subscription('default')->ended()) {
//
}
Incomplete and Past Due Status
If a subscription requires a secondary payment action after creation the subscription will be marked as incomplete
. Subscription statuses are stored in the stripe_status
column of Cashier's subscriptions
database table.
Similarly, if a secondary payment action is required when swapping plans the subscription will be marked as past_due
. When your subscription is in either of these states it will not be active until the customer has confirmed their payment. Determining if a subscription has an incomplete payment may be accomplished using the hasIncompletePayment
method on the billable model or a subscription instance:
if ($user->hasIncompletePayment('default')) {
//
}
if ($user->subscription('default')->hasIncompletePayment()) {
//
}
When a subscription has an incomplete payment, you should direct the user to Cashier's payment confirmation page, passing the latestPayment
identifier. You may use the latestPayment
method available on subscription instance to retrieve this identifier:
latestPayment()->id) }}">
Please confirm your payment.

If you would like the subscription to still be considered active when it's in a past_due
state, you may use the keepPastDueSubscriptionsActive
method provided by Cashier. Typically, this method should be called in the register
method of your App\Providers\AppServiceProvider
:
use Laravel\Cashier\Cashier;
/**
* Register any application services.
*
* @return void
*/
public function register()
{
Cashier::keepPastDueSubscriptionsActive();
}
{note} When a subscription is in an
incomplete
state it cannot be changed until the payment is confirmed. Therefore, theswap
andupdateQuantity
methods will throw an exception when the subscription is in anincomplete
state.
Subscription Scopes
Most subscription states are also available as query scopes so that you may easily query your database for subscriptions that are in a given state:
// Get all active subscriptions...
$subscriptions = Subscription::query()->active()->get();
// Get all of the cancelled subscriptions for a user...
$subscriptions = $user->subscriptions()->cancelled()->get();
A complete list of available scopes is available below:
Subscription::query()->active();
Subscription::query()->cancelled();
Subscription::query()->ended();
Subscription::query()->incomplete();
Subscription::query()->notCancelled();
Subscription::query()->notOnGracePeriod();
Subscription::query()->notOnTrial();
Subscription::query()->onGracePeriod();
Subscription::query()->onTrial();
Subscription::query()->pastDue();
Subscription::query()->recurring();
Changing Plans
After a customer is subscribed to your application, they may occasionally want to change to a new subscription plan. To swap a customer to a new plan, pass the Stripe plan's price identifier to the swap
method. The given price identifier should correspond to a Stripe plan price identifier available in the Stripe dashboard:
use App\Models\User;
$user = App\Models\User::find(1);
$user->subscription('default')->swap('price_id');
If the customer is on trial, the trial period will be maintained. Also, if a "quantity" exists for the subscription, that quantity will also be maintained.
If you would like to swap plans and cancel any trial period the customer is currently on, you may invoke the skipTrial
method:
$user->subscription('default')
->skipTrial()
->swap('price_id');
If you would like to swap plans and immediately invoice the customer instead of waiting for their next billing cycle, you may use the swapAndInvoice
method:
$user = User::find(1);
$user->subscription('default')->swapAndInvoice('price_id');
Prorations
By default, Stripe prorates charges when swapping between plans. The noProrate
method may be used to update the subscription's plan without prorating the charges:
$user->subscription('default')->noProrate()->swap('price_id');
For more information on subscription proration, consult the Stripe documentation.
{note} Executing the
noProrate
method before theswapAndInvoice
method will have no affect on proration. An invoice will always be issued.
Subscription Quantity
Sometimes subscriptions are affected by "quantity". For example, a project management application might charge $10 per month per project. You may use the incrementQuantity
and decrementQuantity
methods to easily increment or decrement your subscription quantity:
use App\Models\User;
$user = User::find(1);
$user->subscription('default')->incrementQuantity();
// Add five to the subscription's current quantity...
$user->subscription('default')->incrementQuantity(5);
$user->subscription('default')->decrementQuantity();
// Subtract five from the subscription's current quantity...
$user->subscription('default')->decrementQuantity(5);
Alternatively, you may set a specific quantity using the updateQuantity
method:
$user->subscription('default')->updateQuantity(10);
The noProrate
method may be used to update the subscription's quantity without prorating the charges:
$user->subscription('default')->noProrate()->updateQuantity(10);
For more information on subscription quantities, consult the Stripe documentation.
Multiplan Subscription Quantities
If your subscription is a multiplan subscription, you should pass the name of the plan whose quantity you wish to increment or decrement as the second argument to the increment / decrement methods:
$user->subscription('default')->incrementQuantity(1, 'chat-plan');
Multiplan Subscriptions
Multiplan subscriptions allow you to assign multiple billing plans to a single subscription. For example, imagine you are building a customer service "helpdesk" application that has a base subscription plan of $10 per month but offers a live chat add-on plan for an additional $15 per month. Multiplan subscription information is stored in Cashier's subscription_items
database table.
You may specify multiple plans for a given subscription by passing an array of plans as the second argument to the newSubscription
method:
use Illuminate\Http\Request;
Route::post('/user/subscribe', function (Request $request) {
$request->user()->newSubscription('default', [
'price_monthly',
'chat-plan',
])->create($request->paymentMethodId);
// ...
});
In the example above, the customer will have two plans attached to their default
subscription. Both plans will be charged on their respective billing intervals. If necessary, you may use the quantity
method to indicate a specific quantity for each plan:
$user = User::find(1);
$user->newSubscription('default', ['price_monthly', 'chat-plan'])
->quantity(5, 'chat-plan')
->create($paymentMethod);
If you would like to add another plan to an existing subscription, you may invoke the subscription's addPlan
method:
$user = User::find(1);
$user->subscription('default')->addPlan('chat-plan');
The example above will add the new plan and the customer will be billed for it on their next billing cycle. If you would like to bill the customer immediately you may use the addPlanAndInvoice
method:
$user->subscription('default')->addPlanAndInvoice('chat-plan');
If you would like to add a plan with a specific quantity, you can pass the quantity as the second argument of the addPlan
or addPlanAndInvoice
methods:
$user = User::find(1);
$user->subscription('default')->addPlan('chat-plan', 5);
You may remove plans from subscriptions using the removePlan
method:
$user->subscription('default')->removePlan('chat-plan');
{note} You may not remove the last plan on a subscription. Instead, you should simply cancel the subscription.
Swapping Plans
You may also change the plans attached to a multiplan subscription. For example, imagine a customer has a basic-plan
subscription with a chat-plan
add-on plan and you want to upgrade the customer from the basic-plan
to the pro-plan
plan:
use App\Models\User;
$user = User::find(1);
$user->subscription('default')->swap(['pro-plan', 'chat-plan']);
When executing the example above, the underlying subscription item with the basic-plan
is deleted and the one with the chat-plan
is preserved. Additionally, a new subscription item for the pro-plan
is created.
You can also specify subscription item options by passing an array of key / value pairs to the swap
method. For example, you may need to specify the subscription plan quantities:
$user = User::find(1);
$user->subscription('default')->swap([
'pro-plan' => ['quantity' => 5],
'chat-plan'
]);
If you want to swap a single plan on a subscription, you may do so using the swap
method on the subscription item itself. This approach is particularly useful if you would like to preserve all of the existing metadata on the subscription's other plans:
$user = User::find(1);
$user->subscription('default')
->findItemOrFail('basic-plan')
->swap('pro-plan');
Proration
By default, Stripe will prorate charges when adding or removing plans from a multiplan subscription. If you would like to make a plan adjustment without proration, you should chain the noProrate
method onto your plan operation:
$user->subscription('default')->noProrate()->removePlan('chat-plan');
Quantities
If you would like to update quantities on individual subscription plans, you may do so using the existing quantity methods by passing the name of the plan as an additional argument to the method:
$user = User::find(1);
$user->subscription('default')->incrementQuantity(5, 'chat-plan');
$user->subscription('default')->decrementQuantity(3, 'chat-plan');
$user->subscription('default')->updateQuantity(10, 'chat-plan');
{note} When a subscription has multiple plans the
stripe_plan
andquantity
attributes on theSubscription
model will benull
. To access the individual plan attributes, you should use theitems
relationship available on theSubscription
model.
Subscription Items
When a subscription has multiple plans, it will have multiple subscription "items" stored in your database's subscription_items
table. You may access these via the items
relationship on the subscription:
use App\Models\User;
$user = User::find(1);
$subscriptionItem = $user->subscription('default')->items->first();
// Retrieve the Stripe plan and quantity for a specific item...
$stripePlan = $subscriptionItem->stripe_plan;
$quantity = $subscriptionItem->quantity;
You can also retrieve a specific plan using the findItemOrFail
method:
$user = User::find(1);
$subscriptionItem = $user->subscription('default')->findItemOrFail('chat-plan');
Subscription Taxes
To specify the tax rates a user pays on a subscription, you should implement the taxRates
method on your billable model and return an array containing the Stripe tax rate IDs. You can define these tax rates in your Stripe dashboard:
/**
* The tax rates that should apply to the customer's subscriptions.
*
* @return array
*/
public function taxRates()
{
return ['tax-rate-id'];
}
The taxRates
method enables you to apply a tax rate on a customer-by-customer basis, which may be helpful for a user base that spans multiple countries and tax rates.
If you're offering multiplan subscriptions, you may define different tax rates for each plan by implementing a planTaxRates
method on your billable model:
/**
* The tax rates that should apply to the customer's subscriptions.
*
* @return array
*/
public function planTaxRates()
{
return [
'plan-id' => ['tax-rate-id'],
];
}
{note} The
taxRates
method only applies to subscription charges. If you use Cashier to make "one off" charges, you will need to manually specify the tax rate at that time.
Syncing Tax Rates
When changing the hard-coded tax rate IDs returned by the taxRates
method, the tax settings on any existing subscriptions for the user will remain the same. If you wish to update the tax value for existing subscriptions with the new taxRates
values, you should call the syncTaxRates
method on the user's subscription instance:
$user->subscription('default')->syncTaxRates();
This will also sync any multiplan subscription item tax rates. If your application is offering multiplan subscriptions, you should ensure that your billable model implements the planTaxRates
method discussed above.
Tax Exemption
Cashier also offers the isNotTaxExempt
, isTaxExempt
, and reverseChargeApplies
methods to determine if the customer is tax exempt. These methods will call the Stripe API to determine a customer's tax exemption status:
use App\Models\User;
$user = User::find(1);
$user->isTaxExempt();
$user->isNotTaxExempt();
$user->reverseChargeApplies();
{note} These methods are also available on any
Laravel\Cashier\Invoice
object. However, when invoked on anInvoice
object, the methods will determine the exemption status at the time the invoice was created.
Subscription Anchor Date
By default, the billing cycle anchor is the date the subscription was created or, if a trial period is used, the date that the trial ends. If you would like to modify the billing anchor date, you may use the anchorBillingCycleOn
method:
use Illuminate\Http\Request;
Route::post('/user/subscribe', function (Request $request) {
$anchor = Carbon::parse('first day of next month');
$request->user()->newSubscription('default', 'price_premium')
->anchorBillingCycleOn($anchor->startOfDay())
->create($request->paymentMethodId);
// ...
});
For more information on managing subscription billing cycles, consult the Stripe billing cycle documentation
Cancelling Subscriptions
To cancel a subscription, call the cancel
method on the user's subscription:
$user->subscription('default')->cancel();
When a subscription is cancelled, Cashier will automatically set the ends_at
column in your subscriptions
database table. This column is used to know when the subscribed
method should begin returning false
.
For example, if a customer cancels a subscription on March 1st, but the subscription was not scheduled to end until March 5th, the subscribed
method will continue to return true
until March 5th. This is done because a user is typically allowed to continue using an application until the end of their billing cycle.
You may determine if a user has cancelled their subscription but are still on their "grace period" using the onGracePeriod
method:
if ($user->subscription('default')->onGracePeriod()) {
//
}
If you wish to cancel a subscription immediately, call the cancelNow
method on the user's subscription:
$user->subscription('default')->cancelNow();
Resuming Subscriptions
If a customer has cancelled their subscription and you wish to resume it, you may invoke the resume
method on the subscription. The customer must still be within their "grace period" in order to resume a subscription:
$user->subscription('default')->resume();
If the customer cancels a subscription and then resumes that subscription before the subscription has fully expired the customer will not be billed immediately. Instead, their subscription will be re-activated and they will be billed on the original billing cycle.
Subscription Trials
With Payment Method Up Front
If you would like to offer trial periods to your customers while still collecting payment method information up front, you should use the trialDays
method when creating your subscriptions:
use Illuminate\Http\Request;
Route::post('/user/subscribe', function (Request $request) {
$request->user()->newSubscription('default', 'price_monthly')
->trialDays(10)
->create($request->paymentMethodId);
// ...
});
This method will set the trial period ending date on the subscription record within the database and instruct Stripe to not begin billing the customer until after this date. When using the trialDays
method, Cashier will overwrite any default trial period configured for the plan in Stripe.
{note} If the customer's subscription is not cancelled before the trial ending date they will be charged as soon as the trial expires, so you should be sure to notify your users of their trial ending date.
The trialUntil
method allows you to provide a DateTime
instance that specifies when the trial period should end:
use Carbon\Carbon;
$user->newSubscription('default', 'price_monthly')
->trialUntil(Carbon::now()->addDays(10))
->create($paymentMethod);
You may determine if a user is within their trial period using either the onTrial
method of the user instance or the onTrial
method of the subscription instance. The two examples below are equivalent:
if ($user->onTrial('default')) {
//
}
if ($user->subscription('default')->onTrial()) {
//
}
Defining Trial Days In Stripe / Cashier
You may choose to define how many trial days your plan's receive in the Stripe dashboard or always pass them explicitly using Cashier. If you choose to define your plan's trial days in Stripe you should be aware that new subscriptions, including new subscriptions for a customer that had a subscription in the past, will always receive a trial period unless you explicitly call the trialDays(0)
method.
Without Payment Method Up Front
If you would like to offer trial periods without collecting the user's payment method information up front, you may set the trial_ends_at
column on the user record to your desired trial ending date. This is typically done during user registration:
use App\Models\User;
$user = User::create([
// ...
'trial_ends_at' => now()->addDays(10),
]);
{note} Be sure to add a date cast for the
trial_ends_at
attribute within your billable model's class definition.
Cashier refers to this type of trial as a "generic trial", since it is not attached to any existing subscription. The onTrial
method on the billable model instance will return true
if the current date is not past the value of trial_ends_at
:
if ($user->onTrial()) {
// User is within their trial period...
}
Once you are ready to create an actual subscription for the user, you may use the newSubscription
method as usual:
$user = User::find(1);
$user->newSubscription('default', 'price_monthly')->create($paymentMethod);
To retrieve the user's trial ending date, you may use the trialEndsAt
method. This method will return a Carbon date instance if a user is on a trial or null
if they aren't. You may also pass an optional subscription name parameter if you would like to get the trial ending date for a specific subscription other than the default one:
if ($user->onTrial()) {
$trialEndsAt = $user->trialEndsAt('main');
}
You may also use the onGenericTrial
method if you wish to know specifically that the user is within their "generic" trial period and has not yet created an actual subscription:
if ($user->onGenericTrial()) {
// User is within their "generic" trial period...
}
Extending Trials
The extendTrial
method allows you to extend the trial period of a subscription after the subscription has been created. If the trial has already expired and the customer is already being billed for the subscription, you can still offer them an extended trial. The time spent within the trial period will be deducted from the customer's next invoice:
use App\Models\User;
$subscription = User::find(1)->subscription('default');
// End the trial 7 days from now...
$subscription->extendTrial(
now()->addDays(7)
);
// Add an additional 5 days to the trial...
$subscription->extendTrial(
$subscription->trial_ends_at->addDays(5)
);
Handling Stripe Webhooks
{tip} You may use the Stripe CLI to help test webhooks during local development.
Stripe can notify your application of a variety of events via webhooks. By default, a route that points to Cashier's webhook controller is automatically registered by the Cashier service provider. This controller will handle all incoming webhook requests.
By default, the Cashier webhook controller will automatically handle cancelling subscriptions that have too many failed charges (as defined by your Stripe settings), customer updates, customer deletions, subscription updates, and payment method changes; however, as we'll soon discover, you can extend this controller to handle any Stripe webhook event you like.
To ensure your application can handle Stripe webhooks, be sure to configure the webhook URL in the Stripe control panel. By default, Cashier's webhook controller responds to the /stripe/webhook
URL path. The full list of all webhooks you should enable in the Stripe control panel are:
customer.subscription.updated
customer.subscription.deleted
customer.updated
customer.deleted
invoice.payment_action_required
{note} Make sure you protect incoming Stripe webhook requests with Cashier's included webhook signature verification middleware.
Webhooks & CSRF Protection
Since Stripe webhooks need to bypass Laravel's CSRF protection, be sure to list the URI as an exception in your application's App\Http\Middleware\VerifyCsrfToken
middleware or list the route outside of the web
middleware group:
protected $except = [
'stripe/*',
];
Defining Webhook Event Handlers
Cashier automatically handles subscription cancellations for failed charges and other common Stripe webhook events. However, if you have additional webhook events you would like to handle, you may do so by extending the Cashier webhook controller.
Your controller's method names should correspond to Cashier's controller conventions. Specifically, methods should be prefixed with handle
and the "camel case" name of the webhook you wish to handle. For example, if you wish to handle the invoice.payment_succeeded
webhook, you should add a handleInvoicePaymentSucceeded
method to the controller:
<?php
namespace App\Http\Controllers;
use Laravel\Cashier\Http\Controllers\WebhookController as CashierController;
class WebhookController extends CashierController
{
/**
* Handle invoice payment succeeded.
*
* @param array $payload
* @return \Symfony\Component\HttpFoundation\Response
*/
public function handleInvoicePaymentSucceeded($payload)
{
// Handle the incoming event...
}
}
Next, define a route to your Cashier webhook controller within your application's routes/web.php
file. This will overwrite the default route registered by Cashier's service provider:
use App\Http\Controllers\WebhookController;
Route::post(
'/stripe/webhook',
[WebhookController::class, 'handleWebhook']
);
{tip} Cashier emits a
Laravel\Cashier\Events\WebhookReceived
event when a webhook is received and aLaravel\Cashier\Events\WebhookHandled
event when a webhook was handled by Cashier. Both events contain the full payload of the Stripe webhook.
Verifying Webhook Signatures
To secure your webhooks, you may use Stripe's webhook signatures. For convenience, Cashier automatically includes a middleware which validates that the incoming Stripe webhook request is valid.
To enable webhook verification, ensure that the STRIPE_WEBHOOK_SECRET
environment variable is set in your application's .env
file. The webhook secret
may be retrieved from your Stripe account dashboard.
Single Charges
Simple Charge
{note} The
charge
method accepts the amount you would like to charge in the lowest denominator of the currency used by your application. For example, when using United States Dollars, amounts should be specified in pennies.
If you would like to make a one-time charge against a customer, you may use the charge
method on a billable model instance. You will need to provide a payment method identifier as the second argument to the charge
method:
use Illuminate\Http\Request;
Route::post('/purchase', function (Request $request) {
$stripeCharge = $request->user()->charge(
100, $request->paymentMethodId
);
// ...
});
The charge
method accepts an array as its third argument, allowing you to pass any options you wish to the underlying Stripe charge creation. More information regarding the options available to you when creating charges may be found in the Stripe documentation:
$user->charge(100, $paymentMethod, [
'custom_option' => $value,
]);
You may also use the charge
method without an underlying customer or user. To accomplish this, invoke the charge
method on an new instance of your application's billable model:
use App\Models\User;
$stripeCharge = (new User)->charge(100, $paymentMethod);
The charge
method will throw an exception if the charge fails. If the charge is successful, an instance of Laravel\Cashier\Payment
will be returned from the method:
try {
$payment = $user->charge(100, $paymentMethod);
} catch (Exception $e) {
//
}
Charge With Invoice
Sometimes you may need to make a one-time charge and offer a PDF receipt to your customer. The invoiceFor
method lets you do just that. For example, let's invoice a customer $5.00 for a "Maintenance Fee":
$user->invoiceFor('One Time Fee', 500);
The invoice will be charged immediately against the user's default payment method. The invoiceFor
method also accepts an array as its third argument. This array contains the billing options for the invoice item. The fourth argument accepted by the method is also an array which should contain the billing options for the invoice itself:
$user->invoiceFor('Stickers', 500, [
'quantity' => 50,
], [
'default_tax_rates' => ['tax-rate-id'],
]);
{note} The
invoiceFor
method will create a Stripe invoice which will retry failed billing attempts. If you do not want invoices to retry failed charges, you will need to close them using the Stripe API after the first failed charge.
Refunding Charges
If you need to refund a Stripe charge, you may use the refund
method. This method accepts the Stripe payment intent ID as its first argument:
$payment = $user->charge(100, $paymentMethodId);
$user->refund($payment->id);
Invoices
Retrieving Invoices
You may easily retrieve an array of a billable model's invoices using the invoices
method. The invoices
method returns a collection of Laravel\Cashier\Invoice
instances:
$invoices = $user->invoices();
If you would like to include pending invoices in the results, you may use the invoicesIncludingPending
method:
$invoices = $user->invoicesIncludingPending();
You may use the findInvoice
method to retrieve a specific invoice by its ID:
$invoice = $user->findInvoice($invoiceId);
Displaying Invoice Information
When listing the invoices for the customer, you may use the invoice's methods to display the relevant invoice information. For example, you may wish to list every invoice in a table, allowing the user to easily download any of them:

@foreach ($invoices as $invoice)

{{ $invoice->date()->toFormattedDateString() }}
{{ $invoice->total() }}
id }}">Download

@endforeach

Generating Invoice PDFs
From within a route or controller, you may use the downloadInvoice
method to generate a PDF download of a given invoice. This method will automatically generate the proper HTTP response needed to download the invoice:
use Illuminate\Http\Request;
Route::get('/user/invoice/{invoice}', function (Request $request, $invoiceId) {
return $request->user()->downloadInvoice($invoiceId, [
'vendor' => 'Your Company',
'product' => 'Your Product',
]);
});
The downloadInvoice
method also allows for a custom filename via its third argument. This filename will automatically be suffixed with .pdf
for you:
return $request->user()->downloadInvoice($invoiceId, [
'vendor' => 'Your Company',
'product' => 'Your Product',
], 'my-invoice');
Handling Failed Payments
Sometimes, payments for subscriptions or single charges can fail. When this happens, Cashier will throw an Laravel\Cashier\Exceptions\IncompletePayment
exception that informs you that this happened. After catching this exception, you have two options on how to proceed.
First, you could redirect your customer to the dedicated payment confirmation page which is included with Cashier. This page already has an associated named route that is registered via Cashier's service provider. So, you may catch the IncompletePayment
exception and redirect the user to the payment confirmation page:
use Laravel\Cashier\Exceptions\IncompletePayment;
try {
$subscription = $user->newSubscription('default', $planId)
->create($paymentMethod);
} catch (IncompletePayment $exception) {
return redirect()->route(
'cashier.payment',
[$exception->payment->id, 'redirect' => route('home')]
);
}
On the payment confirmation page, the customer will be prompted to enter their credit card information again and perform any additional actions required by Stripe, such as "3D Secure" confirmation. After confirming their payment, the user will be redirected to the URL provided by the redirect
parameter specified above. Upon redirection, message
(string) and success
(integer) query string variables will be added to the URL.
Alternatively, you could allow Stripe to handle the payment confirmation for you. In this case, instead of redirecting to the payment confirmation page, you may setup Stripe's automatic billing emails in your Stripe dashboard. However, if an IncompletePayment
exception is caught, you should still inform the user they will receive an email with further payment confirmation instructions.
Payment exceptions may be thrown for the following methods: charge
, invoiceFor
, and invoice
on models using the Billable
trait. When interacting with subscriptions, the create
method on the SubscriptionBuilder
, and the incrementAndInvoice
and swapAndInvoice
methods on the Subscription
model may throw incomplete payment exceptions.
Determining if an existing subscription has an incomplete payment may be accomplished using the hasIncompletePayment
method on the billable model or a subscription instance:
if ($user->hasIncompletePayment('default')) {
//
}
if ($user->subscription('default')->hasIncompletePayment()) {
//
}
There are currently two types of payment exceptions which extend IncompletePayment
. You can catch these separately if needed so that you can customize the user experience:
Laravel\Cashier\Exceptions\PaymentActionRequired
: this exception indicates that Stripe requires extra verification in order to confirm and process a payment.Laravel\Cashier\Exceptions\PaymentFailure
: this exception indicates that a payment failed for various other reasons, such as being out of available funds.
Strong Customer Authentication
If your business is based in Europe you will need to abide by the EU's Strong Customer Authentication (SCA) regulations. These regulations were imposed in September 2019 by the European Union to prevent payment fraud. Luckily, Stripe and Cashier are prepared for building SCA compliant applications.
{note} Before getting started, review Stripe's guide on PSD2 and SCA as well as their documentation on the new SCA APIs.
Payments Requiring Additional Confirmation
SCA regulations often require extra verification in order to confirm and process a payment. When this happens, Cashier will throw a Laravel\Cashier\Exceptions\PaymentActionRequired
exception that informs you that extra verification is needed. More information on how to handle these exceptions be found can be found in the documentation on handling failed payments.
Incomplete and Past Due State
When a payment needs additional confirmation, the subscription will remain in an incomplete
or past_due
state as indicated by its stripe_status
database column. Cashier will automatically activate the customer's subscription as soon as payment confirmation is complete and your application is notified by Stripe via webhook of its completion.
For more information on incomplete
and past_due
states, please refer to our additional documentation on these states.
Off-Session Payment Notifications
Since SCA regulations require customers to occasionally verify their payment details even while their subscription is active, Cashier can send a notification to the customer when off-session payment confirmation is required. For example, this may occur when a subscription is renewing. Cashier's payment notification can be enabled by setting the CASHIER_PAYMENT_NOTIFICATION
environment variable to a notification class. By default, this notification is disabled. Of course, Cashier includes a notification class you may use for this purpose, but you are free to provide your own notification class if desired:
CASHIER_PAYMENT_NOTIFICATION=Laravel\Cashier\Notifications\ConfirmPayment
To ensure that off-session payment confirmation notifications are delivered, verify that Stripe webhooks are configured for your application and the invoice.payment_action_required
webhook is enabled in your Stripe dashboard. In addition, your Billable
model should also use Laravel's Illuminate\Notifications\Notifiable
trait.
{note} Notifications will be sent even when customers are manually making a payment that requires additional confirmation. Unfortunately, there is no way for Stripe to know that the payment was done manually or "off-session". But, a customer will simply see a "Payment Successful" message if they visit the payment page after already confirming their payment. The customer will not be allowed to accidentally confirm the same payment twice and incur an accidental second charge.
Stripe SDK
Many of Cashier's objects are wrappers around Stripe SDK objects. If you would like to interact with the Stripe objects directly, you may conveniently retrieve them using the asStripe
method:
$stripeSubscription = $subscription->asStripeSubscription();
$stripeSubscription->application_fee_percent = 5;
$stripeSubscription->save();
You may also use the updateStripeSubscription
method to update a Stripe subscription directly:
$subscription->updateStripeSubscription(['application_fee_percent' => 5]);
Testing
When testing an application that uses Cashier, you may mock the actual HTTP requests to the Stripe API; however, this requires you to partially re-implement Cashier's own behavior. Therefore, we recommend allowing your tests to hit the actual Stripe API. While this is slower, it provides more confidence that your application is working as expected and any slow tests may be placed within their own PHPUnit testing group.
When testing, remember that Cashier itself already has a great test suite, so you should only focus on testing the subscription and payment flow of your own application and not every underlying Cashier behavior.
To get started, add the testing version of your Stripe secret to your phpunit.xml
file:
<env name="STRIPE_SECRET" value="sk_test_<your-key>"/>
Now, whenever you interact with Cashier while testing, it will send actual API requests to your Stripe testing environment. For convenience, you should pre-fill your Stripe testing account with subscriptions / plans that you may use during testing.
{tip} In order to test a variety of billing scenarios, such as credit card denials and failures, you may use the vast range of testing card numbers and tokens provided by Stripe.


Template class handles the hand off from the controller to the view.
Located in /template/Template.php (line 8)
| Class | Description |
|---|---|
| TemplateCache | TemplateCache class handles the hand off from the controller to the view with cache support. |
ContentFor is a way to pass data from the view to the layout.
The current view that is going to be rendered.
The current controller.
Array of the current route.
Store the sha of the current view path;
Get the current view path
Create a new Template
Return the template in a string.
Grab the object vars from the object passed in.
Get the declared vars that are available to the template.
Documentation generated on Wed, 10 Mar 2010 08:31:26 -0800 by phpDocumentor 1.4.3


Faculty
- Select -
Faculty of Agriculture
Faculty of Sciences
Faculty of Art and Social Sciences
Faculty of Management Science
Faculty of Computing
College of Medecine
Department


Not A Love Poem
Stevie Edwards
Nobody likes showers as hot as me. I’ve learned this from old lovers. A new lover finds thorns where he wants his lips to go, so I buy a new loofah. Scour the past until I’m good meat. In the morning I am a body and at night I am a body. I’ve learned this from failed spells.  I want him to know what to look for.
Stevie Edwards is Editor-in-Chief at Muzzle Magazine and Senior Editor in Book Development at YesYes Books. Her first book, GOOD GRIEF (Write Bloody 2012), received the Independent Publisher Book Awards Bronze in Poetry and the Devil’s Kitchen Reading Award. Her second book, HUMANLY, was released in 2015 by Small Doggies Press. She has an MFA in poetry from Cornell University, and will be starting a PhD in the English Department at the University of North Texas next fall. She currently resides in Ann Arbor, MI, and grew up in Lansing, MI. Her poems have appeared in Indiana Review, The Offing, Salt Hill, Baltimore Review, The Journal, Rattle, Verse Daily, PANK, and elsewhere.


jQuery ScrollTo is a great and reliable way to scroll to any element on your page. It brings such features as:
$('#element).ScrollTo()
and your user will be smoothly scrolled to that element!duration
, easing
, and callback
on your ScrollTo call.Enough talk, let's see it in action!
$('#scrollto1').ScrollTo();
$('#scrollto2').ScrollTo({ duration: 2000, easing: 'linear' });
$('#scrollto3').ScrollTo({ duration: 2000, durationMode: 'all' });
$('#scrollto4').ScrollTo({ duration: 2000, alert('Scrolling has now completed.'); });
$('#scrollto5').ScrollTo();
$('#scrollto6').ScrollTo({ onlyIfOutside: true });
jquery-scrollto
and move all the files and directories into that to continue.jquery-scrollto
which has a whole bunch of stuff in it, then that is fine and you can continue onto the next step.jquery-scrollto
then you must rename it to jquery-scrollto
to continue.jquery-scrollto
directory to somewhere on your webserverBe sure to always keep the entire jquery-scrollto
directory intact; this means if you were to only move some of the files instead of moving the entire directory, then you would run into problems due to the cross directory references would no longer be working.
If your page already has jQuery included then you can skip this step.
<!-- Include jQuery (ScrollTo Requirement) --> <script type="text/javascript" src="http://www.yoursite.com/somewhere/on/your/webserver/jquery-scrollto/scripts/jquery-1.4.2.min.js"></script>
<!-- Include ScrollTo (Production) --> <script type="text/javascript" src="http://www.yoursite.com/somewhere/on/your/webserver/jquery-scrollto/scripts/jquery.scrollto.min.js"></script>
If anything isn't working the way you want it to, or if you would like to request a feature or provide praise or general feedback then be sure to click the feedback button to the right, or the "Get Support" link up the top of this page.
This work is powered by coffee and distributed for free. Donations are how we afford our coffee. Coffee is how we stay awake after our day job hours to work on things like this free open-source project which you're looking at. So go ahead, and get that warm fuzzy feeling knowing you just helped some poor fellow working after hours for free to buy his coffee. You only need to spare a few dollars, or as much as you feel this piece of work is worth. Thanks so much. Alternatively; if you are not in a donating mood, then spreading the word about this project on twitter, your blog, or whatever is just as good. You can also give praise by clicking the feedback button or visiting our "Get Support" link. Thanks a bunch, we appreciate the help deeply.
Licensed under the MIT License.


Week1 Notes of "Haskell First Steps" -- "Functional Programming in Haskell" MOOC
Contents
- Haskell Basics
- Haskell More Basics
- Reduction, Functions and Lists
- Try Haskell online
- Install Haskell
- Recommended reading
Haskell Basics
Expressions
- Haskell has no statements, only expressions!
- Pure functional programming languages don’t have any statements — no assignments, no jumps.
- Instead, all computation is performed by evaluating expressions.
Functions
- There are no parentheses or any special keywords / operators.
- Arguments are given after the function, separated by whitespace.
-
Syntax is fairly simple:
function_name arguments = function_body
-
Example function:
hello name = "Hello, " ++ name
Types
- Haskell types are more powerful than C.
- Function definition follows the function type declaration.
- Type declaration is indicated by
::
and function arguments are separated by->
. -
Syntax is fairly simple:
function_name :: arg1_type -> arg2_type -> argn_type -> return_type function_name arguments = function_body
-
Example function:
f :: Int -> Int -> Int f x y = x*y+x+y
-
More info on the example function:
- In this example,
f
is the function name. - Function arguments are of type
Int
andInt
; while the return type isInt
. -
x
andy
are function arguments andx*y+x+y
is the function body.
- In this example,
Lists
-
Python and Haskell have the same syntax for Lists.
lst = [ "A", "list", "of", "strings"]
-
To join lists, syntax in Haskell is:
lst = [1,2] ++ [3,4]
Anonymous functions
- Anonymous functions are called lambda functions in Haskell, which form the basis of the language.
-
Example syntax:
f = \x y -> x*y+x+y
Higher-order functions
- Higher-order functions are functions that operate on functions.
-
HOFs take other functions as arguments and may also return other functions.
map (\x -> x*2) [1..10] -- > 2,4,6,8,10,12,14,16,18,20]
-
More info on the example Higher-order function:
-
map
function here is a typical example for HOF. - The initial input list is immutable. Output of this statement is a new list is created after iterating / processing all the elements of the input list.
- In this example, each element in the input list is doubled and returned as an element of another new list.
-
More notes
- Precedence of function application: Function application binds tighter than anything else.
- So
f x + 3
means(f x) + 3
and notf (x+3)
- Similarly,
sqrt 16+9
=13
which is deciphered bysqrt(16) + 9
. - This should be written as
sqrt (16+9)
for getting5
as result.
- Similarly,
- If an argument to a function is an expression, it should be put in parentheses.
-
Equations are not assignments
- A name can be given only one value.
- Names are often called "variables", but they do not vary.
- In Haskell variables are constant!
- Once a value is given to a name, it can never be changed!
- This is part of the meaning of "pure" and "no side effects".
n = 1 -- just fine! x = 3 * n -- fine n = x -- Wrong: can have only one definition of n
-
It is valid to write
n = n + 1
, it is termed as an equation and not as an assignment.- Haskell tries and fails to compute the result due to the recursive definition of
n
that has the property thatn = n + 1
.
- Haskell tries and fails to compute the result due to the recursive definition of
- Think of an assignment statement as doing three things:
- It evaluates the right hand side: computing a useful value.
- It discards the value of the variable on the left hand side: destroying a value that might or might not be useful.
- It saves the useful value of the RHS into the variable.
- In a pure functional language
- Old values are never destroyed.
- New useful ones just computed.
- If the old value was truly useless, the garbage collector will reclaim its storage.
-
4+-3
will fail as Haskell thinks you wanted to use a special operation '+-', so it should be written as4+(-3)
.- Same is the case with
abs (-3)
; this should not be written asabs -3
.
- Same is the case with
Haskell More Basics
Blocks
-
Example code block:
roots a b c = let det2 = b*b-4*a*c; det = sqrt(det2); rootp = (-b + det)/a/2; rootm = (-b - det)/a/2; in [rootm,rootp]
let ... in ...
construct is an expression, so it returns a value. And there is no need for a return keyword.
Conditions
- Every
if
should havethen
and its correspondingelse
clause. -
Again the
if ... then ... else ...
construct is an expression, so it returns a value.max x y = if x > y then x else y
case
statement
- A
case
statement is useful for conditions with more than two choices. -
Can't have guards in
case
expressions.data Color = Red | Blue | Yellow color = set_color action = case color of Red -> action1 Blue -> action2 Yellow -> action3 double zs = case zs of [] -> [] (x:xs) -> (2 * x) : (double xs)
Reduction, Functions and Lists
Reduction
- The mechanism for executing functional programs is reduction.
- Reduction is the process of converting an expression to a simpler form.
- Conceptually, an expression is reduced by simplifying one reducible expression (called "redex") at a time.
- Each step is called a reduction.
- Reduction is the sole means of execution of a functional program.
- There are no statements, as in imperative languages; all computation is achieved purely by reducing expressions.
The Church-Rosser theorem
- Every terminating reduction path gives the same result
- Correctness doesn’t depend on order of evaluation.
- The compiler (or programmer) can change the order freely to improve performance, without affecting the result.
- Different expressions can be evaluated in parallel, without affecting the result.
- As a result, functional languages are leading contenders for programming future parallel systems.
- For more info, please check Wiki page of The Church-Rosser theorem.
Functions
- Haskell is a functional language so the function concept is essential to the language.
- There are two fundamental operations on functions:
- function definition » creating a function and
- function application » using a function to compute a result.
Lists
- A list is a single value that contains several other values of the same data type.
-
Syntax: the elements are written in square parentheses, separated by commas.
['3', '5'] ['x', 'y', 'z'] [2.718, 50.0, -1.0]
-
Return multiple values: Lists are useful to return multiple results from a function.
minmax
function below returns both the smaller and the larger of two numbers:minmax = \x y -> [min x y, max x y] minmax 3 8 -- > [3,8] minmax 8 3 -- > [3,8]
-
Lazy evaluation: Elements / expressions are evaluated lazily. As long as the expression is not accessed, it is not evaluated.
let xs = [0..] -- doesn’t throw out of memory xs !! 100 -- > 100 -- we can access any element in the list defined tail xs -- This will continue to generate the numbers......
-
Constructing lists:
-
++
: to concat two lists[23, 29] ++ [48, 41, 44] -- > [23, 29, 48, 41, 44]
-
If
xs
is a list, then[] ++ xs == xs xs ++ [] == xs
-
-
..
: sequence of items[0..5]
gives[0,1,2,3,4,5]
- Sequences are not just limited to numbers.
['a'..'e'] = ['a','b','c','d','e']
which is actually same as"abcde"
as any String in Haskell is basically a list of characters. -
Elements can start from any digit / character and consecutive elements can be incremented or decremented.
[4,7..20] -- > [4,7,10,13,16,19] -- each subsequent element is incremented by 3 [10,7..(-13)] -- > [10,7,4,1,-2,-5,-8,-11] -- each subsequent element is decremented by 3 ['p','s'..'z'] -- > "psvy" -- for alphabets ['x','s'..'m'] -- > "xsn" -- alphabets decrementing ['$'..'*'] -- > "$%&'()*" -- Even for special characters [(-6)..2] -- > [-6,-5,-4,-3,-2,-1,0,1,2]
- Sequences are not just limited to numbers.
-
List comprehensions in Haskell were inspired by the mathematical notation set comprehension.
[3*x | x <- [1..10]] -- > [3,6,9,12,15,18,21,24,27,30]
-
-
Operating on lists
-
!!
: index a list by numbering the elements, starting with 0.- value at a specific index
['a'..'z'] !! 13 -- > n
- value at a specific index
-
head
: first element of listhead [1..10] -- > 1
-
tail
: entire list except for the first elementtail [1..10] -- > [2,3,4,5,6,7,8,9,10] tail ['m'..'r'] -- > "nopqr"
-
init
: entire list except for the last elementinit [1..10] -- > [1,2,3,4,5,6,7,8,9]
-
last
: last element of the listlast [1..10] -- > 10 last ['x','s'..'m'] -- > 'm'
-
Try Haskell online
- Haskell can be tried in the browser at https://www.haskellmooc.co.uk.
- This website was actually created by extending the excellent "Try Haskell" developed by Chris Done: https://tryhaskell.org/.
Install Haskell
- Haskell compiler / interpreter can be installed using Haskell Platform.
Note: Though this course advices to install Haskell Platform, it is better to install
Stack
. Please look for the installation instructions and documentation on Stack website.
Recommended reading
- Please check
Haskell Learning Resources
for detailed list of resources for learning Haskell.


City of Love
Malang is the second largest city in East Java province, Indonesia. It has a history dating back to the ancient Mataram Kingdom. The city is famous for its cool temperature. People in East Java sometimes call it "Paris of East Java.
Destination
Being around by many mountain, Malang not only came with mountain vacation, but our beach, cultural spot, and Human Interest is worth to experienced.
Batu
is a city located in East Java Province of Indonesia. It is situated about 20 km to the northwest of Malang. Formerly, it was a part of Malang Regency; but in 2001, Batu became an independent city.
A population of 190,000 people, it lies on the southern slopes of Gunung Welirang. Its population largely consists of Javanese.
Bromo
Mount Bromo is an active volcano and part of the Tengger massif, in East Java, Indonesia. At 2,329 metres (7,641 ft) it is not the highest peak of the massif, but is the most well known
A population of 190,000 people, it lies on the southern slopes of Gunung Welirang. Its population largely consists of Javanese.
Minsk
Lorem ipsum dolor. Lorem ipsum dolor sit amet, consectetur adipisicing elit. Aspernatur animi alias temporibus quam, dolore, eligendi tempore eveniet quasi sit esse?
A population of 190,000 people, it lies on the southern slopes of Gunung Welirang. Its population largely consists of Javanese.
- 1
- 2
- 3
- 4
- 5
Contact
You Can Find Us Here
Jl.Danau Bratan sekian nomer sekian, Sawojajar Malang
FIND ON MAPS (+62)<PHONE_NUMBER> (+62)<PHONE_NUMBER>Keep in Touch
We Will Give you latest information about Malang


Containers
Contents
Fluid containers
If desired, content can be wrapped in fluid, centered containers. The containers will expand to the max-width specified in the table below. This page has been wrapped in a container-xl
class.
| Class name | max-width |
|---|---|
| container-sm | 480px |
| container-md | 720px |
| container-lg | 960px |
| container-xl | 1200px |
| container-xxl | 1440px |

...

...

Fixed-width containers
Check back soon.


{% extends 'base-app-alt.html' %} {% block content %}
This policy describes how we handle both “Personally Identifiable Information” and “Non-Personally
Identifiable Information”. "Non-Personally Identifiable Information" is information that
cannot
be used to identify you. You can use some of our Site's functionality without revealing your personal
information. An example of this is visiting our Site without logging in and browsing for needs.
“Personally Identifiable Information”, on the other hand, is information such as your name or
contact information that can identify you. Features or services related to creating user profiles and
creating
or participating in Organizational Needs, Course Projects or any related functionality, for example, require
your personal information. It is possible to personally identify you when you use these features or
services.
You are responsible for ensuring that the Personally Identifiable Information that you provide to Wisely is
accurate. Inaccurate information may affect your ability to use the Site, the information you receive when
using
the Site, and our ability to get in touch with you. For example, your email address should be kept current
because that is one way in which we can get in touch with you.
When you submit any Personally Identifiable Information to us, you consent and agree that we may collect,
use,
and/or share such information as per this Privacy Policy and our Terms of Use, and as required or permitted
by
law. If you do not agree with these terms, we request that you do not provide any Personally Identifiable
Information to us. If you refuse or take away your consent, or if you decide not to provide us with
Personally
Identifiable Information, we may not be able to offer our Site’s services to you.
There are two types of information we collect about users through the Site:
Non-Personal Information: When users visit our Site, we may take notice of, collect and aggregate.
Non-Personal
Information indicating, among other things, which pages of our Site were visited, how frequently they were
visited, the order in which they were visited, at what time of day they were visited, and which hyperlinks
or
buttons were "clicked." We also collect information from the URLs from which you navigated to our
Site. Collecting such information may involve storing, among other things, the IP address and browser
software
used by users of our Site. It is important to note that while such information may not be Personally
Identifiable Information per se, we may be able to determine from an IP address a user's Internet Service
Provider and the physical location from where he or she is connecting. We also use or may use cookies and/or
web
beacons to help determine and identify repeat visitors, the type of content and sites to which users of our
Site
link, the amount of time each user spends in particular areas of our Site, and the specific features,
functionalities and/or services that users decide to use. Cookies can be thought of as a user's
identification card for Wisely’s servers. Web beacons are small graphic files linked to Wisely’s
servers
that
allow us to track your use of our Site and related features, functionalities, and/or services. Cookies and web
beacons, together, enable Wisely to serve you better and more efficiently, and to provide you with a more
personal experience on our Site. Cookies and web beacons, however, are not used to retain Personally
Identifiable Information. Please note that we may also use additional typical methods of collecting data.
Please also note that you are able to control whether and how your web browser accepts cookies. Most browsers
provide instructions on how to reset the browser to reject cookies via "Help" menus. However, please
note
that if you reject our cookies, many functions and conveniences of this Site may not work properly.
Personally Identifiable Information: We collect Personally Identifiable Information that you provide to us
when you, among other things, create an account, post or participate in an Organizational Need or Course
Project,
request email updates, participate in other parts of our Site, send us email messages, or partake in our
Site’s other services. Among other things, we may use the Personally Identifiable Information that you
provide
to
respond to your questions, provide you the specific information on Course Projects, Organizational Needs, or
other services that you select, send you updates about other Wisely opportunities and events, and send you
email messages about Site maintenance or updates.
In order to use Wisely’s Pledging model for motivation, we require that you provide us with access to
your Massive Open Online Course provider account information. We ask that you log in with your credentials to
these MOOC servers. By providing us with these credentials, you are expressing permission for Wisely to access
information that is pertinent to tracking your progress and achievement in the course. This information can
include, but is not limited to: grades achieved in current and past courses, any other forms of feedback,
status of completion of any “Verified Certificates”. This information is collected only for the
purpose
of verifying your progress to assess your eligibility for rewards as per Wisely’s Terms & Agreements
as well as to assist us in developing tracking tools to help organize your progress.
Participation in Online Social Spaces:
In order to participate in these Online Social Spaces, you may be required to register with us and/or
provide us with Personally Identifiable Information such as your name and email address. Personally Identifiable
Information shall not include any information posted or sent by or to you via any Social Space.
Wisely may offer public or private forums (the "Forums") where you can share your comments and
thoughts. In order to participate in these Forums, you may be required to register with us and/or provide us
with Personally Identifiable Information such as your name and email address. Personally Identifiable
Information shall not include any information posted or sent by or to you via any public or private
Forum.
Updates:
Wisely may enable you to receive updates via email, posting on portions of the Site only accessible to
registered users, etc. In order to subscribe to these updates, you may be required to provide us with
Personally
Identifiable Information such as your name and email address. You will be able to disable these
notifications by
editing your account settings.
We may receive Personally Identifiable Information when you contact us (including, but not limited to, when
you
send us an email message).
Third-Party Sites:
We may receive Personally Identifiable Information when you access or log in to a third-party site from our
Site or into our Site via such third-party sites. This may include details of your Personally Identifiable
Information available from the third party site.
Partner sites providing related tools and services to Wisely users may collect individual level user data
regarding the individual’s use of that partner site while engaged with such related activities. The
partner sites may share that data with Wisely for the purposes of improving Wisely’s services and/or
the partner site’s services. This data could include, but will not necessarily be limited to, information
such as the amount of time spent on the partner site and pages viewed. The privacy policies of such sites govern
their use.
We request that you take some time to familiarize yourself with the ways Wisely uses the information
gathered:
Non-Personal Information: We use Non-Personal Information to improve the quality of our services. Examples
of how we use Non-Personal Information include performing statistical analyses of the aggregate characteristics
and behaviors of our users, identifying demographical information, user preferences, and other business and
educational purposes.
Personally Identifiable Information: Except as set forth in this Privacy Policy or as specifically agreed to
by you, Wisely will not disclose any Personally Identifiable Information gathered from you on the Site. Please
note that your name, email address, records of participation in courses, pledges, and credentials awarded for
participation will, among other things, by default, be visible on your user profile to members of the Wisely
community but restricted to anonymous users. You will have the option of disabling visibility into these
pieces of information through your account settings options. In addition to the other uses set forth in this
Privacy Policy, we may disclose and otherwise use Personally Identifiable Information as described below. We may
also use it for research and business purposes. Records of your participation on the Site may be used for
research into collaboration, motivation, online education, problem solving, and other domains. In the interests
of
this research, you may be exposed to slight variations in user experience that will not substantially alter your
problem solving involvement. All research findings will be reported at the aggregate level and will not
expose your personal identity, although researchers may have access to personally identifying information
throughout their investigations.
Participation in Pledges:
We use the Personally Identifiable Information that we collect from you when you participate in a Pledge for
processing purposes, including but not limited to tracking progress and completion of courses. We may also
share your Personally Identifiable Information and your performance in a given course with the administrators or
instructor(s) of the course and with the institution or institutions with which they are affiliated. Also,
we may archive this information and/or use it for future communications with you.
Participation in Online Social Spaces:
To facilitate your usage of Online Social Spaces, we use Personally Identifiable Information collected
during your use of Online Social Spaces. We reserve the right to reuse information posted in Online Social
Spaces
containing Personally Identifiable Information in future updates of our Site or disseminate information
posted in Social Spaces as per what is stated in our Terms of Service. We may archive this information and/or
use
it for future communications with you and/or your designee(s). We may also use or publish material submitted on
the Social Spaces without using Personally Identifying Information.
Participation in Forums:
To facilitate your usage of the public or private Forums, we use Personally Identifiable Information
collected during your use of these Forums. In addition, we may publish this information via extensions of our
platform
that make use of third-party services, which can include but are not limited to, mobile applications. We
reserve the right to reuse Forum posts containing Personally Identifiable Information in future updates of our
Site.
We may archive this information and/or use it for future communications with you and/or your designee(s). We
may also use or publish material submitted on the forums without using Personally Identifying Information.
Updates:
We use Personally Identifiable Information collected when you ask to be included on our various email or
update services to send you messages related to the Site, Pledges, Social updates or third-party services that
you
opt into where applicable. We may also archive this information and/or use it for future communications with
you.
Communications with Wisely:
When you contact us (e.g, via email or otherwise), we may use the information provided by you to respond to
your communication and/or as described in this Privacy Policy. We may also archive this information and/or use
it
for future communications with you.
Communications with Wisely Business Partners:
We may share your Personally Identifiable Information with current or future Wisely business partners to
receive communications from such parties that you have opted to receive communications from. You can, at any
point,
opt out of these communications by modifying your account settings.
Disclosure to Wisely Operations/Maintenance Contractors:
From time-to-time, our operations/maintenance contractors may have access to your Personally Identifiable
Information while providing products or services to us. These contractors may include, but are not limited
to, vendors and/or suppliers that provide us with technology, services, and/or content related to the operation
and maintenance of our Site. Access to your Personally Identifiable Information by these contractors is limited
to what is reasonably required for the contractor to perform its duties for us.
Legal Rights, Government Authorities, and Actions:
Wisely may share your Personally Identifiable Information with government authorities in response to court
orders, subpoenas, or other legal processes; to defend against legal claims; to establish or exercise our
legal rights or to protect our property; or as otherwise required by law. In these cases we reserve the right to
waive or raise legal objections or rights available to us. We may also share your Personally Identifiable
Information when we believe it is appropriate or necessary to investigate, prevent, or take action regarding
illegal or
suspected illegal activities; to protect and defend the rights, property, or safety of Wisely, the Site, our
users, partners, customers, or others; and in connection with our Terms of Use and other agreements.
Disclosure to Acquirers:
In connection with a sale, merger, or reorganization of all or the majority of all the equity, business or
assets of Wisely to which your Personally Identifiable Information relates, Wisely may disclose and/or
transfer such Personally Identifiable Information to an acquirer, assignee or other successor entity.
EXTERNAL LINKS:
To serve you better, we may provide links to sites operated by organizations other than Wisely("Third
Party
Sites") that we believe may be of interest to you. We do not and will not disclose your Personally
Identifiable Information to these Third Party Sites without obtaining your consent. Please note, however,
that we do not endorse and cannot be held responsible for the privacy practices of these Third Party Sites. If
you decide to click on a link to one of these Third Party Sites, you should review the relevant privacy policies
posted on these other sites to understand how these third party sites collect and use your Personally
Identifiable Information.
UPDATING OR DELETING YOUR PERSONALLY IDENTIFIABLE INFORMATION:
We maintain a procedure to help you confirm that your Personally Identifiable Information remains correct
and up-to-date or choose whether you wish to receive material from us or from one or more of our partners.
However, you may also update your Personally Identifiable Information by logging into the Site and visiting your
user profile or account settings pages. You may also contact us via<EMAIL_ADDRESS>We aim to respond
to every email promptly. Please note, however, that there will be residual information that will remain within
our hardware, databases, access logs and other records, which may or may not contain your Personally
Identifiable Information. If you have any privacy-related questions or unresolved problems, you may contact us
via<EMAIL_ADDRESS>CONFIDENTIALITY AND SECURITY OF PERSONALLY IDENTIFIABLE INFORMATION:
The security and confidentiality of your information is treated with our utmost care and importance. We will
use commercially reasonable efforts to keep your Personally Identifiable Information private and will not share
your personally identifiable information with third parties, except as otherwise provided in this Privacy
Policy, or unless we have good faith belief that such disclosure is warranted in special cases, such as a physical
threat to you or others. Wisely takes reasonable measures to protect your Personally Identifiable Information
from disclosure to or access by third parties. Please note that we do not guarantee the security of Personally
Identifiable Information, and risks exist, however remote, that unauthorized third parties may find ways to
circumvent our security systems or that transmission of your information over the Internet will be
intercepted.
CHANGES TO OUR PRIVACY POLICY:
Please note that we periodically review our privacy practices and that these practices are subject to
change. Any changes, updates, or modifications will be effective immediately upon them being posted on our Site. We
will notify you of material changes to this Privacy Policy by changing the effective date (located at the bottom
of this page). Please be sure to periodically return to this page to ensure familiarity with the most current
version of this Privacy Policy.
Wisely strongly believes in protecting the privacy of children. Consistent with this belief, we do not
knowingly collect or maintain Personally Identifiable Information on our Site from persons under 13 years of
age, and no part of our Site is directed to persons under 13 years of age. If you are under 13 years of age, then please
do not use or access this Site at any time or in any manner. We will take appropriate steps to delete any
Personally Identifiable Information of persons under 13 years of age that has been collected on our Site
without verified parental consent upon learning of the existence of such Personally Identifiable
Information.


Bezier Curves Demo
Linear
Quadratic
Cubic
Higher-order
Number of Steps
t = 0.0
Browser does not support canvas


Introduction to Structural Motifs¶
It has long been observed that transcription factors show a higher affinity to some sequences than others, and seem to tolerate some variability around these highest-affinity sequences.
The interaction between sequence specific transcription factors and DNA requires compatability at a complex interface of both electrostatics and 3D structure. Analagous to sequence representations of transcription factor binding sites, we assume that transcription factors have a preference for a specific shape of the DNA across the binding site and will tolerate some variation around that preferred shape.
Representing the values that a given position-specific shape feature may adopt as \(v_j\), we expect the preference of the transcription factor to be normally distributed:
In which case, given a set \(D\) of \(n\) sequences with \(m\) position-specific features that describe a sample of the binding sites preferred by a given transcription factor:
we can compute a set of parameters \(\phi\) describing the specificity of that transcription factor:
If we also assume that each feature and each position is independent, then calculating the score \(s\) for the ith sequence becomes:
In order to avoid underflow issues during computation, all computations are done in log space.
De novo Motif finding¶
For de novo motif finding, an expectation maximization approach is employed. This approach assumes that there is exactly one occurrence of the binding site on each of the training sequences. This based on the OOPS model employed by MEME.
E-step¶
The likelihood (\(l_{ij}\)) of the \(j\)th position in the \(i\)th sequence being the start of the binding site is taken to be the score of the StruM at that position multiplied by the likelihood of the flanking regions matching the background model (\(\phi_B\)):
The likelihoods are then normalized on a by-sequence basis to produce \(M\), the matrix of expected start positions:
M-step¶
The maximization step takes these likelihoods and calculates maximum likelihood values for \(\mu\) and \(\sigma\) for each of the \(m\) position-specific features:


Clare McGraw: Portfolio | Art & Design
Lake Kachess photoshop & procreate, 2020
Dragon Tattoo Design procreate, 2021
Cthulhu Concept photoshop, 2020
Master Study colored pencil & colored paper, 2019
Gouache Caricature gouache & watercolor on watercolor paper, 2019
Timothee Portrait photoshop, 2020


| Field | Required | Type | Description |
|---|---|---|---|
|
required | Array<GeocodingResult> | See GeocodingResult for more information. |
|
required | GeocodingStatus | See GeocodingStatus for more information. |
|
optional | string |
A short description of the error. |
|
optional | PlusCode |
An encoded location reference, derived from latitude and longitude coordinates, that represents an area: 1/8000th of a degree by 1/8000th of a degree (about 14m x 14m at the equator) or smaller. Plus codes can be used as a replacement for street addresses in places where they do not exist (where buildings are not numbered or streets are not named). See Open Location Code and plus codes. See PlusCode for more information. |
Generated from the OpenAPI specification. Edit Report bug


UPDATE: DR Congo plane crash death toll rises to 26
by AFP(AFP) — At least 26 people were killed Sunday when a small plane crashed after takeoff into a house in a densely populated area of the city of Goma in eastern Democratic Republic of Congo.
All 17 passengers and two crew members on board the plane perished, while seven more died on the ground as the plane smashed into a house near the airport, the deputy transport minister Jacques Yuma Kipuya said in a statement.
The first images from the scene showed smoke billowing above the neighbourhood and the aircraft in flames with local people throwing buckets of water on it.
A video seen by AFP showed the cabin of the plane still smouldering embedded in the wall of the house.
Other local sources in Goma claimed the death toll was higher, between 27 to 29 killed, and several wounded people were hospitalised.
The Dornier-228 aircraft had been headed for the city of Beni, 350 kilometres (220 miles) north of Goma, when it went down after takeoff in the residential area.
Busy Bee airline staff member Heritier Said Mamadou had earlier confirmed that 19 were on board the flight scheduled from Goma around 9:00 am (0700 GMT).
Busy Bee, a recently established company, has three planes serving routes in the North Kivu province.
The pilot “failed in his takeoff,” Nord Kivu governor Carly Nzanzu Kasivita said in a statement.
One of the airline’s maintenance workers at the site, quoted by news site actualite.cd, blamed a “technical problem”.
Among the victims of the Goma crash was a woman who was the coordinator of an association for the defence of women’s rights, Mambo Zawadi, her NGO said.
There were also three civil servants in the housing sector “who were returning to their posts in Butembo and Beni after work sessions that I had organised,” their supervisor Molendo Sakombi said in a statement.
The UN mission deployed in DR Congo, MONUSCO, sent two fire engines to support local rescue services.
Aircraft accidents are common in the vast, conflict-wracked central African country.
Last month an Antonov-72 cargo plane that was providing logistical assistance for a trip by Congolese President Felix Tshisekedi and carrying eight crew and passengers went missing after taking off from Goma.
More International News Stories
-
‘Jealous’ Ohio mom gets 37 years in prison for killing her 3 sons November 22, 2019
-
Video shows moment Brazilian man shoots, kills homeless woman who asked for 23 cents November 22, 2019
-
Boy, 13, executed teen girl because he feared he got her pregnant November 22, 2019
-
Indiana dad plunges four stories to his death aboard Carnival cruise ship November 22, 2019
-
Navy veteran was dead for 3 years before he was found in apartment November 22, 2019
-
Teen migrants found hiding in car seat, dashboard in attempted smuggling November 22, 2019
-
First male birth control injection almost ready for penises November 22, 2019
-
Texas couple sentenced to prison for disposing of their 2-year-old in tub of acid November 22, 2019
-
380-pound Florida man arrested after hiding drugs in belly button November 22, 2019


| Instructions | |||
|---|---|---|---|
| Wait for the applet and sounds to load, then click on the applet area and press the 'S' key to start. Use the cursor keys to maneuver the snake around the maze. Gobble up the mice to score points but avoid running into the walls or yourself. When the red key appears, grab it to advance to the next level. If you make it through all five levels, you start back at the beginning but the game will move a little faster. You begin with three lives, a bonus life is awarded for every 500 points scored. | |||
| Keyboard Controls | |||
| Key | Description | Key | Description |
| S | Start Game | P | Pause Game |
| M | Mute | ||
| Cursor Left | Turn Left | Cursor Right | Turn Right |
| Cursor Up | Turn Up | Cursor Down | Turn Down |
| Scoring | |||
| Object | Points | ||
| Mouse | 10 | ||
| Level Bonus | 200 | ||
| Source and Download | |||
|
Source: SnakePit.java All files: SnakePit.zip (78KB) |


WITNESS LIST Education Committee March 1, 2005 - 8:30A SB 75 Registering, but not testifying: For: Canaday, Jennifer Lobbyist (ATPE), Austin, TX SB 81 ON: Castillo, A. (Self), North Richland Hills, TX SB 296 ON: Sayavedra, Leo Vice-Chancellor - Academic and Student Affairs (The Texas A&M University System), College Station, TX Registering, but not testifying: For: Oliver, Harold Lobbyist (Greater San Antonio Chamber of Commerce), Austin, TX SB 387 FOR: Eaton, Holly Director of Professional Development and Advocacy (Texas Classroom Teachers Association), Austin, TX AGAINST: Carpenter, Bill Assist. Supt. for Governmental Relations (Houston I.S.D.), Houston, TX Hall, Pamela Secretary-Executive Board (Texas Association of School Personnel Administrators), Austin, TX Martin, Dr. Alejandra (Alex) Executive Director (Texas Association of School Personnel Administrators), Austin, TX Reeves, Gary (Garland I.S.D., Texas School Alliance), Garland, TX Winkler, Sarah Secretary, Alief ISD Board of Trustees (Texas Association of School Boards), Austin, TX ON: Castillo, A. (Self), North Richland Hills, TX Registering, but not testifying: For: Canaday, Jennifer Lobbyist (ATPE), Austin, TX Kelly, Jack Legislative Specialist (Texas State Teachers Association), Austin, TX Lara, Rene Legislative Liaison (Texas Federation of Teachers), Austin, TX Against: Canales, Ramiro Assistant Executive Director, Governmental Relations (Texas Association of School Administrators), Austin, TX SB 482 FOR: Baker, Dr. Vivian Superintendent (Belton ISD), Belton, TX Eaton, Holly Director of Professional Development and Advocacy (Texas Classroom Teachers Association), Austin, TX ON: Jung, Ronnie Executive Director (Teacher Retirement System), Austin, TX Registering, but not testifying: For: Borden, Sandi Executive Director (Texas Elementary Principals & Supervisors Association), Austin, TX Kelly, Jack Legislative Specialist (Texas State Teachers Association), Austin, TX Lara, Rene Legislative Liaison (Texas Federation of Teachers), Austin, TX Martin, Alejandra (Alex) Executive Director (Texas Association of School Personnel Administrators), Austin, TX


Sign-in using Facebook
Fill out our simple event submission form.
It's as easy as clicking a button.
Now every student on campus will see your event without you paying big marketing bucks.
See all events near you or filter based on your preferences.
Purchase tickets or RSVP your attendance.
Share the event with your friends and make it a party!


This application requires Javascript to run. If your device doesn't support javascript look into alternative clients, such as the CLI and desktop applications.


--- layout: default title: Advanced Corporate Finance ---
This is an advanced course in which students are expected to perform professional level work. The course incorporates richer institutional detail into quantitative analysis, bringing students closer to real‐world situations while maintaining a fundamentally analytical approach to financial decision‐making.


Here you'll be able to find out more about my personal and web development learning journey. Come on in!


--- layout: post title: get UA description: "get current page userAgent" tags: [js] author: DANIEL ---
get this userAgent


TABLE OF INTERACTIONS WITH
ACETYLCHOLINESTERASE INHIBITORS
See also: bradycardia inducing drugs
+ ATROPINIC MEDICATIONS
It is necessary to take into account the risk of administering an atropinic medication (tricyclic antidepressants, neuroleptics, phenothiazines, antispasmotics, some H1-antihistamines …) to a patient also taking an anticholinasterase. Aside from the possible decrease of the therapeutic effect of the latter, the abrupt interruption of treatment with an atopinic exposes the patient to the risk of uncovering the muscarinic effects of the parasympathomimetic with symptoms of the “cholinergic crisis” type, which can manifest especially with convulsions.
+OTHER ANTI-CHOLINESTERASE MEDICATIONS
It is necessary to take into account the administration of an anticholinasterase, given for a diagnosis such as for myasthenia or intestinal atonia, with another anticholinsaterase given for Alzheimers, due to the risks of additive undesirable effects of the cholinergic type, especially digestive ones.
From the French ANSM drug interactions document of September 2016, p. 19
ACETYL-CHOLINESTERASE INHIBITORS CLASS CODE: NO6DA-001 |
BETA-BLOCKING AGENTS IN HEART FAILURE CLASS CODE: C07AB-003 |
Risk of excessive bradycardia (addition of the bradycardia inducing effects) |
Precaution for use Regular clinical monitoring, especially at the beginning of the administration of the substances together |
ACETYL-CHOLINESTERASE INHIBITORS CLASS CODE: NO6DA-001 |
PILOCARPINE RxNorm: 8328 ATC: N07AX01 S01EB01 S01EB51 |
Risk of addition of the undesirable cholinergic effects, especially digestive ones |
Take into account |
ACETYL-CHOLINESTERASE INHIBITORS CLASS CODE: NO6DA-001 |
SUXAMETHONIUM RxNorm: 10154 ATC: M03AB01 |
Risk of lengthening of the motor block, increased in the case of partial deficit of pseudocholinesterase |
Take into account |