Diner's Club

Diner's Club is a supported SagePay credit card payment method that is used for transactions during the sales order workflow. Diner's Club is included by default in the payment pick list. It isn't set as a CustomCharge.

Before you can use payment processors and their supported payment methods for transactions during the sales order workflow, configuration is required in Order Management.

The order XML is imported into Order Management with the payment tag when the payment is Authorized or Captured outside of Order Management. When tokenization is enabled, the bfProcessorToken custom attribute is included in the XML. The Secure Storage Enabled field is configured for tokenization in the SagePay External Payment Processors.

Example 1: payment tag in XML

This example shows the payment tag in XML when tokenization is set to 'No' in Order Management, the <card-type> = Diners Club and the <transaction-type> = AUTH.

Note: When the tokenization is set to 'No' for a Captured payment transaction, the XML is the same except that the <transaction-type> = CAPTURE.

<payments>
   <payment>
      <credit-card>
         <card-type>Diners Club</card-type>
         <card-number>XXXX-XXXX-XXXX-08</card-number>
         <expiration-month>05</expiration-month>
         <expiration-year>2020</expiration-year>
     </credit-card>
     <amount>29.33</amount>
     <processor-id>Sagepay</processor-id>
     <transaction-id>16219761</transaction-id>
     <transaction-type>AUTH</transaction-type>
   </payment>
</payments>

Example 2: custom attributes added to the payment tag in XML

This example shows the payment tag in XML when the tokenization is set to 'Yes' in Order Management, the <card-type> = Diners Club, the <transaction-type> = AUTH, and the <custom-attribute attribute-id> ="bfProcessorToken">XXXXX. The XXXXX refers to the token's string of numbers.

Note: When tokenization is set to 'Yes' for a Captured payment transaction, the XML is the same except that the <transaction-type> = CAPTURE.

<payments>
   <payment>
      <credit-card>
         <card-type>Diners Club</card-type>
         <card-number>XXXX-XXXX-XXXX-08</card-number>
         <expiration-month>05</expiration-month>
         <expiration-year>2020</expiration-year>
      </credit-card>
      <amount>29.33</amount>
      <processor-id>Sagepay</processor-id>
      <transaction-id>16219761</transaction-id>
      <transaction-type>AUTH</transaction-type>
      <custom-attributes>
            <custom-attribute attribute-id="bfProcessorToken">DE0F7026-E5B3-2D92-1B1E-26FAB6A984FA</custom-attribute>
            <custom-attribute attribute-id="bfResponseData">VPSProtocol=3.00 Status=OK StatusDetail=0000 : The Authorisation was Successful. VPSTxId={C1DFA2BA-FDC6-CC1E-1821-1302FBB68B58} SecurityKey=ZIFDAIVBRY TxAuthNo=16219761 AVSCV2=DATA NOT CHECKED AddressResult=NOTPROVIDED PostCodeResult=NOTPROVIDED CV2Result=NOTPROVIDED 3DSecureStatus=NOTCHECKED Token={DE0F7026-E5B3-2D92-1B1E-26FAB6A984FA} DeclineCode=00 ExpiryDate=0728 BankAuthCode=999777 VendorTxCode=ae8c0caf-b7d9-499f-99c5-f8b0147c3d7f </custom-attribute>
      </custom-attributes>
   </payment>
</payments>