Stop Replacing Merchant Name with CRV* Prefix and Pass On the Original Information like Google Pay

Yes, I like the fact it does this.
Passing on fill info may lead to some credit card companies charging more (or cash advances)

1 Like

For me, Revolut hides the CRV* prefix and categorizes Curve transactions properly.

2 Likes

Yes, for some reason Revolut hides CRV* prefix 99% of time. Recently I saw only 1 transaction with CRV*, but that also changed later without it.

1 Like

Surely the Curve app does that?

Wrong as this is based on MCC not merchant name,

2 Likes

True. Is there in fact any good reason for the prefix?

I have to agree with keeping the CRV prefix statement - Reconciling back to my underlying card statements is much easier as I can ignore the prefix as I review curve as they happen

3 Likes

Does anyone know how this impacts on loyalty/rewards programmes?

For instance, my HSBC Rewards credit card gives me extra points when spending at specific retailers. But I’m unable to determine if I’m getting those additional points due to the transaction info being modified by Curve.

the only problem with curve is not that it adds CRV* prefix to the merchant name. it changes the merchant info completely. Unlike google pay which behaves exactly like as if the purchase was made with bank’s physical card.
see the screenshot below to see what i mean. if i make a transaction either using google pay or banks physical card, the merchant info is shown in the app (Revolut or other apps) under same Merchant name (and it is recognized, along with its logo and even its address location is correct). But if I make transaction using Curve, it modifies the Merchant info, and it is not recognized as known merchant (“Boojum”) and is shown as generic restaurant and even address location is incorrectly shown as London, GB - which is known problem: Stop reporting Curve Transactions on funding card statements as being generated in “London”

I would really hope to see, if amazing Curve team can do exactly what Google Pay or Apple Pay are doing. making it behave exactly like as if I made my purchase with bank’s original physical card.

1 Like

i’m afraid you may not get your rewards as Curve modifies the merchant info (see previous reply), and your bank may not recognize the transaction as one of those specific retailer.

2 Likes

I make use of this too. As I see all Curve transactions “in real time”, via notifications, I can skip those on my real card statements and just scrutinise the rest.

I don’t think they’d be able to avoid it anyway. It’s the same situation as PayPal, and is completely different to Google Pay (and Apple Pay) where the transaction is still between your card issuer and the merchant.

3 Likes

This has to be an issue with the originl card holder/bank, I bank with Barclays and see all my curve transactions as CRV and then the merchants name on my bank statements , When used with my credit cards the cards dont show CRV but do show the merchant the transaction was made with

This is the correct answer. Google Pay and Apply Pay basically clone your card, while Curve acts as a middle man and recharges the transaction to the selected card as if they were the merchant.

3 Likes

This is not true and based on speculation. First off, you can’t clone an EMV chip card. Only magnetic part can be cloned which is why it’s no longer used/preferred. And secondly, the Google Pay also sets up a virtual card number for each bank card and this is used when you transact at a merchant using Google Pay. The payment is still processed by Google much as Curve does. They both act as middle man and the bank’s card number is not even shared with the merchant at all for security, only virtual card number which is different for each added card. The app tells you this when you add the card to it. You can check it at the bottom when you tap a card.

2 Likes

The transaction is not between card issuer and merchant directly. The Google Pay sets up virtual card number for each bank’s card for security. This virtual number is shared with merchant not the bank’s original card. That means payment is processed much as Curve does.

If Google does it, that means it is possible. I’ll really like to see a setting that can pass on original merchant information to bank’s card. If turned off it will behave like it does now. But atleast there should be an option

1 Like

It is, though. Google, and Apple, Pay are Token Service Providers (see EMV Payment tokenisation). They are an official part of the transaction, and your card issuer still receives all the data of the real transaction. Whilst Tokenization can (but does not usually, despite commonly held beliefs) involve a new token per transaction (to prevent de facto transaction profiling), your card issuer still completes the transaction via the merchant’s acquirer.

But Curve Involves two transactions: Curve acts as the Merchant to your real card, and the card to your Merchant. They are not an official part of the end to end transaction and they aren’t allowed to send just any old data: hence why the CRV* Prefix, and why PayPal have PP*)

It’s also why in the UK your purchases don’t qualify for protection under the Consumer Credit Act when you spend over £100 using Curve. With a Tokenization system they do.

7 Likes

You can not compare Curve to Google or Apple Pay.

The Curve card is what is called a “decoupled payment card” . You can use the card for purchases and ATM transactions but the card itself, is funded by a different payment card.

According to Mastercard rules, the card issuer (i.e. Curve) is allowed to pass to the funding issuer the real MCC (Merchant Category Code) of the merchant where the card was used - this is why your bank is able to correctly categorise the transactions.

However, a decoupled issuer must ALWAYS inform the funding issuer of the decoupled card program name together with the name of the merchant. This is why all Curve transactions begin with CRV* - if not, your bank will not know that a Curve Card was used to process the transaction, and that is important in case you want to file a dispute.

The Country Code must always be the country where the decoupled issuer is based

So this has nothing to do with Curve, but are Mastercard rules Curve has to abide by.

8 Likes

Google Pay and Apple Pay are not a merchant in the transaction. Curve is a merchant in the transaction. You’re comparing apples and oranges. It would be misleading of Curve to present a merchant name to the underlying card issuer that contained only the name of another merchant that is not a party to the transaction between the underlying card issuer and Curve. Therefore the “CRV” prefix must remain.

2 Likes

As far as I can see in my personal situation, my underlying card rewards are not affected as it is based on transaction value spend. If your underlying card has reward specific merchants (quite often Amex has this approach) then it is a hgih chance it won’t be recognised.

Best way I see this is, whenever you purchase something with curve, your contract (and hence by extension any disputes) is with Curve and no longer with the retailer/service provider you bought the item from. Curve is indirectly procuring the item in question and then on-charging the amount to your nominated card selected.

That is untrue. When using Curve, despite using an underlying UK-issued credit card, you lose any rights against that underlying credit card issuer under Section 75 of the Consumer Credit Act 1974 because Curve (like PayPal) breaks the 3-way debtor-creditor-supplier relationship. But you retain all rights against the merchant as if you had not used Curve. When using Curve, your rights against the underlying credit card issuer become very limited, for example fraud and unauthorised transactions.

2 Likes