PXP Financial Payment Provider. Thank you for visiting the PXP Financial Payment provider designer hub.
The PXP Financial Payment Provider Developer Hub
You will find comprehensive guides and documentation to assist you begin working with PXP Financial Payment provider as soon as possible, along with support in the event that you have stuck. Let us jump right in!
Overview
Take note the terms that are following you begin reading the documents:
- Merchant: the business attempting to sell items or solutions and PXP that is using Financial processing the matching economic deals.
- Shop: the internet site owned by a vendor where items or services can be found to customers. a vendor may have a few various shops/websites.
- Client: The subscribed client at a vendor’s website who’s buying items or solutions through the vendor. The terms client and “user” are used interchangeably in this documents. Observe that clients are connected to a merchant, maybe not store.
- Re re Payment: A transfer of funds either from consumer to vendor, or from vendor to consumer. The word payment and “transaction” are employed interchangeably in this documents.
- Deposit: Subtype of re re Payment representing a transfer of funds from client to vendor. Also called Purchase, Buy.
- Withdrawal: Subtype of Payment representing a transfer of funds from vendor to client. Also referred to as Payout, Cashout. Its relevant to merchants in Gaming and Binary Options industries for instance in which clients can get winnings as an example.
- Deposit Reversal: Subtype of re re Payment representing a transfer of funds from vendor to consumer for reverting a formerly done deposit.
- Chargeback: Subtype of re re Payment representing a transfer of funds from vendor to consumer following the client has asked their bank to return a card deposit.
- Card Refund: Subtype of re Payment representing a transfer of funds from vendor to consumer as being a payment for the formerly prepared card deposit.
- Payment Method: Attribute of each and every Re Payment. Represents the mixture of deal kind (Deposit, Withdrawal, Chargeback, Refund, etc.) plus the re re payment choice selected because of the client, e.g. Bank card (Visa), Paypal, Paysafecard, etc.
- Payment Provider: the next celebration (e.g. an organization like Paypal, a bank, another PSP, third party Acquirer) which holds the client funds and certainly will accept the deal, with matching credit/debit after the approval. a payment technique may be supported by/implemented via 2 or maybe more re re re payment providers ( e.g. Visa Deposit via PXP Financial Acquiring, via AIBMS, Wirecard or any other third party acquirers).
- Payment Account: the client recognition information at the provider for the certain repayment method, e.g. card details, bank details, etc.
Re re Payments may be produced in PXP Financial Payment provider simply by using one of several integration that is following:
- Redirect Integration: the client is rerouted to PXP Financial Hosted Payment Pages for going into the re payment information. Almost all of y our direct merchants utilize this integration choice.
- Backend2Backend Integration: the client comes into the re payment data regarding the vendor’s site which causes a server-to-server call to PXP Financial Payment provider API to start the re payment. The Backend2Backend Integration choice provides the vendor the possibility to generate the Payment UI on it’s own and 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 is likely to be delivered from PXP Financial Payment provider to a vendor endpoint indicating what’s the processing status associated with re re payment. Instead, the vendor application can invoke lots of API options for retrieving re re re payment details, doing actions that are additional a payments, etc.
PXP Financial has APIs that is several available merchants:
- Payment Service v3: an XML POST API could be the standard payday loans in Lansing IA no bank account 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.