NetQuarry.Services.Payment Namespace

Handles the webhook events from braintree You must have the web.config entry: <add verb="POST,GET" path="braintree.ashx" type="NetQuarry.Services.Payment.BraintreeWebhook, EAP.Core, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b1bfd4831f604c0b" validate="false" />

Simple version of a disbursement.

Objects used in GoCardless' API. See IGoCardless.

Customer object to pass information about a customer. swedish_identity_number field is NEVER set by us because it may only be supplied for Swedish customers. Corresponds directly to GoCardless Customer object https://developer.gocardless.com/api-reference/#core-endpoints-customers.

CustomerBankAccount object to pass information about a customer bank account. A bank account has to be tied to a customer. 1 customer can have multiple accounts. A customer's bank accounts must be unique. GoCardless will reply with a bank_account_exists error if you try to duplicate a bank account. Corresponds directly to GoCardless CustomerBankAccount object https://developer.gocardless.com/api-reference/#core-endpoints-customer-bank-accounts.

Error information. Set by GoCardless for response to API call instead of the expecting object if there was an error. Corresponds directly to GoCardless Error object https://developer.gocardless.com/api-reference/#api-usage-errors.

Some possible error reasons. Descriptions are from GoCardless.

The type of an error, depending on it's root cause.

Array listing any errors that have been raised in 1 of 2 formats: field + request_pointer + message, or reason + message.

Event object to pass information about an event. Events are stored for all webhooks. An event refers to a resource which has been updated, for example a payment which has been collected, or a mandate which has been transferred. Corresponds directly to GoCardless Events object https://developer.gocardless.com/api-reference/#core-endpoints-events.

Details about the event. Is always set when GoCardless sends an event.

Picklist for origin from GoCardless.

Picklist of options for include from GoCardless.

Picklist of options for resource_type from GoCardless.

IDs of things that could be related.

Mandate object to pass information about a mandate. A mandate is a Direct Debit mandate with a bank account. Almost always only want 1 mandate per bank account. Can take multiple payments against a mandate. Corresponds directly to GoCardless Mandate object https://developer.gocardless.com/api-reference/#core-endpoints-mandates.

Picklist for status from GoCardless.

Options available on all cursor-paginated endpoints. All list/index endpoints are ordered and paginated reverse chronologically by default.

Date cursor options.

ID cursor options: [var before]...[returned items]...[var after]

Key-value store of custom data. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.

Payment object to pass information about a payment. Payments are taken against a mandate. Can have multiple payments against a mandate. Corresponds directly to GoCardless Payment object https://developer.gocardless.com/api-reference/#core-endpoints-payments.

Picklist for status from GoCardless.

RedirectFlow object to pass information about a redirect flow. A redirect flow can create a customer, customer bank account and mandate without needing GoCardless to approve pages. Corresponds directly to GoCardless RedirectFlow object https://developer.gocardless.com/api-reference/#core-endpoints-redirect-flows.

Info about the customer that can be filled by us/from our website. Info be filled in the GC form in the redirect link. Other than in the Create API, this isn't normally used.

Refund object to pass information about a refund. Refund a payment. Corresponds directly to GoCardless Refund object https://developer.gocardless.com/api-reference/#core-endpoints-refunds.

Wrapper for errors if GoCardless gives an error object.

Handles webhook events from GoCardless. You must have the web.config entry: <add verb="POST,GET" path="gocardless.ashx" type="NetQuarry.Services.Payment.GoCardlessWebhook, EAP.Core, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b1bfd4831f604c0b" validate="false" /> Webhooks: https://developer.gocardless.com/api-reference/#events-mandate-actions GoCardless will try sending a webhook up to 10 times. Webhooks may arrive out of order. All past webhooks are visible in online dashboard. Can manually retry sending webhooks from there. Ignore unknown events because new ones might be added by GoCardless and are considered backwards compatible changes. WebHooks are sent from: 37.58.102.70 and 37.58.102.71 (whitelist in firewall).

Class derived from ApplicationWebhookArgs used for incoming GoCardless webhook notifications. Adds ResourceType and Action. See ApplicationWebhookArgs.

PaymentMethod object to pass information to create a payment method.

Notification from braintree

Describes a Braintree subscription.

Transaction object to store transaction details.

Interface to the Braintree service

Payment communication interface. UK Online Direct Debit provider.

Links to GoCardless' documentation:

• API reference: https://developer.gocardless.com/api-reference/#api-usage-making-requests.
• Testing scenarios: https://developer.gocardless.com/getting-started/developer-tools/scenario-simulators/.
• Errors: https://developer.gocardless.com/api-reference/#api-usage-errors.
• Webhooks: https://developer.gocardless.com/api-reference/#events-mandate-actions.

Payment expiration behavior when adding a card. This dictates how the expiration date is provided to the Braintree payment service in AddPaymentMethod(PaymentMethod) which obtains the setting from the service's BraintreeAPI_PaymentExpirationType property.

Controls which attributes to send to Braintree when creating a card. The default is none as the nonce holds PCI compliant data for this. This is used by the Braintree payment service in AddPaymentMethod(PaymentMethod) which obtains the setting from the service's BraintreeAPI_PaymentIncludeAttributes property.

Subscription statuses.

The status of the payment Transaction, status_id These are based on the Braintree Transaction Statuses and more detailed information about these statuses for Braintree statuses can be found there.