Collecting payments

Asking a customer to pay

Where

Payments → Payment Requests

Plan

Growth and above

Permission

Payments → Payment Request

1. Go to Payments → Payment Requests and click New.
2. Enter the Amount. This is required.
3. Leave Currency as it is, or change it.
4. Type the Gateway — paystack, hubtel or payswitch — or leave it blank to use your default provider.
5. Choose the Channel — Mobile money, Card, Bank transfer, USSD or QR code.
6. Choose the Source — POS, Customer portal, Invoice link or Ad hoc.
7. Enter the Customer email and Customer phone if you have them. For mobile money the customer’s network (MTN, Telecel or AirtelTigo) is worked out from the phone number unless one is given.
8. Leave Generate payment link on No to charge straight away, or set it to Yes to create a link the customer can open.
9. Add a Description and click Save.

Gateway is a free-text box with no list

There is no dropdown. A blank box, or a name SaleSprint does not recognise, uses your default provider — see priority. Only a provider you have actually configured is ever charged.

The Provider box on the payout-account form is still free text with no checking.

SaleSprint does not tell the customer anything

No SMS and no email is sent for a payment request. Whatever you choose, you have to reach the customer.

A link generated here is never displayed

Set Generate payment link to Yes and the request saves with a success message — and the link appears nowhere on this screen. No column, no dialog, no copy button shows it, so you cannot pass it to the customer.

Leave it on No when working from this screen.

Pay links do work — just not from here

The same mechanism puts a Pay now button on the invoice a customer opens from one of your emails. SaleSprint creates the link itself when they open the document, reuses it if they reload, and opens a fresh one if the amount owed changes in the meantime.

Every time the customer presses pay on the link, a new attempt is opened with the provider, so switching from card to mobile money, or trying again after a failed prompt, never clashes with the earlier try. If an earlier attempt was in fact paid, SaleSprint notices before asking for the money again. When the customer comes back to the page after paying, the page checks with the provider and turns to paid on its own.

Invoice links and their pay buttons now open on SaleSprint Pay, so no shop address is needed. The button appears whenever a payment provider is available to your workspace and something is owed. See getting paid online.

The customer’s next step is not shown either

With Generate payment link = No, SaleSprint contacts the provider immediately, and the provider sends back either a checkout page to open or an instruction such as approve the prompt on your phone. This screen discards both. The dialog closes and says only that the request was created.

Taking payment at the till does show the customer what to do. This screen does not.

Checking a payment with the provider

Record transaction no longer records what you type. It asks the provider about the request’s own payment and records the provider’s answer:

1. On the request’s row, click Record transaction.
2. Save. Any status, amount or fee you enter is ignored — the provider’s figures are used.

• If the provider says the payment completed for the exact amount and currency, the request is marked Completed and the money is credited — once, however many times you or SaleSprint check.
• If the amounts or currencies differ, the request goes to Under review and nothing is credited.
• If the provider still says pending, nothing changes.

You cannot mark a payment paid by hand

A request that never reached a provider cannot be completed from this screen — you get “a completed payment can only be recorded from a gateway verification”. A provider transaction ID that is not this request’s own is refused too. Money received outside the provider (cash, a bank transfer) belongs in Finance, not here.

View transactions on any row lists everything recorded against that request, including the currency the provider reported and, for a payment that did not complete the request, the reason (for example amount_mismatch).

The list

Columns are Reference, Amount, Gateway, Channel, Created and Status. Statuses are Pending, Initiated, Completed, Failed, Refunded, Partially refunded, Cancelled and Under review.

Under review means the provider reported a payment that does not match the request (a different amount or currency). It was not credited. Your SaleSprint operator decides it: accepted at the amount actually paid — it then completes and reaches your balance like any other payment — or marked to be refunded.

A completed request also shows the Gateway fee, the Platform fee and the Net amount that reached your balance. They are worked out when the payment is confirmed — see settlements and fees.

A request cannot be edited once created — only checked, or cancelled. Once a request is decided (completed, failed, cancelled or under review) it never changes again: a late or repeated notification cannot overwrite it.

Cancelling checks with the provider first

If the customer has already started paying, Cancel request asks the provider first. A payment that went through is recorded and the cancel is refused; only an unpaid request is cancelled. Requests that are simply left open are cancelled automatically once they expire, after the same check.

Cancel needs the delete permission

Cancel request is controlled by the delete permission rather than an edit one, so someone who can record transactions may not be able to cancel a request.

The Merchant Ledger

Where

Payments → Merchant Ledger

Plan

Growth and above

Permission

Payments → Ledger

This is your account with your SaleSprint operator: the money collected on your behalf, what was deducted from it, and what has been paid out. It is read-only — there is nothing to add, edit or correct.

Your balance is given per currency, as Pending, Available and Settled.

Each row is one movement, with its date, amount, a status — Pending, Available, Settled or Reversed — and what it is:

Row	Direction	Meaning
Collection	credit	The full amount a customer paid. One per payment request, and only once the provider has confirmed the payment for the right amount and currency.
Gateway fee	debit	The provider’s charge on that payment.
Platform fee	debit	Your operator’s fee on that payment.
Billing offset	debit	A SaleSprint subscription invoice paid out of a settlement.
Payout fee	debit	A charge for sending a payout, if your operator has one.

Money becomes available on its own. A collection lands as Pending and turns Available once the holding period has passed, with nobody doing anything. Only then is it included in a settlement.

Only payments taken through your operator’s account appear here

If you use your own provider keys, the provider pays you directly and there is nothing for your operator to hold — those payments do not appear in this ledger.

See settlements and fees for what happens next.

Payment Logs

Where

Payments → Payment Logs

Plan

Growth and above

Permission

Payments → Log

A read-only history with Date, Caption, Amount, Transaction # and Status, filtered by date.

Only collections are logged

A collection row for each payment received.

Failures, cancellations, settlements, payouts and provider errors are not logged here. An empty stretch does not mean nothing went wrong. Settlements and payouts have their own screens.

The Status column shows the raw internal word rather than a translated label.

Related

• Settlements and fees
• Payments overview
• Point of sale
• Getting paid online — pay links on invoices, and what the customer sees
• Troubleshooting invoices and online payments