26 lines
1.7 KiB
PHP
26 lines
1.7 KiB
PHP
<?php
|
|
|
|
// What can go wrong on the way to paying, in sentences for the customer.
|
|
return [
|
|
'thanks' => 'Thank you! As soon as the payment is confirmed we start building your cloud — you can follow it on this page.',
|
|
'unavailable' => 'Payment is not possible right now. Please try again in a few minutes.',
|
|
'plan_gone' => 'That package cannot be booked at the moment. Please choose another one.',
|
|
'already_customer' => 'You already have a running package. Change it here rather than buying a second one.',
|
|
|
|
// The line the one-off setup carries on the payment page and on the first
|
|
// invoice. Worded exactly as the price sheet words it: meeting a different
|
|
// name for the same charge at the till is when somebody abandons a checkout.
|
|
'setup_fee_line' => 'Setting up your cloud, one-off',
|
|
|
|
// The express request that the service begin at once.
|
|
//
|
|
// The second sentence used to state a pro-rata liability (FAGG §16). There
|
|
// is none here any more: a withdrawing consumer gets the whole amount back
|
|
// (see App\Actions\WithdrawContract), and a tick-box that promises the
|
|
// customer something worse than what we actually do is a false statement,
|
|
// even when it is against our own interest. Nothing turns on the consent
|
|
// now; it stays as a record that the customer asked us to start at once.
|
|
'immediate_start' => 'I expressly request that you begin providing the service before the 14-day withdrawal period has ended. My right of withdrawal is unaffected: if I withdraw within the period I get the full amount paid back.',
|
|
'immediate_start_required' => 'Please confirm that the service should begin at once — otherwise we can only build your cloud once the withdrawal period has ended.',
|
|
];
|