- PayIn
- PIX — 2.5%
- PayOut
- PIX — 1.3%
Offer distribution for providers
Put a current payment offer in front of demand that can use it.
PULSA converts chat-format terms into a comparable offer, checks freshness and connects the route to suitable merchant demand.
Live route showcase
Coverage ready for a real conversation
The first page is open: compare GEOs, methods and commercial ranges before registering.- 68
- routes
- 33
- GEO
- 11
- methods
- PayIn
- Fee in% - 10%
- PayOut
- On request
- PayIn
- M-Pesa — 6.5%
- PayOut
- M-Pesa — 4.2%
- PayIn
- Ставка Pay In: 1.9%
- PayOut
- Ставка Pay Out: 1.5%
- PayIn
- Ставки
- PayOut
- RUB C2C/SBP — 11%; TG UZS — 9%; TG TJS — 10%; TG ARM — 9.5%; МОБ КОМ — 17%; AZN & QUASI — 8% / 3% payout; TRY — 6.5% / 1.5% payout
- PayIn
- PSE / Nequi — 4% + 1,000 COP
- PayOut
- All Banks — 3.5% + 2,500 COP
- PayIn
- PayID — 9.5%
- PayOut
- PayID — 3.75%
- PayIn
- PayAttitude / OPay / PalmPay / Bank Transfer — 5.5%
- PayOut
- All Banks / PayAttitude / OPay / PalmPay — 2.5%
Create a profile to unlock the full list, save a shortlist and request a controlled introduction.
Availability and final terms are reconfirmed before an introduction. Counterparty contacts are not published openly.
Offer anatomy
Terms merchants can compare without flattening the commercial context.
Public coverage and private commercial terms are separated. The catalog shows the latest observed route state, while final capacity is agreed before launch.
From offer post to active pipeline
Keep the route current and spend sales time on qualified demand.
Providers control what is visible publicly and what is disclosed only inside a relevant introduction.
Structured commercial terms
Translate a post into fields merchants can compare.
- Rates and FX
- Limits and settlement
- Methods and markets
Freshness that is visible
Make it clear when terms were last confirmed and when a recheck is due.
- Confirmation date
- Capacity state
- Expiry reminder
Demand with context
Receive the case behind the request before deciding whether to proceed.
- Traffic profile
- Fit reason
- Controlled contact reveal
Provider journey
Publish once, refresh quickly, discuss only relevant cases.
The offer remains part of an operating pipeline instead of disappearing under newer chat messages.
- 01Submit the route
Add coverage, terms and the person responsible.
- 02Pass review
Confirm source, availability and the public/private boundary.
- 03Receive matched demand
See the merchant case and why the route may fit.
- 04Move to intro
Accept the conversation and keep the outcome visible.
What are you launching or trying to connect?
PULS AI will clarify the missing details and route the conversation to the right person. No procurement form required.