URL: https://token.clover.com/v1/tokenshttps://prnt.sc/1m2kf5x, In this screenshot, test card also gets tokenized on live mode.
Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.
That is expected.
How can we expect test card to pass on live mode. It should show that it's a testing card and can't be used on live mode.
Then, how can we prevent testing cards from getting tokenized.
You are confusing tokenization with authorization. A payment with a test card will not be approved in production.
I have created an app, how can I add the app to the production board. can you guide me on this. I am new to clover.
If that is how it works then anyone can use testing card and placed the order.
That isn't how it works, authorizations may cost the merchant money, you don't want tokenization to be performing an authorization. Tokenization just tokenizes the card data, that is it. When a card is saved on file (https://docs.clover.com/docs/ecommerce-saving-card) we do perform an authorization to ensure the card is valid.
2 People are following this question.
Refunding partially paid orders
Qualifying Transactions - Iframe vs API
Bearer id and merchant id
Does Clover's E-Commerce Payment Gateway support Apple Pay / Google Pay?
How to generate a multi-pay token with the Ecomm i-frame?