WePay

Split/Chained Payments

Scenario

Collect credit card information once and send money to more than one merchant.

Example

Let's say you were a donation platform. When a donor makes a donation, in addition to their primary donation, you give the donor the opportunity to give an additional $5 to a second charity. Your platform only collects credit card information from the donor once but you can send the different amounts to the different charities.

At WePay, the fundraiser is the merchant and the donor is the payer and we'll use those terms below.

Key Concepts

There are two options to facilitate collecting credit card information once and using it multiple times.

  • iFrame - the iFrame uses the /preapproval/create API call to obtain a preapproval_id which can be used multiple times to send money to different payees (merchants). This method lets you use WePay's pre-built and optimized form to collect credit card information. As information is shared securely between the browser and WePay, any PCI compliance is avoided.
  • Tokenization - Tokenization uses WePay's tokenization.js to obtain a credit card token which can be used multiple times to send money to different payees. This method lets you use your own form to collect credit card information. As there is exposure to developer error or fraud, a minor amount of PCI compliance is required.

Solutions