Loading...
Cross shared collection | Cenit Admin

Basic info

Title
Pushpay API 1.1.0.8434
Image
/file/setup~cross_shared_collection/57b1ee95ad9815587a000501/image/
Name
pushpay_api_1_1_0_8434
Tags
Summary
Pushpay® improves sales and business processes by making payments simple.
Readme

These collection have been automatically generated from a swagger specification

API specs supplied by Image title

Categories
IdTitleDescriptionUpdated at
financialFinancialFinancial and accounting servicesDecember 01, 2016 17:06
1 Categories
Authors
Name
Cenit Team
1 Cross collection authors
Pull count
0
Id
57b1ee95ad9815587a000501
Created at
August 15, 2016 16:32
Updated at
December 06, 2016 13:09

Compute

Snippets
NamespaceNameTypeDescriptionUpdated at
Pushpay API 1.1.0.8434AccountPaymentMethod.jsonAuto detect - -
Pushpay API 1.1.0.8434AchModel.jsonAuto detect - -
Pushpay API 1.1.0.8434AddressDetails.jsonAuto detect - -
Pushpay API 1.1.0.8434AnticipatedPayer.jsonAuto detect - -
Pushpay API 1.1.0.8434AnticipatedPaymentListRepresentation.jsonAuto detect - -
Pushpay API 1.1.0.8434AnticipatedPaymentRepresentation.jsonAuto detect - -
Pushpay API 1.1.0.8434AnticipatedPaymentStatusRepresentation.jsonAuto detect - -
Pushpay API 1.1.0.8434Api.jsonAuto detect - -
Pushpay API 1.1.0.8434ApiDeclaration.jsonAuto detect - -
Pushpay API 1.1.0.8434AuthorizationCodeGrantType.jsonAuto detect - -
86 Snippets (showing 10)

Connectors

Connections
NamespaceNameUrlKeyTokenAuthorizationUpdated at
Pushpay API 1.1.0.8434Oauth 2 access code Connectionhttps://api.pushpay.com/ -
Pushpay API 1.1.0.8434Oauth 2 implicit Connectionhttps://api.pushpay.com/ -
2 Connections
Webhooks
NamespaceNamePathMethodDescriptionAuthorizationUpdated at
Pushpay API 1.1.0.8434GET Swagger/swaggerget - -
Pushpay API 1.1.0.8434GET Swagger {resourcename}/swagger/{{resourceName}}get - -
Pushpay API 1.1.0.8434DELETE V1 Anticipatedpayment {token}/v1/anticipatedpayment/{{token}}deleteDeleting an anticipated payment will only work if the payment exists and the Status is 'Unassociated'. -
Pushpay API 1.1.0.8434GET V1 Anticipatedpayment {token}/v1/anticipatedpayment/{{token}}get - -
Pushpay API 1.1.0.8434PUT V1 Anticipatedpayment {token}/v1/anticipatedpayment/{{token}}put - -
Pushpay API 1.1.0.8434GET V1 Anticipatedpayment {token} Payment/v1/anticipatedpayment/{{token}}/paymentgetGet the payment details for the payment that was made for this anticipated payment (if payment has been completed). -
Pushpay API 1.1.0.8434GET V1 Anticipatedpayment {token} Status/v1/anticipatedpayment/{{token}}/statusgetGet's the status of the anticipated payment. Possible values are: * Unassociated (payment link has not been clicked on) * Processing (payment link has been clicked on, user is attempting payment) * Completed (payment has been completed successfully * Failed (payment has failed - Declined for insufficient funds or payment process was abandonded by the user) -
Pushpay API 1.1.0.8434POST V1 Anticipatedpayments/v1/anticipatedpaymentspostWhen creating a new anticipated payment you must: * Specify a merchant (by setting the 'merchant' property to the ID or handle of the merchant). All other fields are optional - but recommend setting the 'reference' field to a local identifier for the payment, and populating an fields that are required to be certain values for tracking the payment for the Merchant. Fields are passed in as an array of objects, each object has 3 properties. * key * value * readOnly The 'key' is a string and must be either the reference definition's ID, or the keyword 'amount' for setting the amount of this anticipated payment. The value is the value of the reference field (a string) or the amount (which must also be specified as a string, or using the format: { "value": "123.45", "currency": "USD"} The value readOnly is a boolean field - where if 'true' then field will be made read-only, this works for both reference definitions and the amount field -
Pushpay API 1.1.0.8434GET V1 Diagnostics Identity/v1/diagnostics/identitygetRetrieves details of the client being used to make this API request - allows clients/3rd party developers to see what claims are included in their access token -
Pushpay API 1.1.0.8434GET V1 Merchant {merchantkey}/v1/merchant/{{merchantKey}}getRetrieves the details of the merchant including the reference definitions -
37 Webhooks (showing 10)
Connection Roles
NamespaceNameWebhooksConnectionsUpdated at
Pushpay API 1.1.0.8434Oauth 2 access code Connections -
Pushpay API 1.1.0.8434Oauth 2 implicit Connections -
2 Connection Roles

Data

Data Types
NamespaceNameSlugTypeStorage sizeUpdated at
Pushpay API 1.1.0.8434AccountPaymentMethodaccount_payment_methodJson Data Type0 Bytes -
Pushpay API 1.1.0.8434AchModelachmodelJson Data Type0 Bytes -
Pushpay API 1.1.0.8434AddressDetailsaddress_detailsJson Data Type0 Bytes -
Pushpay API 1.1.0.8434AnticipatedPayeranticipated_payerJson Data Type0 Bytes -
Pushpay API 1.1.0.8434AnticipatedPaymentListRepresentationanticipated_payment_list_representationJson Data Type0 Bytes -
Pushpay API 1.1.0.8434AnticipatedPaymentRepresentationanticipated_payment_representationJson Data Type0 Bytes -
Pushpay API 1.1.0.8434AnticipatedPaymentStatusRepresentationanticipated_payment_status_representationJson Data Type0 Bytes -
Pushpay API 1.1.0.8434ApiapiJson Data Type0 Bytes -
Pushpay API 1.1.0.8434ApiDeclarationapi_declarationJson Data Type0 Bytes -
Pushpay API 1.1.0.8434AuthorizationCodeGrantTypeauthorization_code_grant_typeJson Data Type0 Bytes -
86 Data Types (showing 10)

Security

Authorizations
NamespaceNameStatusTypeUpdated at
Pushpay API 1.1.0.8434Oauth 2 access code AuthorizationUnauthorizedOauth 2 Authorization -
Pushpay API 1.1.0.8434Oauth 2 implicit AuthorizationUnauthorizedOauth 2 Authorization -
2 Authorizations
OAuth 2.0 Scopes
ProviderNameDescriptionUpdated at
create_anticipated_paymentCreate anticipated payments for any merchant -
list_anticipated_paymentsList anticipated payment for a merchant -
list_my_merchantsList merchants that you are an administrator for -
manage_webhooksManage webhooks for a merchant -
merchant:download_fileDownload files From our storage -
merchant:make_ach_paymentMake ACH Payment -
merchant:make_card_paymentMake Card Payment -
merchant:make_cash_paymentMake Cash Payment -
merchant:manage_community_membersManage members in a merchant's community -
merchant:manage_recurring_paymentManage Recurring Payment (Pause, Resume, Cancel) -
30 OAuth 2.0 Scopes (showing 10)

Config

Namespaces
NameSlugUpdated at
Pushpay API 1.1.0.8434pushpay_api_1_1_0_8434 -
1 Namespaces

Metadata