Overview

Settled Revenue
K0.00
0 paid bookings
Total Bookings
0
Across all tiers
Pending Verification
0
Bank deposit slips waiting
Live Sponsor Logos & Page Artwork
0
Active content blocks

Takings by Payment Status

Loading takings…

Quick Operations

Recent Registrations

#ReferenceNameContactEntryStatusWhen

Attendee Registrations

Click any row to view its printable Report PDF.

ReferenceAttendee Contact Entry & Amount Status WhenProof

Attendee Roster & Comms Consent

Everyone on the guest list: imported guests, every player on a booking (paid or awaiting payment) and the Sponsor & Vendor Passes, with their package, their Broadcast channels and their messaging consent. Broadcast's channels draw on this list.

ReferenceGuest Name Package / pass Contact Organisation Channels SMS Email
📋 Roster Summary PDF

GUEST ROSTER DIGEST

Tournament Guest List & Messaging Consent Report
Total Registered Attendees 0
SMS Comms Consents 0 opted in
Email Comms Consents 0 opted in
Report Date 24 Aug 2026
This document is an authenticated export from the tenant ledger on the UnityZM operations platform.

Bring a guest list in from a spreadsheet. CSV, TSV, JSON and Excel (.xlsx) are read directly. Columns are matched by what they mean, so "Full Name", "Guest" and "Attendee" all land on the name — you do not have to reshape the file first. Nothing is written until you have seen the preview.

Choose a file

Everything stays here — the file is read by this site, not sent anywhere.

Entrants

Every named person inside a booking. A Team of 4 is four entrants — tickets and check-in are per person.

#NamePhoneEmailBookingEntrant referenceWhen

Edit players

Rename the players on a booking, set their phone and email, add a player up to the package's size, or remove one who has not checked in. Each player keeps their reference, so tickets already sent keep working. The booking's amount, package and payment never change here.

Renaming keeps the same ticket. To replace a person, remove them and add the new player, so the old ticket stops working.

The Draw

Players in flights of four, each flight with the hole it starts on (a shotgun start). Everyone with a paid or pending booking in the packages ticked below is in it. A booking stays together.

Holes follow the order of the flights: until the draw is locked, moving a booking can empty a flight and shift the holes of the flights after it. A hole you type stays put.

FlightHolePlayers

Draw settings

Which packages play, and how many players one booking brings (a four-ball is 4). A package whose own words say it is not golf (no golf, a vendor stand, a social or guest ticket) starts unticked: check the ticks before you make the draw. A booking with fewer names than its players keeps its places, held as “Player to be named”.

Logos on the sheet

JPEG or PNG. The left logo is the event's own logo unless you upload one here; the right logo is a partner's. Either can be left empty.

Sponsors and vendors

Each row gets one booking with one pass per person. A pass is free: it is never counted as money, and it does not take a package place. Generating sends nothing. A pass goes out only when you press Send on its row.

On a site whose bookings are kept by the booking system, passes stay on this site: you will find them here, on Tickets & Check-in and on Entrants, not in Registrations or the Guest Roster, so those counts differ.

Add a sponsor or vendor

Holder names are used when the passes are generated. A pass with no holder name reads “Name pass 1”.

Paste or import a list

One per line: name, type, phone, email, passes. Only the name is needed. A file can be CSV, TSV or Excel (.xlsx). Anyone already on the list is left as they are.

Check a guest in

Tap Scan QR to use the camera, or paste the link, or type the reference however they read it out.

One ticket per person, not per booking. The QR carries a signed token, so a ticket cannot be minted by copying someone's booking reference. Hand over the link — it reopens if the message is deleted.

Issued Tickets

Grouped by booking.

#NameBookingArrivedTicket link

Email a file to everyone

Send one file (the Draw, a programme) to every paid guest, every staff account and every site user with an email. The email carries a private link to the file, and each address gets it once.

1. The file

A PDF, PNG or JPEG, up to 10 MB.

SendFileUploadedSentLink

2. The email

3. Who receives it

GroupPeopleWith emailNo emailEmail not confirmedNot opted inNever send

