iVendNextDevelopers Request a sandbox

Payment Connection

Which payment provider's app serves a company's payment rails in a country, and its registration.

Area: Payments and payment methods · Why it is here: recipe payment_connector; recipe wallet · Fields: 27

Read and write it

Every call runs as your app's own user, with its key in one header, at the retailer's own address. The user reads and writes only what its role allows: your app's user, and the rights the retailer gives it.

Read a list (only name unless you ask for fields):

curl -s "https://⟨site⟩/api/resource/Payment%20Connection?fields=%5B%22*%22%5D&limit_page_length=20" \
  -H "Authorization: token ⟨api key⟩:⟨api secret⟩"

Read one:

curl -s "https://⟨site⟩/api/resource/Payment%20Connection/⟨name⟩" -H "Authorization: token ⟨api key⟩:⟨api secret⟩"

Create one (the required fields first), if your app's role may:

curl -s -X POST "https://⟨site⟩/api/resource/Payment%20Connection" -H "Authorization: token ⟨api key⟩:⟨api secret⟩" \
  -H "Content-Type: application/json" -d '{"company": …, "rails": …, "provider_key": …, "state": …, "certification_required": …}'

Change one with PUT /api/resource/Payment%20Connection/⟨name⟩ and the fields you change; a table sent there replaces its rows, so send its existing rows too. All the record calls and their answers: the API reference.

Samples that use it

s22_customer_loyalty

Fields

Read from the product at POS 2.1.0.667 (till app 60147699c): its own fields, the fields iVendNext adds to it, and iVendNext's changes to any of them. Read-only fields are set by iVendNext; a hidden one is not on the form but can be read. Every record also has name (its id, in the address), owner, creation, modified, modified_by and docstatus (0 a draft, 1 submitted, 2 cancelled), all read-only.

Field Field name Type Required Read-only Hidden Links to
Company company Link yes Company
Country country Link yes Country
Rails rails Select yes one of: card_present, card_not_present, mobile_money, wallet, bank_transfer
Provider provider_key Autocomplete yes
Gateway app gateway_app Data
Registration registration_state Select yes one of: Registered, Not Registered, Refused
Registration error last_registration_error Small Text yes
Title title Data yes yes
State state Select yes one of: Draft, App Pending, Credentials Entered, Tested, Blocked, Certification Pending, Live, Suspended, Abandoned
State changed on state_changed_on Datetime yes
State changed by state_changed_by Link yes User
Refusal reason refusal_reason Small Text yes
Note note Small Text
Payment Account account Link Payment Account
Last test last_test Link yes Payment Connection Test
Callback URL callback_url Data yes
Certification required certification_required Select yes one of: unknown, required, not_required
Requirement changed on certification_required_changed_on Datetime yes
Requirement changed by certification_required_changed_by Link yes User
Change acknowledged by the Approver certification_change_acknowledged Check
Decided requirement changed on certification_requirement_lowered_on Datetime yes
Acknowledged on certification_change_acknowledged_on Datetime yes
Certification state certification_state Select one of: not_required, required_not_started, submitted, granted, refused
Since certification_state_since Datetime yes
Owner certification_owner Link User
Reference certification_ref Data
Authority's stated reason certification_refusal_reason Small Text

All record types · What you can use

This record type in the kit