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.

Logo
The Problem

Cross-Border transaction forms ask 20 fields – ready to overwhelm everyone.

An SME finance manager opens the banking app to pay a supplier in Shenzhen. They see an empty form: IBAN, BIC, CNAPS code, beneficiary address, purpose code — and start a painful user journey to fill up to 20 fields with a high likelihood to fail on the first try.
And those who give up and close the banking app, search the web for »how to send international payment«. And FinTechs, not banks, are the go-to-solution.

72%

of SWIFT exceptions are caused by manual data-entry mistakes at the initiation form

$15-40

is the industry cost of repairing one failed cross-border payment

$1.6B

is spent across the industry every year investigating delayed cross-border payments

How It Works

Three steps.
No typing.

1

Photo or PDF

Your customer snaps the supplier invoice — or drops in a PDF. Directly inside your mobile or online banking app.

2

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.

3

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 hit month one.

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 on repair savings alone

Repair cost disappears

72% of SWIFT exceptions are data-entry errors. Less typing = fewer errors. Payback in 30 days from repair savings alone.

$20+

FX margin per recaptured payment

Bring back the lost volume

Close the UX gap without touching pricing, and win back customers that moved to FinTech competition.

~50% less

estimated cross-border ticket volume

Halve support calls

»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
Compliance

ISO 20022 is live.
The initiation layer isn’t.

Since November 2025, every SWIFT cross-border credit transfer uses pacs.008 — 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.

  • Direct fields match to ISO 20022. No translation 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.5×)
ROI Calculator

Run the numbers yourself.

Two inputs. One answer.
Assumptions conservative and sourced (SWIFT 2022, SRM Corp 2024, McKinsey 2024).

International payments per month 35,000
Error rate (industry avg: 5%) 5.0 %
Error reduction with photo payment 80 %

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 avoided €42,000
FX margin recaptured ~30% of diverted volume recaptured €10,500
Lower support load ~80% fewer support tickets €11,200
SAVED PER MONTH (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.

Track record

Already 194,000,000 photo payments a year.

Cross-Border runs on the same SDK trusted every day by Sparkasse, Deutsche Bank, Commerzbank, DKB, Consorsbank and VR-Banks. You’re not onboarding a new vendor — you’re extending a relationship your security and compliance teams already approved.

Icon fees

194M+

photo payments in 2025

Icon graph

+38%

YoY growth

20+

banking apps integrated

Since 2014

in production in Germany

Contact us

Does your company operate a mobile app?

Please provide all necessary information to proceed to the next step.

How many monthly active users does your mobile app have?

Please provide all necessary information to proceed to the next step.

What is your biggest challenge in your current banking operations?

(multiple choice possible)

Please provide all necessary information to proceed to the next step.

And what goal do you want to achieve with your mobile banking app?

(multiple choice possible)

Please provide all necessary information to proceed to the next step.

Almost there – what name would you like to go by?

Please provide all necessary information to proceed to the next step.

Only one more step – how can we reach you?

Would you like to be called personally? *

Please provide all necessary information to proceed to the next step.

Click send and receive a free 30-minute consultation with our experts for tailored advice on achieving your goals.

Thank you for your inquiry - we will get back to you as soon as possible!
There was an error trying to send your message. Please try again later.
FAQ

You have questions, we have the answers

Better/Best (SDK): typically 4–8 weeks to first live deployment in an app that already integrates the SEPA photo payment. Good (API): 2–4 weeks, no UX work.

On the »Best« tier we return a per-field confidence score. Your app decides whether to auto-submit or prompt the user to confirm.

Per payment, in 14 volume bands (B1–B14). Simple corridor base, complex corridor 1.5×. Annual minimum commitment. No setup fee, no platform fee.

We operate a fully certified, GDPR-compliant API pipeline in our own data center in Germany; the same architecture that most German banks already use in production.

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.

We update the mapping centrally. Your app picks it up with the next SDK release — you don’t touch code.