Project

General

Profile

Actions

Wiki » History » Revision 55

« Previous | Revision 55/59 (diff) | Next »
Brienne Kordis, 01/16/2023 05:01 PM


{{last_updated_at}} by {{last_updated_by}}

Megaphone Technology Logo

Welcome to the Megaphone Technology Consulting commons.

As part of our commitment to transparency and open source principles, we try to make our internal documentation available publicly. We hope that this assists others who may be starting their own companies, looking for best practices on web development, and more.

To contact us: You can reach us by phone or e-mail from here: https://megaphonetech.com/contact

Licensing:
Creative Commons BY-SA logo

Unless otherwise specified, all material with https://hq.megaphonetech.com/projects/commons/wiki/ in the URL is licensed to you under a Creative Commons Attribution-ShareAlike 4.0 International License.

Technical Documentation

Sysadmin/Monitoring

Icinga2 Our monitoring platform
Backup Setup
Backup Setup when we don't have root
Install drush
Inherited Site Security Review
Set up a New Website
Upgrading Docker Applications
Ansible
Deploying with Ansible
How to use a shared SSH config file
Azure VPS setup notes
Email Delivery Service
Deleting Former Client Data
Cloning a site

CRM

Debugging CiviCRM cheatsheet
CiviCRM Launch Checklist
CiviCRM for Drupal 8 installation notes
Migrating D8/CiviCRM to Pantheon
CiviCRM multisite to single site cookbook
Troubleshooting PayPal and CiviCRM
VS Code Configuration for CiviCRM
CiviCRM multisite
CiviCRM administrator training
Stripe setup
Testing
PRs/MRs on CiviCRM
CiviCRM 102 training topics
Payment Workflows for CiviCRM

Recurring payment with interdiction (PayPal)

  1. POST request from user to CiviCRM (User submits form) CiviCRM creates a pending contribution and recurring contribution record.
    1. POST request from CiviCRM to PayPal (Civi asks PayPal to authorize card). PayPal responds with success or failure. CiviCRM responds to user's POST request with a thank-you page (or a PayPal error) A few minutes later...
  2. POST request from PayPal to webhook.site (informing Civi that recurring contribution was created on PayPal's side) 3a. POST request (curl, using webhook.site request) to Civi.
  3. POST request from PayPal to CiviCRM (informing Civi that contribution was successfully charged).

One-time payment (PayPal, Auth.net)

  1. POST request from user to CiviCRM (User submits form) CiviCRM creates a pending contribution and recurring contribution record.
    1. POST request from CiviCRM to PayPal (Civi asks PayPal to authorize card). PayPal responds with success or failure. CiviCRM responds to user's POST request with a thank-you page (or a PayPal error)

One-time payment (Stripe)

  • POST request from user to Stripe (user submits form). Stripe responds in JavaScript with success/failure. (aka "pre-authorization")
  • POST request from user to CiviCRM (triggered by the return of Stripe's request, and including the result of Stripe's request). Civi responds with thank-you page or an error.

Backdrop

Backdrop Configuration Management

Other

New Client Questionnaire
GDPR Compliance
Migration Documentation
Your Test Site
Recording an HAR file
Productivity Tricks
Warrant Canary

Administrative Documentation

Bookkeeping
Where to host CiviCRM

Data Migration

Exporting DonorPerfect Online for CiviCRM
Exporting Nationbuilder for CiviCRM
Exporting Wild Apricot for CiviCRM
Exporting Raisers Edge for CiviCRM
Raisers Edge client notes
Exporting Network for Good for CiviCRM

Updated by Brienne Kordis almost 2 years ago · 55 revisions