Skip to content

Pricing

Understand the commercial fit
before you integrate.

APISMA discusses pricing privately after reviewing your company, product categories and expected volume. Start with the assumptions that determine whether the partnership works for your business.

Your starting point

A useful brief separates
volume from assumptions.

Use a realistic starting range. You do not need a completed integration or a promise of future sales to begin the conversation.

InputWhat to prepareWhy it matters
Product categoryThe category you want to start with; distinguish voucher delivery from a direct top-up or connectivity plan.Different fulfilment paths create different customer-support and reconciliation questions.
Expected monthly volumeA starting range and, if relevant, campaign peaks. Label forecasts as estimates.A steady monthly total can hide short bursts and different operational needs.
Customer journeyWho pays, who receives the product and which team supports the recipient.The commercial model needs to account for the responsibilities your business retains.
Markets and currenciesThe recipient markets and currencies you want to discuss, not assumed coverage.Ask which combinations can be agreed; do not build margins around an unconfirmed catalog.

Terms to clarify

Compare the whole commercial model.

A unit price alone does not tell you the cost of offering a digital product. Use these questions when reviewing a proposal.

Price basis

Ask whether the agreed price is tied to a denomination, product, currency or another defined unit. Confirm what is included, what can change and when a price becomes binding.

Fees and commitments

Ask about setup or recurring fees, minimum commitments and any volume conditions. Do not assume a discount, free setup or a minimum-free arrangement.

Funding and settlement

Clarify the applicable payment and settlement arrangement, reconciliation records, currency conversion and responsibility for taxes or other charges.

Exceptions and disputes

Ask what happens commercially when an outcome is pending, rejected or disputed. Confirm the evidence needed, the responsible team and which written terms control the resolution.

An internal decision

Build a margin model with explicit unknowns.

Your own checkout price and support costs are business inputs. Supplier terms remain unknown until confirmed.

  • Revenue assumption

    Record the amount your business expects to collect and the currency. Keep promotional subsidies separate.

  • Cost assumptions

    Separate product cost, agreed charges, currency effects and your customer-support cost. Do not treat unconfirmed fields as zero.

  • Risk assumption

    Identify the effect of pending outcomes, refunds to your customer and support workload on the business case.

Illustrative planning example

A rewards campaign is not steady retail demand.

A campaign can concentrate requests into a short period even when the monthly estimate looks modest. Share the timing and expected peak with the reviewer; an average alone can misrepresent the operating need.

This is a planning scenario, not an APISMA price or capacity commitment.

Common questions

Before requesting commercial terms.

Can I obtain a price without applying?

This site does not publish a rate card or issue an instant quote. Use the access request to introduce your business, categories and volume range for manual review.

Do higher volumes automatically mean lower prices?

No volume discount or price tier is promised here. Ask which commercial conditions apply to your proposed activity and obtain the agreed terms in writing.

What if I am still estimating demand?

Choose the evaluation option or an honest expected range on the form. Explain forecast assumptions during the follow-up conversation rather than presenting a target as committed demand.

Does applying commit my company to a purchase?

Submitting the public form does not form a contract or guarantee approval. Any approved relationship requires separate written terms.

Start with your category and expected volume.

The access request collects the essentials. Detailed commercial assumptions can follow during manual qualification.

Submitting a request does not create an account or guarantee approval.

Request API Access