| Name | Type | Description | Notes |
|---|---|---|---|
| created | DateTime | { "description" : "The UTC DateTime when the object was created.", "verbs":[] } | [optional] |
| organization_id | String | {"description":"ID of the BillForward Organization within which the requested PaymentMethod should be created. If omitted, this will be auto-populated using your authentication credentials.","verbs":["POST"]} | [optional] |
| account_id | String | {"description":"ID of the BillForward Account with which you would like to associate the created payment method.<br>If omitted, BillForward will associate the created PaymentMethod with a newly-created Account, whose Profile details will be populated using billing information from the funding instrument.","verbs":["POST"]} | [optional] |
| default_payment_method | BOOLEAN | {"default":false,"description":"Whether the PaymentMethod produced by this request should be elected as the 'default' payment method for the concerned BillForward Account. Whichever PaymentMethod is elected as an Account's default payment method, will be consulted whenever payment is demanded of that Account (i.e. upon the execution of any of the Account's invoices).","verbs":["POST"]} | [optional] [default to false] |
| cardholder_name | String | {"description":"Name of the person who holds the credit card being captured.","verbs":["POST"]} | |
| card_number | String | {"description":"Number of the credit card being captured.","verbs":["POST"]} | |
| expiry_month | String | {"description":"Expiration month of the credit card being captured, formatted MM.","verbs":["POST"]} | |
| expiry_year | String | {"description":"Expiration year of the credit card being captured, formatted YYYY or YY.","verbs":["POST"]} | |
| cvv | String | {"description":"3 or 4 digit card verification value assigned to the credit card being captured.","verbs":["POST"]} | |
| device_data | String | {"description":"(Required when vaulting a PayPal payment method; otherwise optional)<br>A JSON string providing information about the device your customer used to fill out the card capture form. This information is inserted into your form by <a href=\"https://developers.braintreepayments.com/javascript+node/guides/advanced-fraud-tools/client-side\\\">braintree-data.js</a> — if and only if you use Braintree's drop-in form integrations. You should ideally provide it if you have one (it aids with fraud detection), but it is only mandatory in the case of PayPal payment method vaulting.","verbs":["POST"]} | [optional] |
| merchant_account_id | String | {"description":"Braintree <a href=\"https://articles.braintreepayments.com/control-panel/important-gateway-credentials\\\">Merchant account ID</a> with which you wish for the captured funding instrument to transact. Within your Braintree gateway, you can have multiple merchant accounts to process transactions for different businesses or currencies. If you have a single merchant account, it is not necessary to specify a merchant account ID in your API requests. If you have multiple merchant accounts and choose not to specify the merchant account ID, all requests will process through your default merchant account.","verbs":["POST"]} | [optional] |
| ip_address | String | {"description":"IP address of the customer providing the details of the credit card to be captured.","verbs":["POST"]} | [optional] |
| ip_address_country | String | {"description":"Country of the IP address of the customer providing the details of the credit card to be captured.","verbs":["POST"]} | [optional] |
This repository was archived by the owner on Oct 17, 2023. It is now read-only.