Payment Method Distribution

In addition to the built-in gateway integration, Spreedly also supports the ability to distribute vaulted credit card data to non-gateway, PCI compliant, third parties (referred to as “receivers”). Distribution differs from third party vaulting in that the recipient of the card data is not a known and supported gateway – it can be any third party with whom you do business and is PCI compliant themselves.

How Distribution Works

Using Payment Method Distribution allows you to transact against another service’s API, while still controlling your customer’s card data by vaulting with Spreedly. Consider the following business that needs this ability:

You are a travel service that books accomodations on behalf of your users. You store your customer’s card data in Spreedly up front and use that data to later purchase airline and hotel reservations on behalf of your customers. You only have to ask your customers for their credit card information one time, but can use it to make purchases against several independent services (the airlines, hotels etc…) at booking time. The card data is only transmitted between PCI compliant parties (Spreedly and the airline and hotel endpoints), ensuring compliance with PCI standards.

Spreedly’s payment method distribution functionality enables businesses to transact with multiple PCI-compliant endpoints on behalf of its customers, via a single, consistent, integration.

Single vs. Batch Distribution

Payment method distribution can operate in two modes - single card vs. batch export. If you have an external HTTP API you wish to target that exposes an endpoint that accepts a single card per call, you need the single card mode of PMD. If you have an SFTP endpoint that accepts a file containing multiple cards, then use the batch export mode of PMD.

In both modes, the basic workflow remains the same. You specify a template that tells Spreedly how to format the request, the card or cards to deliver, and Spreedly executes the call on your behalf. Batch export operates in an asynchronous fashion, which involves a little more complexity, but the two modes have more in common than they do otherwise.

Supporting Your Receiver

You can begin developing and testing your PMD workflow using a test receiver. However, before you can distribute real payment method data, you have to get your receiver confirmed and white-listed. Please email the following information to Spreedly to get your receiver in the approval queue. (Alternatively, if you have an existing relationship or contact at the receiver company, you can direct them to Becoming a Receiver. This page is written from their perspective and lets you avoid just being a go-between Spreedly and the receiver.)

  • The receiver name/company along with a link to their public site
  • Proof of the receiver’s level of PCI compliance. Their AOC and most recent security scan usually suffices. Please make sure there is an explicit correlation between the company with the AOC and the API endpoint URL. You can see an example of an AOC and security scan with Spreedly’s own documents which are publicly available.
  • The production URL you will be invoking on the receiver with Spreedly payment data. The production URL must utilize SSL.

We ask that you allow about 2 weeks for Spreedly to approve and configure a receiver for production use. During this time you can begin testing against a test receiver, which allows test payment methods to be delivered to any user-specified endpoint URL.

List of Supported Receivers

We currently support the following receiver types (and their associated whitelisted URLs):

Company Receiver Type and Hostnames
A1 Payments a1_payments
Acapture acapture
Ace Rent a Car ace_rent_a_car
Adquira adquira
Alliance Reservations Network alliance_reservations_network
Allianz Global Assistance allianz_global_assistance,
American Express american_express,,,,
BBC Shop bbc_shop
BestBus bestbus
Bink bink
Blackbaud blackbaud
Blacklane blacklane
Blue Ribbon Bags blue_ribbon_bags
Bluesnap bluesnap bookingcom
Braintree Payments braintree,
Bypass Mobile bypass_mobile
Cashbackapp Mastercard Member Test Facitilty cashbackapp_mastercard_mtf
Cashbackapp Mastercard cashbackapp_mastercard
Cashbackpoint cashbackpoint
CASHNet cashnet
CDS Global cds_global
Chain Commerce chain_commerce
Clover clover
Cosmic Cart cosmic_cart
Credomatic credomatic
CrowdTorch crowd_torch
CyberSource cybersource
Demandware demandware
DirectConnect direct_connect
Diane Von Furstenberg dvf
Economy Rent a Car economy_rent_a_car
ePay epay
Electronic Payment Exchange epx
Eventbrite eventbrite
FanXchange fan_xchange,,
Farelogix farelogix
First Data India Pvt Ltd. first_data_india
Global Technology Partners global_technology_partners
Golf18Network golf18_network
GolfNow golf_now
Hertz hertz,
JEM Marketing jem_marketing
Lincoln Center lincoln_center,
Loyalty Angels Mastercard Member Test Facitilty loyalty_angels_mastercard_mtf
Loyalty Angels Mastercard loyalty_angels_mastercard
Luminate Online luminate_online
Mastercard Member Test Facility mastercard_mtf
Mastercard mastercard
Navitaire navitaire
Network for Good network_for_good
NÜ Car Rentals nu_car_rentals
Omnivore omnivore
ONPEX onpex
Pace Payment Systems pace_payment_systems
PayFabric pay_fabric
Paycorp paycorp
Payflow payflow
Paymark Click paymark_click
Payvision payvision
PrimeSport prime_sport
PromisePay promisepay
Qualpay, Inc qualpay
RedCoach red_coach
RedShield red_shield
Sabre sabre,,
Sage Pay sage_pay
Shopify shopify
SiteMinder site_minder
Spreedly spreedly sprinterbus_net
Stripe stripe
SynXis synxis
Target target
Transcor Data Services tds_tickets
Telecharge telecharge,,,,
Tempus Technologies tempus
Tessitura tessitura_ramp
https://* ticket_network
Ticketmaster ticketmaster
Toast toast
TokenEx tokenex
Travelfusion travel_fusion
Travelport travelport
Travolutionary travolutionary
TSD tsd
Two Tap two_tap
RentPayment vacation_rent_payment
Viator viator
Virtual Card Services virtual_card_services
Walpay walpay
Wantickets wantickets
Worldpay RiskGuardian worldpay_riskguardian,,,
YapStone yapstone