4. Send

Sent one at a time at the email service's pace. Sending again only reaches those who do not have this file yet.

Broadcast: compose and preview

Write one email and one SMS, import the recipients, see the message exactly as it will look, send yourself a test, then send it to the list. Only step 7 sends to the list, and only an owner, after typing the counts.

1. The email

Contact us and the social links are kept in Site details (Public details), the same ones the site's pages show. Change them there.

Header and footer images

Like the invoice letterhead: a JPEG, PNG or WebP under 1 MB each. The header goes across the top of the email in place of the logo band; the footer image sits above the footer that carries the stop link. Saved at once; the preview shows them after you save the draft.

Header
Footer

2. The SMS

0 characters, GSM-7, 0 SMS

3. How it will be delivered

4. Recipients

Import the people to send to from a CSV file with the columns name, organisation, phone, email (any order; organisation is optional; other columns are ignored). At most 1 MB and 5,000 rows. Phones are read as Zambian numbers into +260 form; a phone or email already on an earlier row is used once. A new import replaces the list. Nothing is sent here: step 7 sends.

From your guests, by channel

Channels fill themselves from your guest list (the players on each booking, by package, and the Sponsor & Vendor Passes), and from the guests you tag below. Tick the channels to send to, then Use these channels: it makes the recipients list below, with the same checks as a CSV import.

ChannelFills itself fromPeoplePhones / emails
Or import a CSV file (replaces the list):

5. Preview

The preview shows the saved draft. The stop link in the footer, and a first name where the text has {{first_name}}, are filled in for each person when it is sent. Write {{first_name|friend}} to choose the word used when a name cannot be used.

6. Send a test

On this site a test goes only to your own email.

7. Send to the recipients

