%PDF-1.7 1 0 obj << /Type /Catalog /Outlines 2 0 R /Pages 3 0 R >> endobj 2 0 obj << /Type /Outlines /Count 0 >> endobj 3 0 obj << /Type /Pages /Kids [6 0 R ] /Count 1 /Resources << /ProcSet 4 0 R /Font << /F1 8 0 R /F2 9 0 R /F3 10 0 R /F4 11 0 R >> /ExtGState << /GS1 14 0 R /GS2 15 0 R /GS3 16 0 R /GS4 17 0 R >> >> /MediaBox [0.000 0.000 595.280 841.890] >> endobj 4 0 obj [/PDF /Text ] endobj 5 0 obj << /Producer (dompdf 1.0.2 + CPDF) /CreationDate (D:20240507202939+00'00') /ModDate (D:20240507202939+00'00') >> endobj 6 0 obj << /Type /Page /MediaBox [0.000 0.000 595.280 841.890] /Parent 3 0 R /Annots [ 12 0 R ] /Contents 7 0 R >> endobj 7 0 obj << /Filter /FlateDecode /Length 5747 >> stream x[koH_b`BEQ{4Ĥ"lQ"{G/{E%:vo,6@,&qsνU|)b^+reW۟D'`(wj}7~\kj =QNdEX-uH U֫m6A‡g.>" ߞ&!=[$6IW q驝2 I|Vr(xq|V Z>W<~a>&d(EPn/t-Ņg%s7o> & y(q򞏇`UwGwzXqr۵UgvUXh)Wك5-:/8^U<YZA^k*џÀz1һXmԾ?)5Ҳ,6?]]Rj_'Nj[UoЕֻb>M8Y~iS3,2_,߈F+rfeigǴgq3u b:*|Qꓷ#B[6W:?eǟ}id<,Q/B>73&E:pwos&dM7&N2X Iݏuxv Z2;`s ҇m?mw}ܹ6|vn>M[ }h#m\O>D;i~;L#>yh#M=}m#y&s8H|B#L?3ųCFǕzhG4gJ>KG ߟgV4 /13l4б9m)D:Cz8_g46|}N#Oh//SG>0楿boaoI6)brÇ߮d".dEy|A|e1þɝj/ԿLCSQ C6zH]N@Һ]ôΰ| mkj@հOʿ)XK'k]܊~%ڢeD~W56$>@=w~ir]-) vYB?s:5C7mf>_+ ލP,^ɐ |hZF [}Հ"6v('{ϵNlVC`tƶ3)>5&(_ְsl<+n t [#< %aqY0ajSdM|0s_5}O>ضt#;ຈ0t1xگZ K7 B 3H綁ڵu=BK'x$ T~&go8y³)y @ased2꫆o`oN 30sH5@7%xZI!pj0=dA4&IK|hSj0ږ!'1tܴ@~N_ze):0dmZ08qػs}4ලNqU2'{U#LjTTѨ:z .;Z$o~uWE|MI-~DyIj/`Pӈ`s~ ٪Ҧ|k";M:_9;@c ]$35׼߫~E!L+4>hRfDNZc\`S<U z oE]8t+ -G Csw+}+F݂q 4=W |~(WißN0\=E-|xg>|_2Smb}{IcQ e ͱ)W2%dQi{uO2X1p>.+eS?w7o*uf2c~8L|b)qdU`bv6yӤ2GwD5rm 4rzl%+bLyYgߘ8>ZyC6 %0k5~c?8أ& L|:JuX &1V ]оw\atK)\c+aq*4BmCGͮ~_y%%D(A:ܷ[kk?ո!'7$ޮ6D9菴 1^ /iK_ȳj9?szSLJM3qΫ)4?O ϯ/p1\I X O$~#91ꍩ%|,ɚ]s}b/4t`7mi 0Ǥ BUCܷ\b۫Ј~#\ rřܖGQ-!pSέI̜ӹO !C־{R|}s,s9qE?/Ґx#c|#cQ+}ޖkHcv횏66OB1~(^) 1fR>) 3xtGr_݄m86 RMDy9kx`Lȵ68:cŕ1 sG!: jӥ/&y:C55{rNCxDkf(εkVp}΀^XcӥS}j.4Q])=E?t5U|ZdCԇ|$>ι\̳M4ZhT΃<\L/5c䢎 \# @'ýCq =TznHLEzf^k4s]V',Θ^!MBnAF]e)Yą\OQ^'pqG]#WklŸxVL}sF 䚅(Z+>Vӫs;Z+>!gs;ڟnYOYHh${>w}^g`UGsm֞31́cK<^칐?9} FM G>5-v\7fmb_2|B0u?]Fhd^_tKŗrcr-'jrf7sZ5l,su,jʎ,{3g'YN#Tg "w51nV9Xs8U26g@Խ2 s>",NcCi\W56XwwHs79js|LTԆF룬Y ': lF:;boY9?Þ9{`ƾ =#jaڱ3;<Xm#w~GU gB}wCL/iJl l;ֵTj;&ǴLy!xm fGm'ؑz|[mGƛy2w{^9Gz h~U_8e7ZN7o(<>j΅b\U֗΅L]:PO]SӚ}ŷ^x{ =+F:{Ec`U>*Y趱 oqo,Oi=j}c-閡֗pteŋИ@Z_c%ÔIt)OyBv\K8 r#I$]yb҄oriH-1X9ev3zv[_;;ς\?UմxCϞ'I#Zz멦f*]C5ztMY'w:_]?@$X* ekU|u.S@Rܽ{ocmdu2Q> 鶾w6#X/ yͷI.?nۜ h}+EމԨ4l̔-Ԑ"_^e/K"}SE GT /-sĀejJ_`"Z5Oq)7ײ]:=xRQeɏqN6忔_UE,X`d0"Ce׼gAf^xZWݕs+K3#Ae7y]6>{ťZgz)E4ݒ qu;WD^D~^CSC`Eg¯%#]6@@9t 7{c*#^uZs?ob endstream endobj 8 0 obj << /Type /Font /Subtype /Type1 /Name /F1 /BaseFont /Times-Roman /Encoding /WinAnsiEncoding >> endobj 9 0 obj << /Type /Font /Subtype /Type1 /Name /F2 /BaseFont /Times-Bold /Encoding /WinAnsiEncoding >> endobj 10 0 obj << /Type /Font /Subtype /Type1 /Name /F3 /BaseFont /Helvetica /Encoding /WinAnsiEncoding >> endobj 11 0 obj << /Type /Font /Subtype /Type1 /Name /F4 /BaseFont /Helvetica-Bold /Encoding /WinAnsiEncoding >> endobj 12 0 obj << /Type /Annot /Subtype /Link /A 13 0 R /Border [0 0 0] /H /I /Rect [ 297.1040 177.5046 360.4760 189.7146 ] >> endobj 13 0 obj << /Type /Action /S /URI /URI (https://payyo.ch/speak-to-us/) >> endobj 14 0 obj << /Type /ExtGState /BM /Normal /CA 0.3 >> endobj 15 0 obj << /Type /ExtGState /BM /Normal /ca 0.3 >> endobj 16 0 obj << /Type /ExtGState /BM /Normal /CA 1 >> endobj 17 0 obj << /Type /ExtGState /BM /Normal /ca 1 >> endobj xref 0 18 0000000000 65535 f 0000000009 00000 n 0000000074 00000 n 0000000120 00000 n 0000000372 00000 n 0000000401 00000 n 0000000550 00000 n 0000000672 00000 n 0000006492 00000 n 0000006601 00000 n 0000006709 00000 n 0000006817 00000 n 0000006930 00000 n 0000007058 00000 n 0000007139 00000 n 0000007198 00000 n 0000007257 00000 n 0000007314 00000 n trailer << /Size 18 /Root 1 0 R /Info 5 0 R /ID[<8eea4d52f6d24ef734354c1b576deb2c><8eea4d52f6d24ef734354c1b576deb2c>] >> startxref 7371 %%EOF The Nezasa Story - Payyo

The Nezasa Story

“The most relevant aspect is that our team can relax regarding how payments are being fulfilled across the multiple steps, providers and changes that come with multi-day and multi-stop tours.”

The Nezasa Story

Statement from Patrick Hammer about Payyo:

“The main challenge before Payyo was always making sure payments were successful to every entity and that fees were charged transparently and in an automated manner.”

What is Nezasa?

Nezasa is a B2B software company that empowers the travel industry and its leading players to provide multi-day tour personalisation at scale.

Our award-winning platform, TripBuilder, allows travel brands to create and sell personalised trips with unprecedented automation. Our solution enables tour operators, agents and end consumers to plan highly customised itineraries seamlessly.

Our questions to the CPO of Nezasa.

We met Patrick Hammer and he answered a few questions about the background of Nezasa and their decision to integrate with Payyo.

Hello Patrick, nice to meet you today. Thank you for your time. Can you tell us a little bit of the background of Nezasa and how you describe the business model?

Hello, nice to meet you! Thanks for the opportunity to share a bit of our story with you.

Nezasa’s primary focus has always been to make travel planning and booking easy. Having that in mind, we developed a platform called TripBuilder.

TripBuilder empowers travel brands to sell end-to-end itineraries to travellers in a digital, interactive and hyper-personalised way. Our software allows a completely personalised experience for travellers and travel brands, combining multiple sources and suppliers.

TripBuilder is the core of our business, and we’ve made it our mission to continuously develop it according to our industry and customers' needs.

You are one of the partners of Payyo! How does the cooperation work?

Nezasa's TripBuilder Internet Booking Engine with marketplace supply provides an all-in-one solution to sell personalised itineraries. It allows travel brands to sell their product directly on their websites. These processes involve multiple sources and providers. We needed a partner to solve the challenges of such complex and automated operations for online payments to be successful.

Payyo stepped in and is now helping us automate those processes and ensure payments are distributed without disruption.

What challenges did you face before working with Payyo?

The main challenge before Payyo was always making sure payments were successful to every entity and that fees were charged transparently and in an automated manner. Because Nezasa is focused on personalised itineraries, our product provides customers with various supplier integrations. That means various payments to those providers. TripBuilder’s itineraries can take many shapes and one of its major strengths is its automated capability to combine different use cases of the industry. Tours can be filled with live supplied options, they can be a combination of online and offline products or can even be fixed multi-day tours. And, thanks to Payyo, we achieved a way to fulfill these requirements and keep payments simple.

What is your experience with Payyo since you started?

It’s been excellent! The most relevant aspect is that our team can relax regarding how payments are being fulfilled across the multiple steps, providers and changes that come with multi-day and multi-stop tours.

How would you and your team rate the integration process with Payyo?

Every challenge we faced along the way was fixed effectively. The integration was straightforward and the Payyo team was very helpful and approachable when we had questions.

How is Payyo involved/integrated into your daily business with your activity partners?

We mainly use Payyo for our Marketplace operations. The integration allows our customers to book multiple travel products and pay for them online directly to our marketplace partners. Additionally, the Payyo payment gateway integration allows our customers' clients to book and pay for travel packages directly on our customers' websites. Then, Payyo splits payments between the marketplace operator and our customers.

All of these payments are done in a seamless and stress-free process.

Which advantages have you seen so far with Payyo?

Multiple payments, one partner. That’s the main advantage we’ve witnessed so far. Payyo understands the landscape of the tours and activities market. Of course, there are also cost-effective aspects. There’s no need for multiple payment gateways or unnecessary manual tasks. It is a solution for the long run and does not force us to constantly make workflow changes.

To whom would you most recommend the integration with Payyo?

I would recommend it to any platform, SaaS or marketplace in our industry. Having a partnership that simply reduces all the stress of online payments makes all the difference in the world, especially when you’re working with a large number of suppliers or travel service providers.

Patrick, thank you for your time! We are pleased about the steadily growing cooperation with Nezasa. Thank you for growing with us!

Is Payyo a fit for your business?

Get in touch now to talk to our team.

Close Bitnami banner
Bitnami