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 guides that are comprehensive paperwork to assist you begin working with PXP Financial Payment provider as fast as possible, along with help in the event that you get stuck. Why don’t we jump right in!

Overview

Take note the terms that are following you begin reading the paperwork:

• Vendor: the business offering goods or solutions and PXP that is using Financial processing the matching monetary deals.
• Shop: the web site owned by a vendor where products or solutions might be offered to clients. a vendor may have a few shops/websites that are different.
• Client: The registered client at a vendor’s internet site that is purchasing items or services through the vendor. The terms user and customer” are used interchangeably in this paperwork. Keep in mind that clients are connected up to a vendor, perhaps maybe not store.
• Payment: A transfer of funds either from client to vendor, or from vendor to consumer. The definition of re re payment and “transaction” are utilized interchangeably in this documents.
• Deposit: Subtype of re Payment representing a transfer of funds from consumer to merchant. Also called Purchase, Buy.
• Withdrawal: Subtype of re Payment representing a transfer of funds from merchant to client. Also called Payout, Cashout. It really is relevant to merchants in Gaming and Binary Alternatives companies as an example by https://speedyloan.net/payday-loans-mn/altura/ which clients can get winnings for instance.
• Deposit Reversal: Subtype of Payment representing a transfer of funds from vendor to client for reverting a formerly done deposit.
• Chargeback: Subtype of re Payment representing a transfer of funds from vendor to consumer following the customer has asked their bank to revert a card deposit.
• Card Refund: Subtype of re re re Payment representing a transfer of funds from vendor to consumer being a settlement for the formerly prepared card deposit.
• Re Re Payment Method: Attribute of each Payment. Represents the blend of deal kind (Deposit, Withdrawal, Chargeback, Refund, etc.) in addition to re re payment choice selected by the consumer, e.g. Charge 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 customer funds and certainly will accept the deal, with matching credit/debit following approval. a payment method might be supported by/implemented via 2 or maybe more re payment providers ( e.g. Visa Deposit via PXP Financial Acquiring, via AIBMS, Wirecard or other third party acquirers).
• Payment Account: the client recognition data in the provider for a certain repayment method, e.g. card details, bank details, etc.

Payments may be created in PXP Financial Payment provider simply by using one of several after integration choices:

• Redirect Integration: the consumer is rerouted to PXP Financial Hosted Payment Pages for going into the re payment information. Almost all of y our merchants that are direct this integration choice.
• Backend2Backend Integration: the consumer comes into the re payment information from the vendor’s internet site which causes a server-to-server call to PXP Financial Payment Service API to start the re payment. The Backend2Backend Integration choice provides the vendor the chance to generate the Payment UI on it’s own also to invoke the backend API for initiating payments. Lovers and merchants with built-in payment that is hosted utilize this integration choice.

Both in instances, following the re re payment happens to be triggered a notification may be sent from PXP Financial Payment provider up to a vendor endpoint showing what’s the processing status for the re payment. Instead, the vendor application can invoke lots of API options for retrieving payment details, doing actions that are additional a repayments, etc.

PXP Financial has several APIs offered to merchants:

• Payment Service v3: an XML POST API could be the API that is standard offered 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 extra functionality like vendor onboarding.

Variations are complementary

Take note that more recent versions never completely change older variations, in particular v4 and v5 contain just specific functionality and usually do not fully replace v3.