72%of SWIFT exceptions are caused by manual data-entry mistakes at the initiation form
Paying with a snap — now around the world.
The SDK that saves your users from typing in 10–20 fields and saves you thousands of transaction repair costs, every day.
$15-40is the industry cost of repairing one failed cross-border payment
$1.6Bis spent across the industry every year investigating delayed cross-border payments
HOW IT WORKS
Three steps. No typing.
Photo or PDF
Your customer snaps the supplier invoice — or drops in a PDF. Directly inside your mobile or online banking app.
Data flies into the form
Gini extracts all 10–20 SWIFT fields: beneficiary, IBAN/account, BIC, routing code (CNAPS, IFSC, ABA, Sort Code, Zengin...), amount, currency, purpose code. Validated against the SWIFT network.
Review. Confirm. Send.
Your customer sees a filled-in, ISO 20022-compliant form. One tap — the payment leaves clean. No returns, no repairs.
Instant benefits
Three levers that work immediately.
A bank running 10,000 international payments per month spends €7,500–€20,000/month on repair operations today. Cross-Border Photo Payment costs less — and shrinks the volume at source.
5–6×
ROI from transaction-repair savings alone
Repair costs disappear
72% of SWIFT exceptions are data-entry errors. Less typing = fewer errors. Payback in 30 days from repair savings alone.
€20+
More FX margin per recovered payment
Recover lost payment volume
Close the UX gap without touching pricing, and win back customers that moved to FinTech competition.
~50% less
support volume for cross-border payments
Cut support volume in half
»What is a CNAPS code?« is the most common SME call on international payments. With photo capture, the question disappears.
Users love it
The finance manager doesn’t want to type 20 fields. They want to pay the supplier.
- No research on what a CNAPS or IFSC code is
- No mistyped BIC, no rejected transfer
- No 3-8 minutes of careful data entry per invoice
- No branch visit for their »first« international payment
- No reason to switch to FinTech competitors because the bank form looks scary
- No research on what a CNAPS or IFSC code is
- No mistyped BIC, no rejected transfer
- No 3-8 minutes of careful data entry per invoice
- No branch visit for their »first« international payment
- No reason to switch to FinTech competitors because the bank form looks scary
Compliance
ISO 20022 is live. The initiation layer is not.
Since November 2025, every SWIFT cross-border credit transfer uses pain.001 messages — the exact format Cross-Border Photo Payment outputs natively. You invested in backend compliance. We close the last gap: the input layer your customer touches.
- Native pain.001 message – receive output in ISO 20022 format, without any middle layer.
- BIC validated against SWIFT – Routing checked live against the network — before the payment leaves the building.
- 14 routing formats: IBAN, ABA, Sort Code, CNAPS, IFSC, Zengin, CLABE — plus nine more.
- GDPR-compliant – Same data pipeline as our SEPA SDK in Sparkasse and DB.
- Native pain.001 message – receive output in ISO 20022 format, without any middle layer.
- BIC validated against SWIFT – Routing checked live against the network — before the payment leaves the building.
- 14 routing formats: IBAN, ABA, Sort Code, CNAPS, IFSC, Zengin, CLABE — plus nine more.
- GDPR-compliant – Same data pipeline as our SEPA SDK in Sparkasse and DB.
Corridors
Global reach. Locally validated.
Every destination has its own routing format. We extract, validate and map — all 14 of them.
EU
IBAN
EU
GB
Sort Code
UK
CH
IBAN
Switzerland
AE
IBAN
UAE
TR
IBAN
Türkiye
US
ABA
USA
CN
CNAPS
China
IN
IFSC
India
JP
Zengin
Japan
MX
CLABE
Mexico
AU
BSB
Australia
CA
Routing
Canada
SG
Transit
Singapore
HK
Branch
Hong Kong
- IBAN routing
- Non-IBAN routing (1.5x)
ROI Calculator
Run the numbers yourself.
Two inputs. One answer. Assumptions conservative and sourced (SWIFT 2022, SRM Corp 2024, McKinsey 2024).
International payments per month35,000
Error rate (industry average: 5%)5.0 %
Error reduction with CX photo payment80 %
Assumptions: €30 repair & €8 support cost per error · €20 FX margin per diverted payment · 5% of volume diverted to FinTechs, ~30% recapturable. Only the recoverable share is counted — not the gross loss.
Recoverable per month with Gini
Fewer payment repairs~80% of 1,750 errors avoided42,000 €
FX margin recovered~30% of diverted volume recovered10,500 €
Lower support burden~80% fewer support tickets11,200 €
MONTHLY SAVINGS (REALISTIC)63,700 €
Packaging
Suits every purpose.
Start where your tech-readiness allows, upgrade as the use case matures.
Tier
Good
API extraction · ISO 20022 output · 14 routing formats · field validation
Banks building their own mobile or web UX.
RECOMMENDED
Tier
Better
Everything in Good + Bank SDK (Gini-owned mobile UX)
Banks dropping in-house mobile maintenance.
Tier
Best
Everything in Better + confidence scores + purpose-code suggestions
Banks with compliance exposure (China, India) — unlocks agentic automation.
194M+photo payments in 2025
+38%YoY growth
20+banking apps integrated
Since 2014in production in Germany
Contact us
FAQ
You have questions, we have answers.
How long does integration take?
Better/Best (SDK): typically 4–8 weeks to first live deployment. Good (API): 2–4 weeks without UX work.
What if the invoice photo is poor?
In Best, every field includes a confidence score so the app can fill automatically or request confirmation.
How is pricing calculated?
Pay per use across 14 volume bands. Simple corridors use the base price; complex corridors are 1.5×. No setup or platform fee.
Is data privacy guaranteed?
The API pipeline is fully certified, GDPR-compliant and operated in a dedicated German data center.
Which corridors are available today?
14 routing formats in production: IBAN region, UK, USA, China, India, Japan, Mexico, Australia, Canada, Singapore, Hong Kong, UAE, Türkiye, Switzerland. New corridors land at no extra cost.
What happens when SWIFT changes a format?
We update mappings centrally. The app receives the change with the next SDK release without changes to integration code.