Transaction descriptors

What’s this?

Trans­ac­tion descrip­tors are the descrip­tions for charges a client finds on his card or bank state­ments. Apart from the num­bers that iden­tify cer­tain trans­ac­tions, cus­tomers will also usu­ally find the pay­ment provider’s name. But such infor­ma­tion doesn’t say any­thing about the prod­uct or ser­vice and — what’s more impor­tant, it isn’t use­ful to the customer.

That’s why PayLane offers you the abil­ity to define your own trans­ac­tion descrip­tions. There are two basic types:

Fur­ther­more, each trans­ac­tion may have a unique descrip­tion, mak­ing iden­ti­fi­ca­tion even easier.

What does it mean?

Trans­ac­tion descrip­tors are much more than just good look­ing card state­ments. This ser­vice pro­vides many mea­sur­able ben­e­fits for mer­chants. The most impor­tant one is that cus­tomers don’t have any doubts about their trans­ac­tions, which means they won’t request charge­backs just because they can’t iden­tify a spe­cific payment.

Of course a mer­chant can “defend” him­self when a charge­back request is unfounded. How­ever, he must do it every time and prove his inno­cence within cer­tain time lim­its. Using trans­ac­tion descrip­tors makes life eas­ier and, at the same time, cre­ates a pos­i­tive image as a customer-friendly merchant.

Exam­ple

If a mer­chant owns an e-store, he may choose a sta­tic descrip­tor. A name that clearly iden­ti­fies his brand should be ade­quate – just so his cus­tomers won’t have any prob­lems asso­ci­at­ing pur­chases with his shop.

A soft­ware pro­ducer may need a dif­fer­ent solu­tion. If he mainly pro­motes his appli­ca­tion prod­uct brands, not him­self or his com­pany as provider, he’d prob­a­bly pre­fer dynamic descrip­tors. He won’t be iden­ti­fied by his com­pany name, but most likely he’ll use the prod­uct names as descrip­tors. This won’t leave any doubts — cus­tomers surely remem­ber buy­ing a cer­tain appli­ca­tion, but may not recall the provider’s name.