Skip to main content
The Account object can store multiple payment methods, defined by PaymentMethod objects. Subscribe supports the following payment method types:
  • **Merchant Recorded:**can be used to manually enter payments made by cash, check, or other payment method, and accepted from your customers outside the Subscribe system.
  • Credit cards: Credit cards can be used for standard purchases, including subscriptions.
  • Electronic Check Payment (ECP) through Automated Clearing House ( ACH ) : ECP can be used for recurring or onetime transactions. You can also use ECP to pay your vendors or affiliates in real-time transactions.
  • **European Direct Debit (EDD):**This payment method is similar to ECP in the United States in that it is a direct debit from a banking account. (Einzugsermachtigungsverfahren (ELV), the German version of EDD, requires that a customer complete a mandate to authorize the merchant to debit the customer’s bank account, and is the primary payment method in use for online transactions in Germany.) Subscribe supports EDD in Germany, Austria, and the Netherlands through Chase Paymentech as the payment processor.
  • United Kingdom Direct Debit (UK DD): This payment method is similar to EDD in that it is a direct debit from a bank account, and requires the customer to complete a mandate to authorize the merchant to debit the customer’s bank account. UK DD uses the British pound (GBP) currency.
  • Boleto Bancário: This payment method, primarily used in Brazil, requires that the customer first provide you with a fiscal number. The payment processor then creates a payment slip with that number and other customer details. Finally, the customer presents the payment slip to the bank to complete the transaction. For real-time transactions, the payment processor sends the merchant a URL to a website that provides instructions for payment processing, which the merchant must present to the customer. (The instructions usually involve having the customer print the instructions and a payment slip, and present them to their bank.) Your customer must complete the steps listed on the website before the transaction can proceed. When complete, the bank transfers the money to the payment processor, which captures the transaction and notifies Subscribe. On the Subscribe side, the transaction remains pending until the payment is captured or the transaction expires. For recurring billing (a subscription, requiring an AutoBill object), the customer receives an email during every billing period in which a payment is due, which contains the URL to the website and payment processing instructions. The corresponding transaction is generated and processed by Subscribe in coordination with the payment processor.
  • PayPal: Subscribe supports real-time transactions through PayPal Express Checkout. Subscribe also supports PayPal reference transactions for AutoBill-based recurring billing through e-wallet, whereby PayPal maintains the customer’s payment information, such as the credit card number, checking account number, and bank routing number. When making a purchase on your site, the customer is redirected to PayPal’s login page to complete the payment information then, after success or failure, redirected back to your site to continue the process. For recurring bills with reference transactions, the customer needs to visit the PayPal site only once at startup. The subsequent rebilling transactions require no action on the customer’s part.
  • Token: This is a Vindicia-specific payment method that measures usage or metering, and enables you to support complex billing models that involve tracking token units in addition to fixed-price billing cycles. You define the units, such as minutes, downloads, incentive points, virtual currency, and storage. You also define token types, and manage your customers’ balances by granting or decrementing tokens with Subscribe objects (Product, BillingPlan, and AutoBill) on the Subscribe Portal or with the Subscribe API. The tokens that you grant a customer are associated with a customer account, each token type having a separate balance. For example, a customer account can have separate balances for downloads, storage, and logins, which are displayed as payment methods on the customer’s account page. Note: Subscribe support for payment methods varies from payment processor to payment processor. Contact Vindicia Client Services for more information.
  • External Token: To support external tokens as a payment method, set the externalToken field of the PaymentMethod object to the token value and set Type to the payment method that is tokenized (for example, CreditCard). For supported processors, when an externalToken is specified, the underlying payment method type-specific object can be left without the identifier/account number (for example, for credit cards). Specify what is known, but Account Number, Expiration, and CVN are not needed.

Define a Payment Method for an existing Account

Parent topic:Working with Accounts