add_payment_method
Add payment method for contact
Code
add_payment_method › Request Body
contact_idach_accountach_bankach_name_onach_routingach_typecard_cvv2card_expires_mmcard_expires_yycard_name_oncard_numbercard_typetypeaddresscustomer_profile_idvendor_payment_method_idaccount_descriptionmetadataadd_payment_method › Responses
successmessagedataapprove_pending_payment
approve_pending_payment
approve_pending_payment › Request Body
integration_instance_external_idExternal ID of the integration instance.
payment_idUnique identifier for the payment to approve. Exactly one of payment_id or reference_id must be provided.
reference_idExternal reference identifier for the payment to approve. Exactly one of payment_id or reference_id must be provided.
set_reference_idOptional reference ID to set on the payment.
settlement_date_timeDate and time when the payment was settled.
vendor_processing_fee_in_centsOptional processing fee charged by the vendor in cents.
approve_pending_payment › Responses
successIndicates whether the payment approval was successful.
messagesError messages if the operation failed.
change_payment_method_single
Setup payment method for policy or policy term (if policy term id passed)
Code
change_payment_method_single › Request Body
policy_idpolicy_term_idauto_payment_method_idauto_pay_days_beforecontact_idoverride_propagationchange_payment_method_single › Responses
successmessagedatadecline_pending_payment
decline_pending_payment
decline_pending_payment › Request Body
integration_instance_external_idExternal ID of the integration instance.
vendor_messageMessage from the vendor explaining the reason for declining the payment.
payment_idUnique identifier for the payment to decline. Exactly one of payment_id or reference_id must be provided.
reference_idExternal reference identifier for the payment to decline. Exactly one of payment_id or reference_id must be provided.
requester_contact_idOptional. Contact id of the BriteCore user who originated the payment, derived from the authenticated user by request_payment_entry and echoed back via the Stripe PaymentIntent metadata. When provided, the "Payment Declined" policy note is attributed to that user instead of the integration service account (srv_integrations). See BC-19725.
decline_pending_payment › Responses
successIndicates whether the payment decline was successful.
messagesError messages if the operation failed.
ensure_receipt
Code
ensure_receipt › Request Body
payment_idUUID of the payment
policy_numberPolicy number to get the receipt for
ensure_receipt › Responses
successWhether the request succeeded
Receipt data when success is true
evaluate_convenience_fee_formula
Design-time tester for convenience-fee formulas.
Code
evaluate_convenience_fee_formula › Request Body
Per-method formula strings. Every key is optional. Empty / omitted values surface as inheritance markers in the response so the admin UI can render (inherits) instead of an error.
disclosure_stylePreview-message style for the returned messages. Defaults to standard; any unrecognized value is treated as standard.
evaluate_convenience_fee_formula › Responses
successWhether the operation was successful
get_billing_contact_emails
Code
get_billing_contact_emails › Request Body
policy_numberPolicy number to get billing contact emails for
get_billing_contact_emails › Responses
successWhether the request succeeded
Email and email options when success is true
get_unpaid_invoices_by_date
Retrieve unpaid invoices for bill_date/due_date with additional information
Code
get_unpaid_invoices_by_date › Request Body
bill_datedue_datemanualpay_date_adjustmentautopay_date_adjustmentget_unpaid_invoices_by_date › Responses
successmessagedataimport_payment_method
import_payment_method
import_payment_method › Request Body
vendor_customer_idVendor Customer ID. This is the ID of the customer in the vendor system.
vendor_payment_method_idVendor Payment Method ID. This is the ID of the payment method in the vendor system.
payment_method_typecontact_idContact ID to which the payment method should be associated with.
contact_external_system_referenceExternal System Reference of the Contact to which the payment method should be associated with.
policy_term_idPolicy Term ID to which the payment method should be associated with.
policy_term_external_system_referenceExternal System Reference of the Policy Term to which the payment method should be associated with.
requester_contact_idContact ID of the BriteCore user who originally requested that this payment method be created. When provided, this user (rather than the integration server's service account) is recorded as the author of the resulting note. The integration server should forward the requester_contact_id it received on the matching request_payment_method_entry call.
import_payment_method › Responses
successIndicates if the request was successful
make_payment_by_contact_and_payment_method
Make payment for policy/contact with payment_method_id and payment_amount
Code
make_payment_by_contact_and_payment_method › Request Body
payment_method_idBritecore Payment Method ID
payment_amountPayment Amount: min/max/next_term or Explicit Amount to Pay
contact_idContact ID
policy_idPolicy ID
payor_namePayor name: contact name of the person who initiated payment for the policy(optional)
payor_emailPayor email: contact email of the person who initiated payment for the policy(optional). When present and valid, the standard payment confirmation is auto-emailed to it; when absent or invalid, no confirmation email is sent.
bypass_cannotpay_guardSkip the payability guard and accept the payment on a policy the carrier's configuration would otherwise refuse -- a pending non-pay cancellation flagged Poor Payment History, an expired or rejected policy, one canceled past its payment window (BC-24420). For internal callers acting on behalf of staff, who may take a payment the insured cannot make themselves: the life-cycle options behind the refusal are scoped to external payments. Must be a real boolean: a non-boolean is rejected with error_code invalid_parameter rather than coerced, so a stringy "false" cannot be read as an enabled bypass. Omit it, or send false, on any insured-facing channel.
make_payment_by_contact_and_payment_method › Responses
successIndicates if the request was successful
error_codeStable, machine-readable reason the request failed. Present only on failure, and only for failures that have one. 'payments_not_allowed' means the policy's status or its policy type's life cycle forbids an electronic payment (BC-24420) -- a refusal by configuration, not an outage, so retrying will not help. 'invalid_parameter' means a parameter was sent with the wrong type -- notably bypass_cannotpay_guard, which must be a real boolean and is rejected rather than coerced, so a stringy "false" cannot be read as an enabled bypass.
make_payment_by_invoice_or_policy
Please use api/v2/payments/store_external_payment endpoint if you're simply registering an external payment.
Code
make_payment_by_invoice_or_policy › Request Body
amountpayment_dateinvoice_numberpolicy_numberpayment_transaction_idsource_idmetamake_payment_by_invoice_or_policy › Responses
successmessagedatamark_payment_nsf
Searches respective payment for the specified amount/date/invoice and mark it as NSF.
Code
mark_payment_nsf › Request Body
amountpayment_datepolicy_numberinvoice_numberconfirmation_numberdisable_auto_paymark_payment_nsf › Responses
successmessagedatarecord_saved_method_authorization
Persist the saved-payment-method authorization attestation for a contact.
Code
record_saved_method_authorization › Request Body
contact_idUUID of the policyholder the payment method is being stored for.
authorization_confirmedThe affirmative attestation captured by the consent UI. Proof is recorded only when this is a strict boolean true; a truthy-but-non-affirmative value is rejected.
record_saved_method_authorization › Responses
Decision Table
| Variant | Matching Criteria |
|---|---|
| type = object · requires: data, success, messages | |
| type = object · requires: success, messages | |
| type = object · requires: success, permissionDenied |
successAny messages related to the request.
retrieve_convenience_fee
Retrieve the convenience fee to be charged by the enabled payment processor based on the amount of the payment and the type of account being used.
Code
retrieve_convenience_fee › Request Body
account_typeThe type of the account being charged. For PaymentProcessor integration: 'ACH', 'CC', or 'DEBIT'. For legacy vendors: 'ACH', 'MasterCard', 'VISA', 'AmericanExpress', 'Discover'
policy_idPolicy ID (Optional)
retrieve_convenience_fee › Responses
successIndicates if the request was successful
retrieve_convenience_fee_preview
Retrieve convenience fee preview with messages and fee amounts grouped by payment method.
Code
retrieve_convenience_fee_preview › Request Body
payment_methodsList of payment methods to calculate fees for. If not provided, defaults to all payment methods (ach, cc, debit)
policy_idPolicy ID (optional)
retrieve_convenience_fee_preview › Responses
successIndicates if the request was successful
retrieve_payment
retrieve_payment_method_creation_details
retrieve_payment_method_creation_details
retrieve_payment_method_creation_details › Request Body
contact_idContact ID for which to retrieve payment method creation details.
typesOptional list of payment method types to include in the creation details.
policy_idsOptional list of policy IDs to associate with the payment method.
success_urlOptional URL to redirect to after successful payment method creation.
cancel_urlOptional URL to redirect to if payment method creation is cancelled.
requester_contact_idOptional contact ID of the requester. If not provided, defaults to the currently logged-in user.
retrieve_payment_method_creation_details › Responses
successIndicates if the request was successful
retrieve_payment_methods
Retrieves payment methods according to received parameters
Code
retrieve_payment_methods › Request Body
contact_idsRequired. List of contact IDs to filter payment methods by.
exp_less_thanOptional. Filter all payment methods where expiration date is less than or equal to (current date + exp_less_than days). If not provided, all active payment methods are returned.
min_updated_onOptional. Filter payment methods created after the given date in ISO 8601 format (e.g. 2025-01-01T00:00:00Z).
retrieve_payment_methods › Responses
successIndicates if the request was successful
retrieve_pending_payments_for_settlement
retrieve_pending_payments_for_settlement
retrieve_pending_payments_for_settlement › Request Body
integration_instance_external_idExternal ID of the integration instance. Only pending payments owned by this instance are returned.
retrieve_pending_payments_for_settlement › Responses
Response schema for /api/v2/payments/retrieve_pending_payments_for_settlement
idUnique identifier for the pending payment.
reference_idExternal reference identifier for the payment.
retrieve_policy_billing_information
Retrieve a Policy's billing information
Code
retrieve_policy_billing_information › Request Body
policy_idID of the Policy
policy_term_idID of the Policy Term
billing_onlyFlag to indicate that the response should only include billingSetup information.
retrieve_policy_billing_information › Responses
successIndicates if the request was successful
retrieve_saved_method_authorization
Whether the saved-payment-method consent control must be shown, and the disclosure copy to render with it. Read-only.
Code
retrieve_saved_method_authorization › Request Body
retrieve_saved_method_authorization › Responses
Decision Table
| Variant | Matching Criteria |
|---|---|
| type = object · requires: data, success, messages | |
| type = object · requires: success, messages | |
| type = object · requires: success, permissionDenied |
successAny messages related to the request.
send_payment_receipt_email
Code
send_payment_receipt_email › Request Body
payment_idUUID of the payment
policy_numberPolicy number; must belong to the payment. Does not select the attached document -- multi-policy payments email the group confirmation
recipient_emailRecipient email address (from UI dropdown or free-form entry)
subjectOptional email subject; defaults to a standard receipt subject if omitted
bodyOptional email body; defaults to a standard message if omitted
send_payment_receipt_email › Responses
successWhether the request succeeded
Result when success is true
store_external_payment
Code
store_external_payment › Request Body
policy_numberpolicy_number_normalizedtransaction_amount_in_centstransaction_date_timeexternal_account_namecheck_numbersweep_check_numberstore_external_payment › Responses
successmessagedatastore_payment
store_payment
store_payment › Request Body
integration_instance_external_idExternal ID of the integration instance.
policy_numbersList of policy numbers associated with the payment.
transaction_amount_in_centsAmount of the transaction in cents.
convenience_fee_in_centsConvenience fee charged for the transaction in cents.
pay_byMethod of payment.
account_nameName associated with the payment account.
masked_numberMasked account number for security.
transaction_date_timeDate and time when the transaction occurred.
vendor_messageMessage from the payment vendor.
reference_idUnique reference ID for the transaction.
vendor_responseRaw response from the payment vendor.
vendor_processing_fee_in_centsOptional processing fee charged by the vendor in cents.
payor_nameName of the payor from payment gateway billing details (e.g., Stripe).
payor_emailEmail address of the payor from payment gateway billing details (e.g., Stripe).
britecore_confirmation_numberOptional. BriteCore confirmation (receipt) number minted up front by request_payment_entry and echoed back here so the stored Payment's confirmation number matches the value attached to the Stripe PaymentIntent metadata (BC-22803). When omitted, BriteCore generates one at store time. Capped at 32 chars to match the payments.confirmationNumber VARCHAR(32) column.
requester_contact_idOptional. Contact id of the BriteCore user who originated the payment, derived from the authenticated user by request_payment_entry and echoed back via the Stripe PaymentIntent metadata. When provided, the "Payment Received" policy note is attributed to that user instead of the integration service account (srv_integrations). See BC-19725.
store_payment › Responses
idUnique identifier for the payment.
confirmation_numberConfirmation number for the payment transaction.
receipt_file_idsList of file IDs for payment receipts.
policy_numbersList of policy numbers associated with the payment.
vendor_messageMessage from the payment vendor about the transaction status.
store_payment_nsf
Mark a payment as NSF (V2 API).
Code
store_payment_nsf › Request Body
payment_idUUID of the payment to mark as NSF.
policy_idUUID of the policy that the payment belongs to.
assess_feeWhen to assess NSF fee. 'now' = immediately, 'next' = on next invoice, 'waive' = no fee.
allow_cancelWhether to allow policy cancellation. Must be false if postpone_until_date is provided.
postpone_until_dateDate to postpone outstanding invoices. Accepts various date formats (YYYY-MM-DD recommended).
policy_term_idUUID of the policy term. Required if policy_term_external_system_reference is not provided.
policy_term_external_system_referenceExternal system reference for the policy term. Required if policy_term_id is not provided.
store_payment_nsf › Responses
successWhether the operation was successful.
messagesList of messages from the operation.
Payment data returned from the operation.