Sends the saved draft to the imported list, in the background at a few messages a second. Each person gets each message once: pressing Send again reaches only those who have not had it. An owner sends, after typing the counts shown. Managers can watch and press Stop.

    Staging test recipients

    This is a staging site: every SMS, WhatsApp and email goes only to the phones and emails on this list, and anyone else is refused before the messaging service. Add your own test numbers and emails here, one at a time. A change applies to the next message, with no redeploy.

    No names, commas or several at once. A phone is kept in the +260 form; an email in lower case.

    Added in Admin

    KindRecipientAdded

    Set at deploy

    From the site's deploy settings (MESSAGING_ALLOW_ONLY). They cannot be changed here.

      Addresses are shown masked: the first letter and the domain, or the last three digits.

      A vendor can answer HTTP 200 and still not send anything. The result below is the vendor's own verdict, not the transport's — which is the only way "Insufficient bundles" looks different from success.

      Delivery Log

      Newest first.

      ReferenceChannelToWhatResultVendor statusWhy notWhenAction

      Messaging Vendor

      SMS and email for tickets, reminders and receipts.

      Vendor, channel and backup settings

      The vendor

      One account and one key serves all three channels.

      A queued message is not a delivered one — the callback is how the vendor tells us which it was.

      SMS

      What recipients see as the sender. Most networks cap this at 11 characters.

      Email

      The vendor rejected email as Invalid Sender on 26 Aug. It must be an address they have verified for this account.

      WhatsApp

      Off until a test message actually arrives — the vendor accepting one is not the same as a handset receiving it.

      WhatsApp is a separate account from SMS on this vendor and does not accept the SMS API key. Without these two it answers Missing required keys and nothing is delivered.

      These two are settings rather than fixed, because this vendor uses a different field per channel — email needs email_body where SMS needs message, and the wrong one is accepted and then queues nothing. If a test is accepted but never arrives, change this first.

      Purchase alerts

      Three channels to two numbers is five messages for one booking. "First that works" tries WhatsApp, then SMS, then email, and stops as soon as one is actually accepted — a refused channel still falls through to the next.

      Two numbers, because the person on the gate and the person doing the money are rarely the same person. Both get the alert on whichever channel sends.

      Backups

      Daily. Recent copies are kept on the server. The email is a short summary only (time, size, checksum, row counts) and never carries guest or member data; staff download the full backup under Staff & Access → Download backup.

      Two mailboxes, because one is a single closed account away from being no backup at all. Each copy is sent and reported separately — "one of two sent" is the case worth knowing about.

      Who gets told

      A bank transfer needs a human to release the ticket. Without an address here, nobody is told a slip has arrived.

      Send a test

      This sends a real message and costs real money. Use your own number or inbox.

      The checks a person would otherwise run by hand. Dry run exercises the real code — it builds the request, then describes it instead of sending — so the payment provider is not called and nobody is texted. Nothing is written either: the booking, entrants and ticket below are made in memory and thrown away.

      Test data

      Prefilled — change anything you want the checks to use.

      A ticket is per person, so two names means two tickets and two passes.

      Every invoice sent by email, as it stands now. A guest who uploaded a proof of payment (POP) shows under POP to check: open it in Payments to Verify, check it against the bank, then Authorise there. Nothing here changes a booking.

      InvoiceBookingBill toAmountIssuedDueStatusAction

      Guest limits

      A guest stuck on a limit (3 invoice codes an hour for one email, a few bookings in 10 minutes for one phone or email, or for one network address): type it, see what is limited and until when, then reset. The trail records that a limit was reset, never the email, number or address.

        Bank transfers land here as recorded — the guest says they have paid and has usually attached a slip. Check it against the bank, then Authorise. That is the moment the booking becomes paid and the ticket is issued; nothing here happens on its own.

        Awaiting Verification

        Newest first.

        ReferenceGuestEntryAmountSlipReceivedAction

        Transactions

        Every payment the site takes, of every type, including the ones that did not go through: its amount (the price), the fee on top, the total charged and the wallet it was paid into, all as recorded when it was made. Customer reference is the payment's identity outside this system, and it only exists once a payment settles. On mobile money it is the id on the payer's own SMS (MP260825.2136.A28446 on MTN, a long number on Airtel) — match on that when someone rings about a payment. On card it is the gateway's id, which the payer never sees; match those by amount and time instead.

        …

        WhenReferenceTypeFor PayerMethod AmountFeeTotal charged WalletStatus Provider referenceCustomer reference

        Record a Consent Decision

        Booking confirmations always send. They are part of what the person asked for, so they cannot be switched off here and are not listed alongside.


        Or give them the link and let them choose for themselves — a decision someone makes personally is a stronger record than one entered here.

        Recorded Decisions

        Who has agreed to receive reminders and promotions.

        Name Destination Channel What for Decision How When

        Add a Staff Member

        What Each Role May Do

        A steward deliberately cannot see takings. The guest list they do need already carries enough personal data.

        Every capability, role by role
        CapabilityOwnerManagerSteward

        Staff Accounts

        Disabled rather than deleted — an audit line naming someone who no longer exists is worse than a disabled row.

        NameRoleByStatusAddedChange

        Reset this event

        Clears the bookings, entrants, messages, support and work items, and reduces staff to one owner — you. Everyone else loses access and you get a new password. Payment and messaging credentials are always kept.

        …

        Restore a backup

        Puts the data and the design back. A backup is signed and bound to the site it came from — one taken elsewhere is refused as Host Invalid unless you deliberately override it.

        Audit Trail

        Every change, and who made it. Reads are not recorded.

        WhoRoleActionSubjectDetailWhen

        These are the tenant's members in the platform — the people who sign in to the portal itself. They are separate from the Staff & Access accounts above, which sign in to this event site only.

        Invite a Member

        They get an invite email asking them to accept (the link works once, for 7 days). They join when they accept; someone new chooses their own password then. Nobody is given a password by someone else.

        Platform Members

        Active tenant memberships and their roles.

        EmailNameRoleChange

        Entry packages

        What guests can book. Flip On sale to show or hide a package on the page; with none on sale the booking form is hidden.

        Loading packages…
        PackagePricePlacesOrderOn sale

        The key is how bookings name the package; it cannot change once used. A package switched off may not be listed on every site: to bring one back, add it again with the same key.

        The wording shown on each package card, line by line. Lines are saved as text and rendered as text — a line cannot bring its own markup onto the public page.

        Add a package

        It is added to the event page and the booking form; then give it wording and a picture below.

        Dashboard

        Money received

        Confirmed gifts, by day.

        How people give

        Confirmed gifts in the period, by payment method.

        From started to confirmed

        Gift sizes

        Confirmed gifts in the period, by size.

        Needs attention

        Waiting on a person, whatever the period.

          Website

          What the public site is running with.

            Enquiries in the period

            Latest gifts

            The ten newest, by reference. Names stay on the Donations screen.

            Site activity

            Page views

            Pages seen, by day.

            Where visitors come from

            Page views in the period, by how the visitor arrived.

            Devices

            Top pages

            Views and average time on the page.

            Search, social and other sites

            Only the site's name is kept, never the search words or the link followed.

            Most clicked

            Buttons and links, across all pages.

            Click heatmap

            Where people click on a page. The page is shown as it is now, without its scripts.

            Choose a page.
            Fewer clicksMore clicks

            Bots and crawlers

            Search engines, AI crawlers, SEO tools, link previews and scanners that asked for this site in the period. They are never counted as visitors.

            For a whole group

            Allow: nothing is said to it. Ask to stay away: the site's robots.txt tells it not to read the site; well-behaved bots obey. Block: asked to stay away and, once the web server is connected, refused outright. Hide: left out of these figures only.

            Sitemap

            The pages search engines should know about, one per line (for example /donate/).

            robots.txt

            What the site tells bots, from the rules on the left.

            
                      

            Donations

            Every gift, newest first. Open one to see its whole payment journey, check a bank slip, or view its receipt. A mobile money gift is confirmed only when the payment provider reports the money settled; a bank gift is confirmed once a person has compared its slip with the bank statement.

            WhenReferenceDonorMethodAmountStatusOpen
            Loading…

            Members

            People who registered on the site to follow their gifts. A gift is linked to a member only when they were signed in while giving; earlier gifts are not linked.

            Looking after an account: open a member to see their status and dates, and to send a confirmation code, confirm their email, give a reset code (read out by phone, or emailed), sign them out everywhere, suspend, edit or delete the account. Check who you are speaking to first; every action asks why, and goes in the audit trail.

            Loading…

            The site's theme, pages and wording, as stored for this site. These are plain settings editors for now; the full screens follow. Each save names the version you loaded: if someone else saved in between, yours is refused and nothing is lost — reload and apply your change again. A theme whose colours are hard to read is refused, naming the pair.

            Public details

            What the public site shows for contact, giving and social links. Saved into this site's settings and read by the site within a minute. An empty field is not shown on the site.

            Contact
            Charity
            Bank account

            Shown on the giving page for bank transfers.

            Mobile money
            Social links

            Full web addresses, starting https://.

            About page

            More of your story, shown on the About page once it is filled in (a site whose pages show it). Plain text; line breaks are kept.

            Gift amounts

            Whole amounts in the giving currency (not set). These are the same amounts online giving checks, so the page and the payment always agree.

            Theme

            Pages and sections

            Wording

            Every wording region the public page declares. Leave a field blank to keep the page's own shipped wording — saving a half-filled form never blanks a section. Lines are stored and rendered as text: a line cannot bring its own markup onto the page.

            Add Sponsor Logo or Advert

            Read aloud to people who cannot see the image. Required.

            Not SVG. An SVG can carry script, and served from this address it would run with this admin's privileges — so the server refuses it. Export the logo as a PNG with a transparent background.

            Artwork Guidelines

            • Sponsors Rail: Clean horizontal logos on transparent or solid white plates render best in the looping marquee.
            • Adverts: Featured sponsor banners shown between tournament overview sections.
            • Event Logo: Primary brand mark displayed in the hero section and navigation.
            • Caching: Live updates take effect immediately and cache for ultra-fast mobile loads.

            Current Live Artwork

            0 items

            Event logo and hero image

            The mark and the main picture for the event itself. Each event has its own. Leave one unset and the page falls back to the artwork built into it.

            Event branding

            Each event's colours, fonts and background are now set on its Event identity screen, with its words, details, partners, photos and news.

            Event identity

            Everything that makes this event look like itself, in one place. An event with nothing set here shows exactly what it showed before.

            The preview shows the saved identity. Save first to see a change.

            Copy identity from…

            Fills this form from another event as a starting point. Nothing is saved until you press Save identity (and Save colours and fonts for the look), and nothing stays linked to the other event. Copied as text: tagline, summary, description, venue, course, dress code, map link, extra details, page sections, background kind and shade, Shared or own, news tags, alt texts and share text. Not copied: the title, the date, the other event's album and photos, its logo, main poster, background picture and video, and the alt texts of its logo and main poster. Copied pictures are drafts: they show nowhere and replace nothing until you press Save identity; one you leave out, or never save, is deleted (unsaved drafts after 24 hours).

            Identity check

            What this event still has nothing of its own for.

              Look

              Inherit the site's look, or give this event its own colours, fonts and background. Its look shows on this event's pages only (its event page, booking, coming-soon and past pages); the website and the other events keep the site's look.

              Background

              Background shade

              How far the background is darkened so the words read, as for Home.

              Background video sound

              Whether this event's background video may play with sound once a visitor turns it on (Sound on / Mute and Pause at the foot of the page), on its own page and on its slide on Home.

              Logo and posters

              The order below is this event's page slideshow, and its first picture is the event's slide in the Home carousel. Drag a picture to move it, or use Up and Down. Give each an alt text that says what it shows. Pictures are checked as JPG, PNG or WebP and their metadata is removed.

              Logo

              Main poster

              Extra posters and pictures

              The photos of this event's own album in Website photos are listed too.

              Order

                Sharing

                What a WhatsApp or Facebook link card shows for this event's page. Left empty, the card shows what it showed before.

                Preview

                How a link card looks. Each app draws it a little differently.

                Address and QR code

                Words

                Plain text only. A section switched off is left off this event's page.

                Page sections

                Details

                Each detail shows on the page only when it is filled.

                Extra details

                Up to four more, such as Format: Fourball.

                Shared or own

                Shared shows the site's items, the same on every event that shares them. Own shows only this event's. "As before" keeps what the event showed until now.

                Event Information & Schedule

                Tickets open the gate from midnight on the first day until 6am after the last day. Leave it empty for a one-day event. At most 14 days after the start.

                Bank Transfer Instructions

                Shown to attendees who choose offline direct bank transfer.

                {prefix} {date} {time} {yy} {seq:3} {rand:6} — guests read this out and write it on deposit slips, so shorter is kinder. Random characters are always appended if your format has none, because a guessable reference exposes other people's bookings.

                These are shown to guests paying by transfer, with their booking reference. A transfer with no reference cannot be matched to a guest.

                Proof Verification Policy:

                Attendees upload deposit slips upon registration. Staff confirm payments in the Registrations tab before issuing final admission badges.

                Requests from the site

                Sent from the Help button and the site's contact, enquiry and sign-up forms. A reply is delivered to the contact they left.

                Reviews from the site

                A review shows on the website only once you approve it, with the name the person typed. Rejected reviews are removed after 180 days.

                Checks Passing
                —
                probed live, not declared
                System Node Runtime
                —
                Uptime: —
                Memory Allocation
                —
                Lightweight BFF Engine
                Collecting Into
                —
                —
                Time Booked
                —
                on open items

                Work Items

                Things your team has decided to do. These are real records — add, assign and close them here.

                #ItemPagePriorityOwnerStatusWorkedAdded
                Email me when work changes

                Capability Checks

                Each row is answered by inspecting this deployment right now. Nothing here is a status somebody typed in.

                CapabilityStateEvidence

                What the home page shows

                Showing now: …. Nothing changes on the site until you save here.

                Website videos

                Videos for the website. The first plays just under Home's picture with a few words around it; with more than one, visitors choose from the list beside it. MP4 files only, up to 100 MB each and 24 videos. They show while a design is chosen and the home page is the Website.

                The design's Videos page (/videos, in the menu while a video is published) plays them in a large player with Up next beside it. Open Page details under a video for its category, event, description and poster picture, captions, Featured (first on the page), Ad, and Published or Hidden. A hidden video is shown nowhere on the website. A browser or network cache may still play a copy it already has for up to 1 hour after you hide it; to withdraw a video at once, delete it.

                #VideoSize

                Choose a short, small clip, such as the course or wildlife; it loops behind the next event's band, muted unless Background video sound is On (Home & Events, Home layout). Every video here is also listed with the videos to watch on Home, this one included, in the order above, and plays there with sound.

                Website photos

                Photos for the website's Gallery page, in albums (one per event, or Sponsors & partners). Home shows the first nine. Choose many at once: each is made smaller in this browser (at most 2000 px on its longest side) before it is sent, and the server removes its location and camera details. Up to 600 photos. They show while a design is chosen and the home page is the Website.

                Choose an album for each, or None. Visitors open any of its photos in a viewer, and reach the whole album on the Gallery page. Put adverts and posters in their own album (for example "Focus") to rotate them.

                While it is on, the member screens (sign in, create an account, forgot and reset password) are a split page: the form on the right and, on its left, the Sign-in showcase album's photos taking turns, with the headline and the link over them, for example the challenge or a sponsor. With no album chosen the event's hero picture is used, then a Backgrounds photo, then a plain panel in the site's colours. On a phone it is a short strip under the form.

                Landing page

                The site's own name: the browser tab, the menu, the footer and its copyright, on every page of the website. Empty uses the brand name, then the service's own name. The heading below shows only on the landing page and the website's Home.

                Website menu

                Used when the home page is the Website. Each item shows only when its page has something to show: Events while an event is on sale or a past event is shown, News while News is on. Reviews, About Us, Contact Us and Gallery show once their pages exist.

                ItemShowLabel

                Footer social links

                The “Follow us” links at the foot of every page of the website, in this order. Paste each profile’s address (https://…); leave one empty to hide it. A link also set in Site details shows that one.

                News in the site design

                With a site design: the latest stories of one news section in a row on Home, with a link to all of that section’s news. It shows only while that section has a published story. None keeps Home’s news as it is.

                Website Home layout

                With a site design, in Website mode. Plain keeps Home as it is. Event-driven opens Home with your upcoming events: the event on sale and the ones announced, in date order, one at a time, each poster opening its event’s page. With no upcoming event Home stays Plain. Current event and Landing are not changed.

                How far the picture or video behind the hero is darkened, with an Event-driven Home or a chosen background. The words stay readable in every shade.

                With On, a background video shows Sound on / Mute and Pause buttons at the foot of the page. Sound never starts by itself on a first visit; once a visitor turns it on, it carries on as they move between the website's pages. Each event can use this setting, or choose Off or On, on its Event identity screen.

                Cookie notice

                A bar along the foot of the website’s pages with Accept and Decline, until each visitor chooses. Their choice stays in their browser; a visitor who declines is not counted by Site activity. Leave the words empty to use the standard ones.

                Events

                Closing an event stops its bookings and payments at once, on every method. Payments already started still finish, and a slip for a booking made before the close still comes to Payments to Verify. Each event keeps its own packages, poster and sponsors: choose the event at the top of the menu, then use the usual screens.

                Announce (coming soon) shows an added event on the website before it has packages on sale: its title, date, venue, poster, words and partners, with “Registration opens soon”. Nobody can book or pay for it. Announced events are listed in date order; the earliest is “Our next event” when nothing is on sale, and the rest are “Coming up”. When its packages are ready, Enable it as usual. An event whose date has passed is no longer shown.

                EventDateVenuePackagesStatus

                Add a new event

                It stays off the site until you enable it, so you can load its packages, poster and sponsors first. The landing page, past events and the current event are not touched.

                Archived bookings

                Archiving is how a test entry stops counting as real money. It comes off every working screen and out of every total — settled revenue included, and whatever status it ended in — without deleting anything. The ledger, the messages and the audit trail are untouched — and a full copy of everything linked to it is captured here at the moment it was archived, so it still answers questions a year from now.

                ReferenceWasAmountCapturedWhyByWhen

                Who is coming to the site

                 

                On the site now
                —
                In the last hour
                —
                People
                —
                Page views
                —
                Bots (not counted)
                —

                People per day

                Most visited

                Where they came from

                What they used

                Everything that happened

                Bookings, messages, gate scans, support and staff actions in one order, so “what happened at 13:31” is one question and not five screens.

                WhatKindWhoReferenceDetailWhen

                Add-ons this site may use. Switching one on or off, or changing its settings, needs a reason and is recorded in the activity log.

                Which build is running

                Read from the running service, not from this page — so it answers “did the deploy land?” rather than repeating what was deployed.

                Version
                —
                Commit
                —
                Built
                —
                Running since
                —
                Tickets point at
                —

                What changed

                What the organisers were told

                Every purchase alert that went out, and every one that did not. A booking with no line here is a booking nobody was told about.

                ReferenceEventChannelToResultWhy notWhen

                Where a payment actually goes

                The override, as the decisions it really makes. Two of these steps fall back to the platform account without failing — which is how "the key is set" and "payments are failing" can both be true at once.

                Everything that happened to one booking

                Built from what was written — the ledger, the entrants, the messages, the staff actions, the gate — not from a diagram of what should happen. They differ exactly when something is wrong.

                Lipila Mobile Money Rail

                Not sure where collections are actually landing? See the payment chain — it shows which branch of the override really fires, and whose wallet the money reaches.

                Direct Airtel & MTN request-to-pay collections.

                Loading gateway config…

                Leave blank to keep the key already stored for this wallet. Each wallet keeps its own key, so pasting a test key never disturbs the live one.

                Where the live key collects.

                Where the test key collects.

                Both are saved together, whichever wallet is selected. The environment is a property of the KEY and the HOST together — a live key sent to the sandbox is refused, and that refusal looks exactly like a bad key.

                …

                Sent to Lipila with every collection. There is nothing to switch on in the Lipila dashboard for this — if it is missing here, no payment can be reported back to us.

                Payout Accounts

                Other Lipila wallets a payment can be collected into: a product's own wallet, a fee account. Lipila cannot split one payment or move money between wallets, so each share is collected on its own wallet's key, as its own prompt to the payer. The wallet above is always available as site.

                Loading…

                Mobile money gifts only (a bank gift goes to the bank account the donate page shows). If the chosen wallet cannot take money, gifts are refused rather than sent to another wallet.

                IdName payers seeCollecting onLive keyTest keyWebhook secretState

                Add an account

                Leave a key or secret blank to keep the one stored. Every payment is checked back with its own wallet before it counts, so a secret is an extra check, never the only one.

                Event Gateways

                Each event takes payments on the site's gateway above (Shared) or on its own (Own), part by part: mobile money and card (Lipila), bank transfer, and the methods it offers. A payment always stays on the gateway it was started on. Keys are typed in and never shown again: only whether one is set, its first and last four, and its length.

                Loading…

                EventOn saleMobile money and cardEnvironmentKeyBank transferMethodsState

                Choose an event above to change its gateway

                Production Checklist

                Each line is checked against the live system, not against the setting that describes it.

                Not checked yet.

                Invoices by Email

                A guest paying by bank transfer can ask for an invoice by email. They confirm the address with a code first; the booking holds its place until the invoice is due. A receipt they upload is never taken as paid: you verify it as any bank slip.

                With the invoice chosen, guests are also asked for their account or order (LPO) number with you, their organisation and TPIN. A team names its organisation and marks its games; all of it is printed on the invoice.

                It starts with the country's banks. A guest whose bank is not listed chooses "Other bank" and types it.

                Letterhead and signature

                JPEG, PNG or WebP, under 1 MB each. The header runs across the top of the invoice, the footer along the bottom, and the signature sits above the signatory's name.

                Header
                Footer
                Signature