Accepting PayCo as a merchant

PayCo is a South Korean wallet, used domestically for online and in-store payment with stored cards and balances. For a European merchant its relevance is inbound: Korean customers who prefer to pay with the wallet they already use rather than by entering card details.

Bundles

How Korean wallet acceptance usually happens

Rarely as an individual integration. Korean and wider Asian wallets typically reach European merchants through cross-border acceptance networks that bundle several wallets behind a single connection. That is efficient, and it also means a merchant frequently accepts wallets nobody deliberately chose. Knowing which of your enabled methods arrived as a decision and which arrived as a package is worth five minutes with your PSP.

Cross-border cost and who earns the currency spread

Inbound wallet transactions are cross-border by definition, bringing currency conversion and cross-border assessments alongside the acceptance fee. Whether the customer is billed in your currency or theirs sets the rate applied and decides who earns the spread. It is configured once at integration and almost never reviewed.

Scale

Measure your own inbound volume, not the market

The size of Korean e-commerce is not the size of your Korean revenue. If inbound volume is material, negotiate properly. If it is marginal, the reconciliation and support overhead may exceed the contribution, and that is a legitimate reason to simplify. What is not legitimate is carrying the method for years without ever having looked at which case applies.

Testing

A method you cannot test is a method you cannot trust

There is a practical problem with inbound wallets that nobody puts in a proposal. You cannot test them. Buying from your own shop with a Korean wallet takes a Korean phone number, a Korean bank account and an app that will not install on your phone, which means the one method your team can never check end to end is also the one nobody would notice failing.

That matters more than it sounds, because a method producing no transactions looks exactly like a method that is broken. Both show zero. Error-rate monitoring does not help: a wallet that never gets selected produces no errors, and a wallet that redirects to a dead page produces errors in somebody else’s system rather than in yours.

Two things fix it and neither is expensive. Ask your provider for a test path or a sandbox account for each inbound method you accept, and record who holds the credentials, because in a lot of businesses the answer turns out to be the agency that did the integration and no longer works with you. Then set an alert on absence rather than on failure: any method that produced transactions in each of the last eight weeks and none in the last seven days should send somebody an email.

Which payment provider supports PayCo in Europe?

Toss Payments and KG Inicis in Korea, alongside KOMOJU and Rapyd, all document PAYCO, among others, as do the other gateways carrying Korean wallet coverage. The useful questions are the effective rate on wallet volume, whether currency conversion is shown separately, whether the wallet arrived bundled, and what share of revenue actually flows through it.

Silence

What silence costs

Put a number on the failure nobody sees. Take 5 million euros of annual revenue with an inbound wallet carrying 0.8 per cent of it, so 40,000 euros a year, which is precisely the size at which nobody watches it.

Now suppose it breaks in January and somebody notices in May. Four months of a 40,000 euro run rate is roughly 13,300 euros of orders attempted and not completed. Some of those customers pay by card instead and you lose only the difference in conversion. Some abandon, and for an inbound customer with no convenient alternative that is the whole order. Even at a conservative half, 6,600 euros walked out over a fault that a seven-day absence alert would have caught in the first week.

Which is an argument for the monitoring rather than for the method. The rule costs one afternoon, it applies to every method you accept rather than only this one, and it converts the hardest kind of failure, the silent kind, into an email.

Reviewing what this costs you

What you pay is set in your agreement, not by the scheme. Start by establishing whether you are overpaying your PSP, or look at what payment performance optimisation does to authorisation rate and cardmix, which is where a wallet earns or costs you money.

How a wallet behaves inside your flow, from one-click through to the return after a challenge, is a checkout flow optimisation question as much as a pricing one.

Relevant markets: South Korea, global inbound