menu

Why Should I Choose J2pay

The main question usually raise is why should I choose this library instead of working directly on gateways API`s or SDKs. To make it simple to understand read below points.

  1. You can learn one API for all gateways.
  2. You want multi gateway support in your application.
  3. You do not have time for learning individual payment gateways docs that are also (poorly documented)
  4. You want to support multiple payment gateways in your application without worrying about the implementation of each gateways.
  5. You want to use single API for each gateway.
  6. You don’t want to take risk whether your code works perfectly on live environment.

Generic Request/Response

If you would like to work with multiple gateways the main problem developers usually face are API parameters names. Some gateways take first name as fname or first_name or take card number as CardNumber or Card_Number or card. J2Pay excludes this type of efforts and provide classes for customer details and customer cards which will remain same for all gateways. Same problem when parsing gateway response. J2Pay also excluded this type of efforts and provide generic response for all gateways. When a transaction is successfully processed some gateways return transaction id as transaction_id or transId or trans_tag. But if you are using J2pay you will always receive "transactionId". (More on this Responses section)