A collection
Money inYour server asks for a collection of GHS 250.00. The payer is prompted for exactly that — nothing is added to their side.
Your integration keeps recording GHS 250.00 against the customer who paid it.
Pricing
Pycue rates are agreed per organization and quoted as a percentage on collections and on withdrawals. Each rate is independent, and either can be zero. Whatever Pycue withholds is a matter between Pycue and your organization — it is never added to what your customer pays.
Worked examples
Assume your organization is charged 5% on collections and 5% on withdrawals. The payer is always prompted for the full amount.
Your server asks for a collection of GHS 250.00. The payer is prompted for exactly that — nothing is added to their side.
Your integration keeps recording GHS 250.00 against the customer who paid it.
Your organization requests GHS 250.00. The full amount leaves your balance immediately, whether that is a direct API payout or a cashout you request from the workspace.
You see the net before anything is committed, and the payout figure is recorded against the transaction.
How the rate is set
A rate of 0% means that flow is free. Rates are capped at 50% to protect an organization from a configuration error in a single transaction.
Precision
All amounts are integers in pesewas — the smallest unit of the Ghanaian cedi — so nothing depends on floating-point arithmetic.
The charge rounds up
A charge is always rounded up to the next whole pesewa, so Pycue never silently keeps a fraction. The organization absorbs the rounding remainder.
The rate is snapshotted
A transaction records the rate in force when it was created. Changing your rate later never rewrites a payment that is already in flight.
Replays are stable
Re-sending a request with the same idempotency key returns the original quote, not a fresh one calculated at today's rate.
Reversals are exact
If a payout fails or you ask us to refund a cashout, the withheld charge is returned in full alongside the amount.
Messaging
You buy blocks of credit up front. Each message debits one unit per recipient, and requests stop rather than overdraw.
Prepaid blocks
Purchased per organization and visible in the workspace.
One unit per recipient
A single request to 50 numbers costs 50 units.
Fails closed
An over-budget send is refused outright rather than partially delivered.
Package pricing is confirmed with your Pycue contact, since it follows provider cost.
Rates are agreed per organization rather than published, because they depend on volume and on what you build. Open an account and request access — we will confirm your rate before you move any money.