doc2.0 doc2.0 doc2.0
/
  • General Introduction
  • 1. API Use-Cases
    • 1.1. Server-to-Server Sale
    • 1.2. Server-to-Server Preauth, Capture and Cancel
    • 1.3. Server-to-Server Transfer
    • 1.4. Server-to-Server Payout
    • 1.5. Sale Form
    • 1.6. Preauth Form, Capture and Cancel
    • 1.7. Transfer Form
    • 1.8. Payout Form
    • 1.9. Payout By Reference
    • 1.10. Payout with bank confirmation
    • 1.11. Deposit To Card Transfer
    • 1.12. Recurring Sale
    • 1.13. Recurring Preauth, Capture and Cancel
    • 1.14. Recurring Payments Service
    • 1.15. Return Transactions
    • 1.16. Payment Cashier
    • 1.17. Buy Now Button
    • 1.18. Direct Bank transfer
    • 1.19. Bank transfer with Invoice
    • 1.20. Mobile Device Sale
    • 1.21. Mobile Device Transfer
    • 1.22. Mobile Device Сard Verification
  • 2. General API Usage
    • 2.1. Async-Response
    • 2.2. Billblend test scenarios
    • 2.3. Request Authentication Methods
      • SHA-1 Request Authentication Method
      • OAuth Request Authentication Method
  • 3. API Commands, Callbacks & Redirects
    • 3.1. /api/v2/auth-cash
    • 3.2. /api/v2/capture
    • 3.3. /api/v2/create-card-ref
    • 3.4. /api/v2/get-balance
    • 3.5. /api/v2/get-balance/manager
    • 3.6. /api/v2/get-balance/merchant
    • 3.7. /api/v2/get-exchange
    • 3.8. /api/v2/get-card-info
    • 3.9. /api/v2/make-rebill-preauth
    • 3.10. /api/v2/make-rebill-sale
    • 3.11. /api/v2/preauth
    • 3.12. /api/v2/preauth-form
    • 3.13. /api/v2/return
    • 3.14. /api/v2/sale
    • 3.15. /api/v2/sale-form
    • 3.16. /api/v2/payout-form
    • 3.17. /api/v2/status
    • 3.18. /api/v2/void
    • 3.19. /api/v4/create-card-ref
    • 3.20. /api/v4/create-recurring-payments
    • 3.21. /api/v4/process-recurring-payments
    • 3.22. /api/v4/update-recurring-payments
    • 3.23. /api/v4/status
    • 3.24. /api/v4/payout
    • 3.25. /api/v4/payout-by-ref/
    • 3.26. /api/v4/payout-check
    • 3.27. /api/v4/payout-pay
    • 3.28. /api/v4/transfer
    • 3.29. /api/v4/transfer-form
    • 3.30. /api/v4/transfer-by-ref
    • 3.31. /registry/upload
    • 3.32. /services/transaction-report
    • 3.33. /services/v2/rpt-engine
    • 3.34. /view-invoice
    • 3.35. /view-invoice-xml
    • 3.36. /api/3ds/v1/upload-cres-result
    • 3.37. /api/3ds/v1/upload-method-url-result
    • 3.38. /api/3ds/v1/upload-pares-result
    • 3.39. CRes Redirect
    • 3.40. PaRes Redirect
    • 3.41. Final Redirect
    • 3.42. Mobile Device Connecting Party Server API
      • Initiate verification
      • Check verification
      • Verification card mapping notification
      • Initiate sale
      • Check sale
      • Sale card mapping notification
      • Initiate transfer
      • Check transfer
      • Transfer card mapping notification
      • Development tools
    • 3.43. Mobile Device Billblend API
      • Perform validation
      • Verification status
      • Perform sale
      • Sale status
      • Perform transfer
      • Transfer status
      • Complete Transfer
    • 3.44. Connecting Party Callbacks
  • 4. Common Utilities
    • 4.1. Account balance
    • 4.2. PAN Eligibility
    • 4.3. Receipt and message templates
    • 4.4. Reports for Integration
  • 5. Reference
    • 5.1. FAQ
    • 5.2. 3DS Overview
    • 5.3. Forms Customization
    • 5.4. Country and State Codes
    • 5.5. Currency Codes
    • 5.6. Payment Gateway Internal Errors
    • 5.7. Language Codes
    • 5.8. Order Stage
    • 5.9. Statuses
    • 5.10. Transaction Filters
    • 5.11. Glossary
  • 6. OpenAPI Specification
  1. doc2.0 /
  2. 4. Common Utilities
View Source Open in ChatGPT Open in Claude

4. Common Utilities

  • 4.1. Account balance
  • 4.2. PAN Eligibility
  • 4.3. Receipt and message templates
  • 4.4. Reports for Integration
Previous
3.44. Connecting Party Callbacks
Next
4.1. Account balance

support@billblend.com