Support Center
A complete guide to the platform for administrators, office staff, treasurers, teachers and families: what each part does, how to set it up, and how to connect it to other software through the API and webhooks.
How to use this guide. Search with Ctrl+F (Cmd+F on Mac) or jump from the contents. The features available depend on your community's plan: Administration → Modules shows what it includes. If something doesn't match your screen, write to us from the Support tab of the platform or at contact@keshercloud.com.
1. Getting started
What KesherCloud is
A management platform for synagogues and Jewish communities, in English and Spanish. Each community has its own independent installation (its own database, backups and address), hosted and maintained by us. The data belongs to the community: it can export all of it whenever it wants.
First sign-in
- We create your installation and the first administrator. You choose the password (at least 12 characters; a long phrase is better): nobody else sees it.
- When you sign in, turn on two-step verification: add the key shown to an authenticator app (Google Authenticator, Aegis, 1Password…) and enter the 6-digit code. It is required for all staff accounts.
- Choose your language with the ES / EN button in the top bar. Your choice is remembered.
- Create your team's accounts in Administration → Users and give each a role (section 2).
If you lose your phone or password
Write to us from another administrator account or at contact@keshercloud.com naming the affected user. We reset access with a temporary password and remove the second factor; the change is recorded in your community's audit log (see section 15). Before doing it, we verify that the request comes from a community administrator.
The main menu
- Community: families, yahrzeits, events, honors, seating, campaigns, dues, school, cemetery, spaces and bookings, email, mourning notices, accounting and community details.
- Administration: users, roles, appearance, modules, audit log, email, payments and system (backups).
- Support: tickets with our team.
- Help: short help for each screen.
- My account: your password, second factor and language.
2. Roles and permissions
A role is a set of permissions. Each team member gets one or more. The platform follows the least-privilege principle: each position sees only what it needs.
| Role | Can | Cannot |
|---|---|---|
| Administrator | Everything: users, roles, appearance, modules, audit log, payments, email, exporting the data | — |
| Secretary | Add and edit families, events, honors, seating, spaces, bookings, bulk email, import and export, community details; view dues, school and cemetery | Change dues or payments; configure online payments |
| Treasurer | Generate dues, record payments, apply credits, issue receipts, donations, accounting, configure online payments | Bulk email, delete or import, school, cemetery |
| Rabbi | Members, yahrzeits, events, email to the whole community, school, burials and plots, bookings | See families' accounts, dues or payments |
| Teacher | Their classes: students, attendance and reports | Anything else |
| Gabbai | Events, honors, seating, yahrzeits, spaces, bookings and the family record | Dues, payments, bulk email, delete, school, cemetery |
| Member (portal) | See and change only their own data in the portal (section 13) | Everything else |
- You can edit the roles, create your own and tick permission by permission in Administration → Roles. The predefined roles are created once: if you change them, they are never overwritten.
- No role except Administrator manages users, roles, appearance, the audit log or system status.
- The "Administrator" role always exists and always has every permission.
3. Families and people
Community → Families. Each family has a membership type, status, contact details and address, and its people (relationship, Hebrew name, date of birth).
- Search by name and filter by status.
- Import from a CSV (the Import families option): one row per person; columns in Spanish or English; a preview that saves nothing; families that already exist are skipped; day/month/year or month/day/year dates; a downloadable template is provided.
- Export to CSV (management permission). To take all your community's data, see section 16.
- Deleting a family needs the management permission and is recorded in the audit log.
4. Hebrew calendar and yahrzeit
The Hebrew calendar is built into the platform and includes the rules for Cheshvan and Kislev and for Adar I/II. On each deceased person's record:
- You save the date of death; the platform calculates the Hebrew date and the next yahrzeit. There is an option for deaths after sunset.
- Community → Yahrzeit lists the next 14 to 365 days and the home panel highlights them.
- Families add and remove their own from the portal.
Note. Today the platform shows yahrzeits on the panel; it does not yet send automatic email reminders.
5. Events and registrations
Community → Events. Calendar with the Hebrew date, capacity, price, registration by family or guest, and a waiting list with automatic promotion when someone cancels. It records attendance and payment.
- An event can be linked to a space: the event's capacity cannot exceed the space's, and the platform warns you if the space is already taken at that time.
- From the event you can write to the registered people.
- Families register and cancel from the portal.
6. Email to families
Community → Email. Send to all families, to a membership type, or to the people registered for an event. Use the {{familia}} and {{titular}} fields to personalize. Every send is logged per recipient.
Setting up the mail server
Administration → Email (administrator only). Choose the type:
- Resend (API over HTTPS): recommended on managed hosting. You only need the API key and the sender address.
- Zoho Mail (API over HTTPS): with a Zoho Self Client.
- SMTP server: for those who have their own.
Important. The provider of the servers where we host communities blocks outgoing SMTP (ports 25, 465 and 587). Use Resend or Zoho Mail via API, which go out over HTTPS.
A domain alone does not send email. You need a sending service and three DNS records on your domain:
| Record | Purpose |
|---|---|
| SPF (TXT at the root) | Authorizes the service to send on behalf of your domain. A domain can have only one SPF: if one exists, merge into it. |
| DKIM (usually 3 CNAMEs) | Signs every message. |
DMARC (TXT at _dmarc) | What to do with what fails SPF/DKIM. Start with v=DMARC1; p=none; rua=mailto:someone@your-domain and tighten later. |
Use Send test (it goes only to the person administering) and check that it lands in the inbox and not in spam. The key is stored encrypted and is never shown again. Without a configured server, sending is simulated: it is logged but nothing goes out.
7. Mourning notices (hodaot)
Communication → Mourning notices. Prepare a death notice and send it to members.
- New notice: choose the notice language (Hebrew, Spanish or English, independent of the panel language), the gender, name, title, memorial abbreviation, relationship, date, time, place and family surname.
- Suggest the text: the platform fills each line of the template with the usual wording for the language, with gender and relationships agreed and the Hebrew date. Every line can be edited by hand: what you see is what is produced.
- Save: you get the notice image (PNG, to share) and a PDF to print.
- Send to members: first "Send me a test", then send to all active families with an email address or to one family type. The email carries the text and the image attached. It is logged like any bulk send.
Viewing and editing notices needs community permissions; sending and deleting needs community management.
8. Spaces and bookings (including the mikvah)
Community → Spaces. The physical spaces (sanctuary, hall, library, classrooms, kitchen, mikvah…) with name, type, capacity and address. Events and classes are linked to a space and the platform prevents clashes.
Bookings
In each space, the "Bookings for this space" section:
- Accepts booking requests (off by default).
- Staff must approve each request (on by default).
- Fixed duration (e.g. 60 minutes for the mikvah).
- Roles that can request it from the portal. If you tick "Member (portal)", families will see and be able to book that space; if you do not, it does not appear for them. The check is done on the server.
The family books from the portal (Book spaces), sees the status (pending, confirmed, declined with a note, cancelled) and can cancel its own.
The secretary manages Services and events → Reservations (permission reservas.gestionar): confirm or decline with a note, book on behalf of a family or cancel a confirmed booking. A confirmed booking occupies the space; a pending one does not. A booking that clashes with another or with an event is never confirmed.
Email notices: to the secretary when a request arrives and to the family when it is resolved. For privacy, the email does not carry the family's notes and, for the mikvah, not the family's name either: that is only visible inside the panel.
9. Honors, seating and campaigns
- Honors (gabbai): aliyot and other honors by date and occasion, with pledges. The "whose turn is it?" panel sorts by kohen, levi and israel (who has gone longest without an honor).
- High Holiday seating: sections with numbered seats, assignment to families or guests, release, and charging to each family's account without charging twice.
- Campaigns and donations: campaigns (donation, Shalach Manot, Maot Chitim…) with goal and progress; donations with "in memory of" and an anonymous option (the name is only visible to editors); printable yearly summary per family.
10. Dues, payments and receipts
Community → Dues.
- Set the amount per membership type and generate the annual dues for all families (idempotent: it does not duplicate).
- Create manual charges and choose their concept.
- Each payment is applied to a specific charge (membership, seat, tuition…), not to "the debt in general". Each charge is pending, partial or paid.
- If a payment exceeds what is due, the excess stays as a credit for the family, which you later apply to another charge.
- Voiding a charge returns what was applied as credit.
- Printable statement, balances, overdue and CSV.
Receipts
A fully paid charge has a Receipt link (for staff and in the portal's My account). It is printable, carries the community's name, address and tax ID, the concept, the amount and the payments applied. It has its own stable number (R-YYYY-NNNN). Fill in Community → Community details (country, state, EIN or other ID) so they come out right.
11. Online payments
Administration → Payments (permission pagos.gestionar). There are four options:
- Stripe and PayPal: dues and donations.
- Donorbox: donations only.
- A simulated gateway for testing and demos.
Principles
- KesherCloud never sees card data: payment happens on the provider's page.
- Each community uses its own account at the provider: the money goes directly to it and we never hold it.
- The amount always comes from the platform's data, never from the browser.
- One active provider per installation.
Connecting Stripe (test mode first)
- In Stripe, with test mode on, copy the secret key (
sk_test_…). - In Administration → Payments paste it and save. It is stored encrypted and never shown again.
- In Stripe, Developers → Webhooks → Add endpoint, with the address the screen shows (
https://YOUR-INSTALLATION/payments/webhook/stripe) and these events:checkout.session.completed,checkout.session.async_payment_succeeded,checkout.session.async_payment_failed,checkout.session.expiredandcharge.refunded. Copy the signing secret (whsec_…) into the second field. - Test the connection (it must say test mode) and Activate payments.
- In the portal of a family with a balance, press Pay now and use the test card
4242 4242 4242 4242(any future date and CVC). - The charge appears in Dues → Online charges and the payment in the family's account.
PayPal uses Client ID, Secret and Webhook ID. Live keys are enabled when the community decides, together with us.
How a charge works
The family presses Pay (one charge or everything outstanding) or Donate → the platform creates a pending charge and sends them to the provider's page → the provider notifies with a signed webhook → the platform checks the signature, the time (5 minutes), that it has not been processed already, that amount, currency and mode match, and only then records the payment, once.
Partial payments and refunds
- Partial online payments: an option in Payments → Payment rules, off by default. Staff can always record a partial payment received another way.
- Refunds: the notice marks the charge as refunded and alerts staff. The books are never changed automatically: in Dues → Online charges use "Settle in the books" to remove the payment or donation (it is recorded in the audit log).
12. Accounting
Principle: KesherCloud is the subsidiary ledger of the families (who owes, who paid, who donated). Your accounting software (QuickBooks, Xero, Wave…) receives a summary journal. There is no two-way synchronization: the accounting software never modifies families, charges or payments.
Community → Treasury → Accounting (permission contabilidad.gestionar).
Community currency
In Accounting → Currency you choose the currency in which your community manages dues, charges, payments, donations, prices and accounting: US, Canadian or Australian dollar, euro, pound, Mexican, Argentine, Chilean, Colombian or Uruguayan peso, real, sol, guarani, colón, quetzal, Israeli shekel, Swiss franc and others. Every amount is shown and exported in it, including the CSV, the accounting API and the accounting webhook.
- Choose it before you start. Once there are charges, payments or donations it cannot be changed (the stored amounts would mean something else). If you need to change it, write to us from Support and we will do it with you.
- Currencies without decimals (Chilean peso, guarani): whole pesos are stored;
12.500is read as twelve thousand five hundred. - Online payments: Stripe charges in all of these currencies (if your Stripe account has them enabled); PayPal only in US, Canadian and Australian dollar, euro, pound, Mexican peso, real, shekel and Swiss franc. The platform does not let you activate a gateway that does not charge in your community's currency.
Chart of accounts
Enter, as it appears in your accounting software, the account (and an optional class) for:
- each income concept for charges: membership dues, tuition, seats, plots and others. You can add your own ("Hall rental", "Kiddush", "Mikvah"), rename them and remove the ones you do not use;
- each donation campaign;
- each payment method (deposit account): transfer, check, cash, card, other, and your own ("Zelle", "Venmo"…);
- accounts receivable and fee expenses.
Journal by period
Preview with totals and CSV download. Each movement is a two-line entry:
| Movement | Debit | Credit |
|---|---|---|
| Charge to a family | Accounts receivable | Income of its category |
| Voiding a charge | Income of its category | Accounts receivable |
| Dues payment | Deposit account (method) | Accounts receivable |
| Donation | Deposit account (method) | Income of its campaign |
| Gateway fee | Fee expenses | "Card" deposit account |
CSV columns: Date, Entry, Type, Name, Memo, Account, Class, Debit, Credit. Entry (charge-12, payment-5, donation-7, fee-3, charge-void-12) is the movement's stable identifier: it never changes and lets you avoid importing it twice. Anything without an assigned account comes out as UNMAPPED and the preview tells you what is missing.
Known limits: dates are UTC; a refund is corrected in the platform but does not appear as a separate entry; the provider's grouped payouts are not reconciled with the bank.
13. The family portal
Each family signs in with its own account (role Member (portal)). Staff grant or remove access from the family record (a temporary password, shown once). These accounts are not required to turn on the second factor, though they can.
The family sees and changes only its own data:
- Its record and contact details.
- Yahrzeits: add and remove its own.
- Events: register, see the status and cancel.
- My account: charges, payments and donations; pay online and download the receipt for each paid concept and its donation statement.
- Book spaces (if its role can request any).
- Its plots and the burials of its relatives (if there is a cemetery).
14. Religious school and cemetery
School
Community → School (permissions escuela.ver and escuela.editar). Classes per year (level, teacher, schedule, enrollment), students taken from the people of active families, daily attendance (present, absent, excused), reports per period with grade and comment, tuition charged to each family's account, and a notice of upcoming Bar/Bat Mitzvahs (13 Hebrew years from the date of birth). The teacher takes attendance and writes reports but sees nothing else.
Cemetery
Community → Cemetery (permissions cementerio.ver and cementerio.editar). Cemeteries with plot sections (color grid: free, reserved, occupied), plot reservation to a family with a price, burials with date of death and Hebrew date (which can create the yahrzeit at the same time), and plot charges to the account without charging twice. The family sees its plots and its relatives' burials in the portal.
15. Security, privacy and audit
- Second factor required for staff; passwords protected with Argon2id; lockout after failed attempts.
- Everything travels encrypted (HTTPS). Email, payment and second-factor keys are stored encrypted.
- Least-privilege roles and permission checks on the server.
- Audit log (Administration → Audit log): every important change is recorded in a tamper-evident chain and the platform checks its integrity.
- Our team's access. We only enter your community's data for the support you ask for or for security or maintenance reasons, and every access is recorded with its reason in Administration → Audit log → KesherCloud team access. If you see one you do not recognize, write to security@keshercloud.com.
- Your data is yours. We do not sell it, use it for advertising or use it to train AI models. Read the Terms, the Privacy Policy and the Data Processing Agreement.
- Minors: data about minors is entered by the community, which is responsible for having parental or guardian authorization.
16. Backups, export and leaving
- Daily encrypted backups, with a second copy in another place outside the server. Restore is tested. Administration → System shows the state of the latest backup and of the external copy, and the home screen warns you if they are not up to date.
- Export all my data: Administration → System → "Export all my data" (administrator-only permission). It downloads a ZIP with one CSV file per table (families, people, dues, payments, donations, accounting, events, school, bookings, cemetery, users and audit log), a
manifiesto.jsonand aLEEME.txt. It does not include passwords, keys or secrets. Each download is recorded in the audit log. The file contains personal data: keep it somewhere safe. - Leaving: when the contract ends you have 30 days to export your data. After that we delete it from active systems and, 60 days later, from the backups.
17. API and webhooks
The platform offers these interfaces today to connect it with other software:
| Interface | Purpose | Address |
|---|---|---|
| Accounting API (read-only) | Read the accounting journal as JSON | GET https://YOUR-INSTALLATION/api/v1/accounting/… |
| Outgoing accounting webhook | KesherCloud notifies you of every new entry | An address of yours, https://… |
| Payment webhooks (incoming) | Stripe and PayPal notify KesherCloud | POST https://YOUR-INSTALLATION/payments/webhook/{provider} |
YOUR-INSTALLATION is the address of your KesherCloud. The accounting API and webhook are in Community → Treasury → Accounting → Connections (permission contabilidad.gestionar); depending on your community's plan they may or may not be included.
Coming soon: a public API and embeddable widgets to show events, times and the Hebrew date on the community's website. It is not available yet; this document only describes what works today.
17.1 Accounting API
Keys. In Connections create a key (sk_…). It is shown only once, only its fingerprint is stored, and it can be revoked. It only gives read access to the journal (accounting:read). A platform session does not authorize the API.
Authentication. Send the key in the header Authorization: Bearer sk_….
Limits. 120 requests per minute per key; attempts with invalid keys are throttled per address. Responses are not cached (Cache-Control: no-store).
Check the key
curl -s https://YOUR-INSTALLATION/api/v1/accounting/ping \
-H "Authorization: Bearer sk_YOUR_KEY"
{"ok": true, "version": "v1", "key": "QuickBooks", "scope": "accounting:read"}
Read the journal
GET /api/v1/accounting/journal?from=YYYY-MM-DD&to=YYYY-MM-DD
| Parameter | Required | Description |
|---|---|---|
from, to | Yes | Date range YYYY-MM-DD (from ≤ to) |
limit | No | 1 to 2000. Default 500 |
cursor | No | The next_cursor of the previous response (opaque) |
curl -s "https://YOUR-INSTALLATION/api/v1/accounting/journal?from=2027-01-01&to=2027-01-31&limit=500" \
-H "Authorization: Bearer sk_YOUR_KEY"
{
"from": "2027-01-01",
"to": "2027-01-31",
"currency": "USD",
"entries": [
{
"entry": "payment-5",
"date": "2027-01-12",
"type": "payment",
"name": "Alfa",
"memo": "check",
"currency": "USD",
"complete": true,
"lines": [
{"account": "1010 Checking", "class": "", "debit_cents": 20000, "credit_cents": 0},
{"account": "1200 AR", "class": "", "debit_cents": 0, "credit_cents": 20000}
]
}
],
"next_cursor": null,
"unmapped": []
}
entryis the stable identifier: use it to avoid importing the same entry twice.complete: falsemeans a line has an account that is not assigned in the chart of accounts.- Amounts (
debit_cents,credit_cents) are in the minor unit of your community's currency: cents for the dollar or euro (20000= 200.00) and whole pesos for the Chilean peso or guarani (12500= 12,500 pesos). Thecurrencyfield of the response and of each entry (ISO code, e.g.USD,EUR,CLP) tells you which: do not assume dollars. - Entries come sorted by date and
entry. Ifnext_cursoris notnull, repeat the request withcursor=to continue. unmappedlists the accounts still to be assigned.
A Python example that walks all pages:
import requests
BASE = "https://YOUR-INSTALLATION"
KEY = "sk_YOUR_KEY"
def entries(date_from, date_to):
cursor = None
while True:
params = {"from": date_from, "to": date_to, "limit": 500}
if cursor:
params["cursor"] = cursor
r = requests.get(f"{BASE}/api/v1/accounting/journal", params=params,
headers={"Authorization": f"Bearer {KEY}"}, timeout=30)
r.raise_for_status()
data = r.json()
yield from data["entries"]
cursor = data["next_cursor"]
if not cursor:
break
for e in entries("2027-01-01", "2027-01-31"):
print(e["entry"], e["date"], e["complete"])
Errors
All error responses have the same shape:
{"error": {"code": "unauthorized", "message": "Missing or invalid API key"}}
| HTTP | code | Cause |
|---|---|---|
| 400 | invalid_request | Missing from/to, invalid dates, limit out of range or invalid cursor |
| 401 | unauthorized | Key missing, wrong, revoked or with another scope |
| 429 | rate_limited | Too many requests; wait as the Retry-After header says |
17.2 Outgoing accounting webhook
Instead of polling the API, you can ask KesherCloud to notify you of every entry.
Setup (Connections):
- Enter the address of your receiver (
https://…;http://and private or local addresses are not accepted). - Save. The signing secret (
whsec_…) is shown only once: keep it; it is stored encrypted. - Choose the date to send from ("Send from") and enable it. Use "Send test notice" to check the connection.
What is sent. Each entry once, as soon as it appears in the journal and only if it is complete (all its accounts assigned), from the activation date onward. An entry that was already sent is not resent if it changes later: for that there are the CSV or the API.
Request. POST with Content-Type: application/json, the headers X-Event-Type (journal.entry or ping), User-Agent: KesherCloud-Webhook/1 and X-Signature (see below), and the body:
{
"id": "evt_payment-5",
"type": "journal.entry",
"created": 1799000000,
"data": {
"entry": "payment-5",
"date": "2027-01-12",
"type": "payment",
"name": "Alfa",
"memo": "check",
"currency": "USD",
"complete": true,
"lines": [
{"account": "1010 Checking", "class": "", "debit_cents": 20000, "credit_cents": 0},
{"account": "1200 AR", "class": "", "debit_cents": 0, "credit_cents": 20000}
]
}
}
idnever changes for the same entry: use it to avoid processing twice (retries repeat it).typeisjournal.entry, orpingin the test notice (with emptydata). The currency is indata.currency.createdis the send time in Unix seconds.
Signature. Every request carries the header X-Signature: t=<time>,v1=<hex>, where v1 = HMAC-SHA256(secret, "<time>.<body>"). Always verify the signature using the body exactly as received (raw bytes, not reformatted) and reject times more than 5 minutes off.
import hmac, hashlib, time
def signature_valid(secret: str, header: str, body: bytes) -> bool:
p = dict(x.split("=", 1) for x in header.split(","))
if abs(time.time() - int(p["t"])) > 300:
return False
expected = hmac.new(secret.encode(), p["t"].encode() + b"." + body,
hashlib.sha256).hexdigest()
return hmac.compare_digest(expected, p["v1"])
// Node.js (Express): use express.raw({type: "application/json"}) to keep the original body
const crypto = require("crypto");
function signatureValid(secret, header, body /* Buffer */) {
const p = Object.fromEntries(header.split(",").map(x => x.split("=", 2)));
if (Math.abs(Date.now() / 1000 - Number(p.t)) > 300) return false;
const expected = crypto.createHmac("sha256", secret)
.update(`${p.t}.`).update(body).digest("hex");
const a = Buffer.from(expected), b = Buffer.from(p.v1 || "");
return a.length === b.length && crypto.timingSafeEqual(a, b);
}
Response and retries. Reply with any 2xx in under 10 seconds and process in the background. Redirects are not followed. If you fail, it is retried with increasing waits: 1 min, 5 min, 30 min, 2 h, 12 h, 24 h and 24 h (8 attempts in total). An entry that runs out of attempts is marked failed; removing and recreating the webhook restarts the deliveries. The screen shows counters (sent, pending, failed) and the latest deliveries with their last error.
Best practices: store the id of every processed event; reply quickly; verify the signature before doing anything; do not rely on arrival order; and do not expose the secret.
Webhooks deliver new events. There is no retroactive sending: for history use the API with a date range or the CSV.
17.3 Payment webhooks (Stripe and PayPal)
These are notices the provider sends to KesherCloud, not the other way around. You configure them in the provider's dashboard with the address shown by Administration → Payments: POST https://YOUR-INSTALLATION/payments/webhook/stripe (or /paypal). Event details and steps are in section 11. KesherCloud checks the HMAC-SHA256 signature (5-minute tolerance; several secrets are accepted so they can be rotated), processes each notice only once and rejects notices with a different amount, currency or mode. Donorbox does not use webhooks: the platform polls its API every few minutes.
18. Appearance, branding and language
- Appearance (Administration → Appearance): one-click ready-made styles (Classic, Warm, Modern, Elegant, Fresh), a palette or your own color with a contrast check (minimum 4.5:1), font size and typeface, corners and default light or dark mode (each person can change it).
- Own branding: upload the community's logo; it appears in the platform, receipts and the donation statement.
- Language: English and Spanish throughout. Mourning notices can also be produced in Hebrew.
19. Modules and plans
All installations run the same program; your plan decides which functions are on. Moving up a plan means turning functions on, without reinstalling or moving data. In Administration → Modules you see what your plan includes and can turn off what you will not use: it disappears from the menus but no data is deleted, and you can turn it back on.
20. Technical support
- Support tab in the platform: open a ticket (permission
soporte.usar) and we continue the conversation there. Each ticket has a unique reference likeKC-00012; quote it if you write to us by email. - Email: contact@keshercloud.com. For privacy matters, privacy@keshercloud.com; for vulnerabilities or access you do not recognize, security@keshercloud.com.
- Your server's status: your installation sends us a technical report every few minutes (version, disk, backups, errors) with no data from your community. If something fails, we see it and open a ticket.
When you write to us, it helps a lot to include: what you were trying to do, what happened, the screen (a screenshot) and the approximate time. Never send us passwords, payment keys or verification codes; we never ask for them by email.
21. Frequently asked questions
Where is my data? In your independent installation, on servers we contract. Backups go encrypted to a second place.
Can I take my data with me? Yes, at any time: Administration → System → Export all my data.
Is card data stored? No. Payment happens on the Stripe, PayPal or Donorbox page with your community's account.
Can your team access my data? Only for the support you ask for or for security, and every access is recorded and visible to you.
An email does not arrive or goes to spam. Check the domain's SPF, DKIM and DMARC (section 6) and use "Send test".
An online payment does not appear. Look at Dues → Online charges: if the charge is pending, the provider has not confirmed yet; if it fails, check that the Stripe webhook has the five events and the right secret.
My webhook receiver gets the same request several times. That is normal if you did not reply 2xx in time: they are retries. Use the event id to ignore repeats.
The API returns 401. Check that you use Authorization: Bearer sk_…, that the key is not revoked and that it is an accounting key.
I want to change plan or close the community. Write to us from Support.
22. Glossary
| Term | Meaning |
|---|---|
| Yahrzeit | Anniversary of a death according to the Hebrew calendar |
| Hodaa / Hodaot avelut | Mourning notice(s) |
| Mikvah | Ritual bath |
| Kibudim / aliyot | Honors in the Torah reading |
| Gabbai | The person who organizes the honors and worship |
| Kohen, levi, israel | The three traditional categories for honors |
| High Holidays | Rosh Hashanah and Yom Kippur |
| Bar/Bat Mitzvah | Religious coming of age (13 Hebrew years) |
| Shalach Manot, Maot Chitim | Purim and Passover campaigns |
| Journal entry | An accounting movement with debit and credit lines |
| Webhook | An automatic notice one program sends to another when something happens |