The PXP Financial Payment Provider Developer Hub
You will discover comprehensive guides and documents that will help you take effect with PXP Financial Payment provider as soon as possible, along with help in the event that you have stuck. Why don’t we jump right in!
Overview
Take note the following terms before you begin reading the documents:
- Merchant: the business offering items or solutions and PXP that is using Financial processing the matching economic deals.
- Shop: the web site owned by a vendor where items or solutions could be offered to clients. a vendor may have a few various shops/websites.
- Consumer: The subscribed client at a vendor’s internet site that is purchasing items or solutions through the vendor. The terms client and “user” are used interchangeably in this paperwork. Observe that clients are linked up to a vendor, perhaps not store.
- Re Payment: A transfer of funds either from client to vendor, or from vendor to client. The definition of re re payment and “transaction” are utilized interchangeably in this paperwork.
- Deposit: Subtype of re re Payment representing a transfer of funds from consumer to vendor. Also called Purchase, Buy.
- Withdrawal: Subtype of re re re Payment representing a transfer of funds from vendor to customer. Also referred to as Payout, http://speedyloan.net/payday-loans-oh/ravenna-4/ Cashout. Its relevant to merchants in Gaming and Binary Alternatives industries as an example for which customers can get winnings as an example.
- Deposit Reversal: Subtype of re re re Payment representing a transfer of funds from vendor to consumer for reverting a formerly done deposit.
- Chargeback: Subtype of re re re Payment representing a transfer of funds from vendor to client following the consumer has expected their bank to return a card deposit.
- Card Refund: Subtype of re re re Payment representing a transfer of funds from vendor to consumer as being a settlement for a formerly prepared card deposit.
- Re Re Payment Method: Attribute of each and every Re Re Payment. Represents the mixture of deal type (Deposit, Withdrawal, Chargeback, Refund, etc.) and also the re payment option selected by the consumer, e.g. Bank card (Visa), Paypal, Paysafecard, etc.
- Payment Provider: thage party that is 3rde.g. a business like Paypal, a bank, another PSP, third party Acquirer) which holds the client funds and can accept the deal, with matching credit/debit following approval. a repayment technique may be supported by/implemented via 2 or even more re payment providers ( ag e.g. Visa Deposit via PXP Financial Acquiring, via AIBMS, Wirecard or any other party that is 3rd).
- Payment Account: the client identification information in the provider for a payment that is specific, e.g. card details, bank details, etc.
re Payments may be developed in PXP Financial Payment provider by making use of one of several integration that is following:
- Redirect Integration: the consumer is rerouted to PXP Financial Hosted Payment Pages for going into the re payment information. Almost all of our merchants that are direct this integration choice.
- Backend2Backend Integration: the client comes into the re re payment information regarding the vendor’s web site which causes a server-to-server call to PXP Financial Payment provider API to start the re payment. The Backend2Backend Integration choice provides merchant the likelihood to generate the Payment UI on it’s own also to invoke the backend API for initiating payments. Lovers and merchants with built-in Hosted Payment Pages utilize this integration choice.
Both in full situations, following the re re payment happens to be triggered a notification will likely be delivered from PXP Financial Payment Service to a vendor endpoint showing what’s the processing status associated with the re payment. Instead, the vendor application can invoke lots of API options for retrieving re re payment details, doing actions that are additional a repayments, etc.
PXP Financial has APIs that is several available merchants:
- Payment Service v3: an XML POST API may be the standard API wanted to merchants for Redirect and Backend2Backend Integration.
- Payment Service v4: a REST/JSON API containing only functionality pertaining to Direct Post Integration.
- Payment Service v5: a REST/JSON API containing only functionality associated with individual enrollment.
- Payment Service v6: a REST/JSON API supporting functionality that is additional vendor onboarding.
Variations are complementary
Please be aware that more recent variations usually do not completely change older variations, in particular v4 and v5 contain just specific functionality and try not to fully replace v3.
